PEGACPSSA23V1 Exam Dumps - Pegasystems Certified Pega Senior System Architect Questions and Answers

An association rule differs from a class join in that it is a reusable rule that can be used by anyone with appropriate permissions when creating reports. This makes it available across multiple reports. Class joins, on the other hand, are specific to each report definition and are not reusable in the same way. References: Pega Reporting Guide - Associations vs. Joins.

To copy items selected by a user to a page list property when the user submits the form, add a data transform to the flow action as a post-processing action (A). Post-processing actions occur after the user submits the form, making it the right moment to transfer the selected items into the page list property for further processing or storage.References: Pega Community documentation on data transforms and flow action post-processing.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.References: Pega Community documentation on SLAs and urgency calculation.

Sixteen hours after the case reaches the assignment, the assignment urgency is calculated as follows: Initial urgency (20) + Urgency after goal (10) + Urgency after deadline (20) + Urgency after passing the deadline (2 hours passed, urgency increases by 20, and this event repeats for the limit of 5 times, so 20x5=100). Adding these together: 20 + 10 + 20 + 100 = 150. However, since none of the options matches this calculation, there might be an error in the given options or a misinterpretation of the question. Based on the provided options, 90 would be the closest, indicating a possible oversight in the question. References: Pega official documentation on Service Level Agreements (SLAs) and urgency calculations.

• A: Configuring a data transform to apply the Open-Review status on the appropriate assignments can be used to change the status of a case when it is assigned to a user for review.
• D: Apply the Open-Review status to the appropriate assignments directly within the flow where the assignment is configured. References: Pega official documentation on case statuses and data transforms.

When deploying mashup code in a webpage, it is necessary to add the host URL in the Pega application to ensure that Pega Platform accepts incoming requests. This is part of configuring the trusted origins within the application's settings. References: Pega official documentation on Pega Web Mashup deployment and configuration.

The purpose of the Policy Verification landing page in Pega Platform is to test if a user has the required access to a case (A). This tool allows administrators and developers to verify access control policies by simulating how the policies would apply to different users, ensuring that the security configurations align with the application's requirements and that users have appropriate access levels to cases and data.References: Pega Community documentation on security policies and Policy Verification tool.

In Application Settings, you can specify different values for production levels using text (e.g., URLs, file paths) or picklists (for selecting from predefined options). These settings allow for easy adjustment of values according to the environment the application is running in. References: Pega Platform Help - Application Settings.

To enable the attending doctor to update the Patient visit case while the Lab analysis and Diagnostic imaging child cases are active, the following configurations are necessary:

• A: Configuring the Patient visit case type to allow multiple users ensures that more than one user can work on the case simultaneously, which would allow the doctor to update the case with notes even while the child cases are in progress.
• B: Configuring the Lab analysis and Diagnostic imaging case types to allow other users to open the parent case type ensures that opening the child cases does not lock the parent case, allowing the doctor to make updates concurrently. References: Pega official documentation on case type configuration and locking strategies.

Rule resolution will choose the rule that is most specific to the circumstances of the case. Since the country is set to Japan, the rule resolution algorithm will choose the rule version that is circumstanced for Japan. Among the options, 01-01-02 is the circumstanced rule that matches the country condition of Japan and would be selected over the base rule and any other versions. References: Pega Platform Help - Rule Resolution.