Certified Pega Senior System Architect (CPSSA) 23V1

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.

The rule types that you can mark as relevant records are those that are frequently referenced and are of high importance in the application. Reports (B) and Sections (D) can be marked as relevant records to easily access and modify these important rules.
References:
Pega official documentation on relevant records.

To support accessibility, it's recommended to use a calendar control that displays an entire month. This allows users who rely on screen readers or keyboard navigation to select a date without the need for precise mouse control or having to manually input the date, which can be error-prone.
References:
Pega User Interface Design Guide - Accessibility.

Field-level auditing is enabled directly on the property rule form, where you can specify that changes to the property should be audited. This ensures that any changes to the field are tracked and recorded.
References:
Pega Platform Help - Auditing.

A prerequisite for configuring a Pega Web Mashup is having a web server to test your host page. This is because the mashup will be embedded within a webpage, and testing on a web server ensures that the integration works as expected before going live.
References:
Pega official documentation on Pega Web Mashup prerequisites.

Unit tests are the first line of testing when ensuring that an integration passes data as expected. They are designed to test individual parts of the code -- in this case, the integration point with an external data source -- to confirm that it works properly in isolation.
References:
Pega Platform Help - Automated Unit Testing

The difference between using the Call and Branch methods in an activity step to invoke other activities is that Call will return to the originating activity once the called activity completes, while Branch will not return to the originating activity and will skip the remainder of it after the called activity completes.
References:
Pega official documentation on activity methods.

The primary purpose of a production ruleset is to allow rules to be updated in a production environment.
Production rulesets are designed to hold rules that business users can modify directly in a production environment without requiring a deployment from development through testing environments. This enables quick changes to be made to decision tables, correspondence, and other rule types that business users are permitted to change.
References:
Pega official documentation on ruleset types.

The Static Assembler is a Pega tool used to address rules assembly issues specifically when the server is managing a large number of rules caches. By pre-assembling rules into a static content, the Static Assembler helps in improving performance in situations where cache management becomes complex due to the volume of rules. It creates a set of static files that represents the assembled rules, which can reduce the overhead on the server during rule assembly and cache management.
References:
Pega official documentation on performance tools and best practices.