Pegasystems PEGACPSSA23V1 Dumps - Pass the Certified Pega Senior System Architect 23 Exam in 2026

Managing encrypted data in Pega Platform comes with certain limitations, one of which is that encrypted properties cannot be referenced using filter conditions in reports (A). This is because the encryption obscures the actual value of the property, making it impossible for the reporting engine to perform comparisons or filtering based on the encrypted data. This limitation is essential for maintaining data security, as it prevents unauthorized access to sensitive information through report queries. Reference: Pega Community documentation on encryption and reporting.

To allow both doctors and nurses to modify cases while complying with the identified security requirements, the best approach is to create a single access role for both doctors and nurses (C) and set the modify action to 5. This configuration grants both user groups the necessary permissions to modify cases throughout the case life cycle. By using a single access role with a high level of access for modifications, the application simplifies role management while ensuring that both doctors and nurses can perform their duties effectively, without compromising the security and integrity of patient cases. Reference: Pega Community documentation on Access Role to Object and case management best practices.

To fulfill orders received during the peak season in December and process the orders in batches multiple times a day, you would create a queue processor that can process orders received by the company. Queue processors are designed to handle asynchronous, high-volume processing, which is suitable for the described use case. Reference: Pega official documentation on queue processors.

Controlling access to an attachment category can be achieved through various configurations. Using a When condition like 'IsCurrentStageTesting' (A) allows for dynamic access control based on the case's current stage, enabling attachments to be accessible only under certain conditions. Assigning privileges, such as 'DeleteOwn' (C), to users enables fine-grained control over actions users can perform on attachments, such as deleting their own attachments, thus enhancing security and compliance with business rules. Reference: Pega Community documentation on attachment categories and access control.

To satisfy the requirement that users assigned the role 'Manager' can edit objects related to any studio work, the Access of Role to Object (ARO) record should be configured at the 'UPlusMusic-Production-Work-Studio-' level (C). This level is the common parent class for all studio-related work, such as Recording and Editing. By setting the ARO at this level, it ensures that managers have the necessary permissions to edit any object that falls under the studio work hierarchy, without having to set permissions at each individual subclass level. Reference: Pega Community documentation on class hierarchy and Access of Role to Object configuration.