PEGACPSA23V1 Exam Dumps - Certified Pega System Architect

To adapt the display of property photos to different screen sizes within an apartment hunting application, the best approach is:

A. Use a dynamic layout with a responsive breakpoint at 800 pixels to change from inline-grid triple to inline-grid double format. This option uses responsive design principles to adjust the number of columns based on screen size. When the screen width is below 800 pixels, the layout automatically changes from three columns (triple) to two columns (double), ensuring optimal display on smaller devices.

To ensure that valid data is used in a case:

A. The data fits the business logic. Valid data must align with the business rules and logic of the application, ensuring that the data used in case processing is appropriate for the business context.

C. The data is the correct field type. Having data that is of the correct field type is fundamental to ensuring that the application processes and stores information accurately. This includes ensuring that dates, numbers, text, and other data types are used in their respective fields appropriately.

To manage the progression of a Visa application case type, contingent upon the resolution of an Interview child case:

B. Following the Create Case step, add a Wait step that pauses the parent case until the Interview reaches the Resolved status. This approach is ideal for ensuring that the main Visa case does not proceed until the Interview child case is fully resolved, aligning the case progression with the actual completion of necessary procedural steps, thus maintaining process integrity and dependency.

When configuring mobile app channels for ABC BankCorp's Transaction Dispute application to accommodate GloboBank and LocalBank, certain requirements directly influence the need for separate channels due to differing functionalities or branding.

• B. Customers can create only dispute cases, while CSRs can also create fraud report cases: This requirement indicates a functional difference between the apps intended for customers and CSRs. The ability of CSRs to handle additional case types (fraud report cases) necessitates a tailored app configuration to support these distinct functionalities, likely leading to the need for separate app channels for customers and CSRs.
• C. Mobile app color palette is customized for each subsidiary: The requirement for subsidiary-specific branding, including color palettes, directly impacts the app's UI design. To maintain distinct brand identities for GloboBank and LocalBank within the app, separate mobile app channels would be required to accommodate the different branding elements for each subsidiary.

Supporting both phones and tablets (A) and customizing currency units and date/time format according to the user's locale (D) are requirements that can typically be met within a single mobile app channel through responsive design and localization features, and thus do not inherently require multiple app channels.

Certain updates require the capabilities of Dev Studio because of their complexity and the need for custom configuration:

D. A new confirmation view displays a read-only text property. Creating and configuring new UI components, particularly those that involve specific behavior such as displaying read-only properties, typically necessitates using Dev Studio. This environment provides the necessary tools and features to design and implement detailed user interface requirements.

Grouping a set of existing actions into a multistep form as per a stakeholder's request involves adding new functionality or modifying the existing functionality of an application. This type of change request is best captured as a User Story in Agile Workbench.

• D. User Story: User stories are a way to document specific requirements or changes in an agile development environment. They focus on the value or outcome of the change from the perspective of the end-user or stakeholder. In this case, creating a user story allows for the clear articulation of the stakeholder's preference for a multistep form, including the rationale and the expected benefit, facilitating prioritization and implementation during the development cycle.

Bugs (A) are used to report issues or errors in the existing application functionalities. Feedback (B) can capture general comments or suggestions but lacks the structured approach of a user story for implementing new features or changes. Status (C) is not a work item but an attribute used to track the progress of items like bugs, feedback, or user stories.

Given the updated business requirement allowing the parent Accident Claim case to continue independently of the status of the child cases:

D. Configure the step so that users can continue with the parent case process regardless of child case status. The Wait step previously used to pause the parent case should be removed or configured to not halt the parent case processing, thereby permitting the parent case to proceed without dependency on the child cases' progress or resolution. This change reflects the new requirement for the parent case to operate independently from the Vehicle Damage (VD-001) and Body Injury (BI-001) child cases.

To fulfill the requirement that all managers must be able to view the Employee vacation requests report in their Manager portal dashboards, the report must be made readily accessible in a manner that integrates seamlessly with the existing portal structure.

• D. Add the report to a public category, and then add the out-of-the-box Reports landing page to the portal: This approach ensures broad accessibility by placing the report within a public category, making it available to all managers. Integrating the Reports landing page into the portal provides a centralized location for managers to access this and potentially other relevant reports directly from their dashboard, enhancing the usability and efficiency of the portal.

Creating a new landing page (A) specifically for the new report may not be necessary if the existing Reports landing page structure can accommodate the report, and it may introduce unnecessary complexity. Adding a report widget and publishing it to the default (B) or without specifying the target audience (C) might not ensure the report's visibility to all managers as required.