PEGACPSA23V1 Exam Dumps - Certified Pega System Architect

Calculated fields in Pega are used to compute values based on other data elements within the application, suitable for:

A. A sales representative wants to quote the cost of an insurance policy based on selected coverage options. Calculated fields can dynamically compute the total cost of an insurance policy as different coverage options are selected, providing real-time pricing information.

C. A project manager wants to estimate the cost of painting a banquet hall based on labor and materials required. Similarly, calculated fields can be used to aggregate costs of materials and labor to provide an overall estimate for a project, facilitating budget management.

To meet the requirement that loan applicants must enter their annual salary and that the application process diverges based on whether the salary is above or below a qualifying threshold, the configuration options chosen must efficiently manage the conditional logic and user interaction.

• A. Design a user view with an annual salary field and a data relationship for cosigner information: This approach efficiently handles the collection of applicant salary information and conditional display of cosigner information fields. A visibility condition based on the annual salary ensures that additional cosigner information is requested only when necessary, streamlining the application process for those above the threshold.
• B. Use a collect information step with an annual salary field. Use a decision shape to determine whether to advance to a step to enter cosigner information or complete the process: This configuration leverages the process modeling capabilities in Pega, where a decision shape dynamically directs the flow of the application based on the salary entered. It succinctly captures the requirement's logic, ensuring applicants are either promptly approved or directed to provide cosigner details, as appropriate.

Option C proposes an optional action for collecting cosigner information, which might not strictly enforce the requirement for applicants below the salary threshold. Option D, involving manual review by a loan officer, introduces potential bottlenecks and departs from the requirement for automatic approval based on salary.

For a purchase request case type where requests should automatically go to a manager of an employee, the most straightforward configuration is to design a step within the case lifecycle that specifically routes the case to the manager. This routing logic ensures that once an employee submits a purchase request, it is automatically forwarded to their manager for approval, streamlining the workflow and enforcing organizational approval hierarchies.

To construct a decision table for recommending a moving vehicle based on the number of bedrooms in the customer's current living space and whether heavy furniture is being moved, the decision table needs to account for these input parameters and provide a corresponding recommendation.

• A. Create a column for the recommended moving vehicle: This column will hold the output of the decision table, which is the type of moving vehicle recommended based on the input criteria. This setup allows for a clear and direct presentation of the recommendation to the customer.
• D. Create two columns, one for the number of bedrooms and one for whether the customer is moving heavy furniture: These columns will serve as the input conditions for the decision table. By evaluating the values in these columns, the decision table can determine the appropriate moving vehicle recommendation for each unique set of circumstances.

Creating rows for the recommended moving vehicle (B) would not follow the conventional structure of a decision table, where rows typically represent different rule conditions or scenarios rather than outcomes. Creating two rows, one for each input condition (C), misunderstands the structure of decision tables, where conditions are represented as columns and individual scenarios or rule conditions are represented as rows.

Configuration options for a mobile app channel in Pega focus on enhancing user experience and security specific to mobile environments:

A. Define security behavior for a mobile app such as biometric identifiers. This option allows for the integration of advanced security features, like biometric authentication, enhancing user security and data protection in mobile applications.

C. Define the UI behavior for each view in a case type when the case is displayed on a mobile device. Customizing how user interfaces behave on different mobile devices ensures that the app is responsive and provides an optimal user experience, adapting dynamically to various screen sizes and orientations.

The Localization Wizard in Pega is designed to facilitate the localization of various rule types that involve user-facing text:

B. Paragraph. Paragraph rules, which contain blocks of text used in user interfaces, are often localized to cater to different languages, making them accessible and understandable to users in various regions.

C. Correspondence Fragment. Correspondence fragments are parts of larger correspondence templates and typically contain text that needs to be presented in the user's language, making them crucial candidates for localization using the wizard.

To ensure that a list of hotels refreshes dynamically based on changes to check-in or check-out dates in a hotel reservation application, configuring action sets on these date fields is the correct approach. Action sets can be set to trigger a specific response, such as refreshing a section of the form, whenever the date fields are modified by the user. This setup maintains accurate and up-to-date availability data for the user, enhancing the application's responsiveness and user experience.

To effectively test a new process for a case type and verify that the UI elements collect the expected results, utilizing scenario testing in Pega is highly recommended. This approach allows for recording a set of interactions and saving the test result, which is crucial for verifying process functionality.

• B. Create a scenario test for the case type: Scenario testing in Pega allows for the simulation of an end-to-end process, including interactions with UI elements. This tool enables the creation and execution of tests that mimic real-world user actions, ensuring that the entire process functions as intended. By creating a scenario test, you can capture and automate the testing of specific pathways through a case type, making it an essential tool for validation.
• C. Add explicit assertions on the UI elements: Assertions are conditions that you expect to be true at a certain point in your test. By adding explicit assertions to the UI elements during scenario testing, you can specify the expected outcomes or states of those elements. This ensures that not only does the process flow correctly, but the UI elements also behave and capture data as intended. Assertions provide a powerful way to validate the functionality and user interface of your application precisely.

Together, these configurations enable a robust testing framework that can simulate user interactions, verify UI behaviors, and ensure the overall functionality of the process and its fields.