PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

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.References: Pega Community documentation on class hierarchy and Access of Role to Object configuration.

• A: When using a Pega Web Mashup, leveraging the standard authentication service IACAuthentication and updating the authentication activities to match the external system's requirements is a common practice.
• D: Configuring application permissions by specifying a list of trusted domains in the application rule is important for security purposes and to control which external domains are allowed to embed the mashup. References: Pega official documentation on Pega Web Mashup configuration.

To prevent the application from using the rule in TRB-HRApps-Work-Feedback, you would save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Withdrawn". This marks the rule as no longer valid for use in the application. References: Pega official documentation on rule availability.