The Certified Pega Senior System Architect 23 Exam (PEGACPSSA23V1)

A keyed data page is best used for data that does not change frequently and can be retrieved by a unique key. A long list of vehicle parts that rarely changes fits this criterion because the data can be cached and doesn ' t require frequent updates, optimizing performance. References: Pega Platform Help - Data Pages.

Withdrawing the circumstanced rules in the AccountOpen class is the correct action to stop using a circumstanced rule. This allows the non-circumstanced (or base) rule to be used instead without affecting other circumstanced versions of the rule for different case types. References: Pega Platform Help - Withdrawing a rule.

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 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.

A: Running the process to completion before capturing PAL readings is important because it ensures that all the necessary rule assemblies have taken place. If you measure performance without doing this, the rule assembly might skew the results by adding additional overhead.

B: Capturing PAL readings after significant changes to a process helps in identifying any performance impacts due to those changes. This allows you to compare the performance data before and after changes to assess their impact. References: Pega official documentation on Performance Analyzer (PAL).

The initial urgency is set at 20. At 5 hours, the urgency increases by 10 (total 30). At 8 hours, the urgency increases by 20 (total 50). After the deadline, the urgency increases by 20 every 2 hours, up to a limit of 5 events. By 16 hours, all 5 events have occurred, adding 100 to the urgency, leading to a total urgency of 150 (initial 20 + goal 10 + deadline 20 + passed deadline 100). References: Pega Platform Help - Service Level Agreements.

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.

On 1 June 2020, rule resolution would choose the instance of the rule that is circumstanced for Algeria, provided that the rule ' s availability is not blocked or withdrawn and the ruleset version is accessible by the operator ' s access group. The specific rule circumstanced for Algeria would take precedence over the base rule or other circumstanced rules that do not match the circumstance condition. References: Pega SSA course materials on circumstancing rules.

To report potholes through a mobile application using the Pega API, the POST/cases method would be used to submit the report case, and the GET/casetypes method would be used to access the related case type to ensure the correct case type is used for the report. References: Pega Platform API Guide.