Free Pegasystems Certified Pega Senior System Architect 23 Exam PEGACPSSA23V1 Exam Questions

To enable property-level encryption for sensitive data such as SSN and Account Number, you create an Access Control Policy of type PropertyEncrypt. This policy specifies which properties should be encrypted and how the encryption should be applied. Reference: Pega Platform Help - Access Control Policies.

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. Reference: Pega official documentation on Service Level Agreements (SLAs) and urgency calculations.

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. Reference: Pega official documentation on Performance Analyzer (PAL).

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. Reference: Pega User Interface Design Guide - Accessibility.

In Access Control Policies, attributes like Appointment date (A) and Number of dependents (B) can be used to define conditions for data access. These attributes can be part of case data or user profiles and serve as criteria for determining access levels. For example, an access control policy can restrict access to certain case information based on the appointment date or allow access to specific functionalities based on the number of dependents associated with a user profile. Reference: Pega Community documentation on Access Control Policies.

To ensure that the advisor and the student can simultaneously edit the draft proposal, configure the locking on the case type to allow multiple users (B). This setting enables a shared access model, where multiple users can work on the case at the same time. Additionally, Pega's conflict resolution mechanisms can be utilized to check for changes before committing them to the database, ensuring that any concurrent edits are properly managed and the integrity of the proposal is maintained. Reference: Pega Community documentation on case locking and concurrent editing.

Dedicating and classifying a node for the job scheduler allows the job scheduler to run on a node that is optimized for batch processing. This ensures that resource-intensive jobs do not impact the performance of the user nodes, thus maintaining peak performance at all hours. Reference: Pega Platform Help - Job Schedulers.

To ensure that the values are only initiated once for each flow action, add logic to the pre-processing data transform to test if the values were already initiated (A). This logic can prevent the reinitialization of values that have already been set, allowing the pre-processing to only set default values when they are not present, avoiding any unwanted overwrites or duplications of effort. Reference: Pega Community documentation on data transforms and flow action pre-processing.

To ensure that the correct pattern is entered for a part number field, configure an edit validate rule and reference it from the property rule for the field. The edit validate rule can be set up to check that the first two characters are letters and the last four are digits. Reference: Pega official documentation on property rules and edit validate rules.

The Purge/Archive wizard in Pega Platform is appropriately used to remove old cases to reduce the size of a database table (B). Over time, completed or resolved cases can accumulate in the system, leading to large table sizes that can negatively impact application performance. By archiving these cases, you can move them out of the primary database tables into an archive, and by purging, you can delete cases that are no longer needed. This process helps maintain optimal database performance and manage storage costs effectively. Reference: Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.