PEGACPSA23V1 Exam Dumps - Certified Pega System Architect

To ensure the validation that the 'Date account opened' is indeed in the past for a loan application:

B. Use a validate rule to verify the Date account opened is in the past. Validate rules in Pega are used to enforce data integrity and accuracy, making them suitable for verifying that a date entered is before the current date. This method ensures that data meets the business requirement directly and effectively.

In Pega applications, work parties represent entities associated with a case. When configuring status updates for patients who are not users of the application, it is essential to use a class that accurately represents external individuals.

• A. Data-Party-Person: This class is designed to represent individual people as parties in a case. Using this class to create a work party for a patient allows the application to store relevant personal information and contact details necessary for sending status updates about medical test processing. Since patients are the recipients of the information and not operators or organizational entities within the system, this class is the most appropriate choice.

The other options, such as Data-Party-Operator (used for application users), Data-Party-Org (used for organizations), and Data-Party-Com (used for commercial entities), do not fit the context of individual patients receiving updates.

The Estimator tool in Pega is used for planning and sizing development efforts, particularly for Minimum Lovable Products (MLP):

B. MLP sizing leads to precision in the sprint cycle and resource planning. Accurate MLP sizing helps in detailed planning of sprint cycles and resource allocation, ensuring that development efforts are aligned with project goals and timelines.

D. Initial estimations are high-level and can be refined during sizing. Early estimations in the project are often broad and generalized but become more refined and accurate as the project sizing process progresses, allowing for better project planning and management.

The scenario describes a series of actions related to managing a job application process. Proper naming of steps in a business process is crucial for clarity and effective communication. The step "Schedule Interview" directly reflects the action of setting up the date and location for the interview, while "Notify Candidate" describes the action of sending an email confirmation to the candidate. These names are clear, action-oriented, and specific to the tasks being performed, aligning with best practices in business process modeling.

To write a single page of data to a single database row in the configured system of record:

D. Database save. A database save operation is used to persist data from a Pega data page into a database. It matches the structure of the data page to the corresponding database table structure and writes the data to a new row, fulfilling the requirement to synchronize a page of data to the database.

For automating the advancement of university admission application cases based on standardized test scores, the correct configurations would be:

A. Configure a process with a decision shape that continues if the TestThreshold configuration setting is less than the applicant’s test score. This configuration directly supports the requirement by placing a decision shape in the process that compares the applicant's test score against a pre-configured threshold. If the score exceeds the threshold, the case advances, automating the workflow based on performance.

D. Configure a TestThreshold Configuration setting with the national average for the test score threshold. This option involves setting a dynamic threshold that adjusts based on the national average each year. It ensures that the decision shape in Option A has a relevant and up-to-date threshold to compare against.

Options B and C are incorrect because B involves calculating the average rather than setting a threshold, and C incorrectly states the comparison logic.

The combination of configuring the case type to create temporary cases and adding a Persist case step to the case life cycle is appropriate for this scenario. Temporary cases allow users to enter and process data without immediately committing it to the database, ideal for initial checks like membership status. If the user decides to make changes (hence modifying the membership), the Persist case step can be used to save these changes and assign a case ID, thus converting the temporary case into a permanent record in the system.

For the requirement where an auditor needs to receive an email notification if the refund is greater than twice the price of the item, it's important to select a participant role that accurately reflects the auditor's involvement in the case.

• B. Interested individual: This role is designed to represent parties who need to be informed about certain events or milestones within a case but are not directly responsible for actioning the case. In this scenario, the auditor's role is to be notified under specific conditions for oversight purposes, making "Interested individual" the appropriate choice. This setup allows the application to send targeted notifications to the auditor without assigning them case responsibilities that are not part of their role.

The other options, such as Customer (Option A), Owner (Option C), and Work queue (Option D), do not accurately represent the auditor's role in relation to the specific notification requirement.