PEGACPSSA23V1 Exam Dumps : Certified Pega Senior System Architect 23 Exam

When configuring Pega Web Mashup, it's essential to create one DIV element in the hosting web page for each Pega gadget (A), ensuring that each gadget is properly isolated and rendered within its designated area on the web page. Additionally, adding a list of trusted domains in your application settings (B) is crucial for security, as it specifies which domains are authorized to host the mashup, preventing unauthorized use or embedding of the Pega functionalities in untrusted environments.References: Pega Community documentation on Pega Web Mashup configuration and security best practices.

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.

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.