PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

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

Using a data page with a predefined key enhances performance by leveraging the caching mechanism of Pega. When a data page is loaded with a specific key, it is stored in memory. Subsequent accesses to the data page with the same key do not require fetching the data again from the external data source, significantly reducing the access time. This approach is particularly beneficial in cloud deployments where network latency can impact performance. It ensures that once the data for a particular customer is fetched and stored in the cache, accessing the same customer's information again is much faster, addressing the performance issue reported.References: Pega Community documentation on data pages and performance best practices.