PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

To handle the unavailability of a system of record when using a SOAP connector, the most effective approach is to implement the retry logic in the connector's error handler flow. This flow can be configured to wait for a specified duration (in this case, an hour) before retrying the connection. If the system remains unavailable after the retry, the flow can then proceed to send a notification to the system administrator. This approach encapsulates the error handling logic within the connector's flow, making it reusable and maintainable.References: Pega Community documentation on connector error handling and SOAP connectors.

To ensure that the Manager role cannot open a purchase request during the Audit stage, applying an Access When record (B) is the most suitable approach. An Access When record allows for the definition of conditional logic that determines whether a specific action, such as opening a case, is permitted based on the user's role and the current context of the case, such as its stage. By configuring this rule to evaluate to false for users with the Manager role during the Audit stage, you can effectively restrict their access to purchase requests in this stage, aligning with the requirement.References: Pega Community documentation on Access When rules and stage-based access control.

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.