What are three valid ways to exchange data through a Pega Web Mashup? (Choose Three)
Answer(s): A,B,E
In a Pega Web Mashup, valid ways to exchange data include using an action object configured as a script to perform additional actions on a web mashup gadget (A), utilizing the Javascript function doAction() to set or read data values through the hosting web page (B), and using the data-pega- event-onpagedata attribute to configure default values for the gadget (E). These methods facilitate dynamic interaction between the mashup and the hosting web page, allowing for seamless data exchange and integration of Pega functionalities into external web applications.
Pega Community documentation on Pega Web Mashup and integration techniques.
Which two statements are valid about configuring Pega Web Mashup? (Choose Two)
Answer(s): A,B
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.
Pega Community documentation on Pega Web Mashup configuration and security best practices.
Which three items are generated and displayed in the compliance score of an application? (Choose Three)
Answer(s): A,D,E
The compliance score of an application in Pega Platform includes items such as rules with unjustified warnings in the application (A), rules with warnings in the application (D), and the percentage of compliant rules in the application (E). These metrics provide insights into the application's adherence to best practices and guardrails, highlighting areas that may require attention to improve application quality, maintainability, and performance.
Pega Community documentation on Application Quality Dashboard and compliance scoring.
What is the purpose of the Policy Verification landing page when configuring a security solution in Pega Platform?
Answer(s): A
The purpose of the Policy Verification landing page in Pega Platform is to test if a user has the required access to a case (A). This tool allows administrators and developers to verify access control policies by simulating how the policies would apply to different users, ensuring that the security configurations align with the application's requirements and that users have appropriate access levels to cases and data.
Pega Community documentation on security policies and Policy Verification tool.
In a hiring case type, only HR Managers should have read access to a candidate's reference letter attachment. Which two tasks are used to fulfill this requirement? (Choose Two)
Answer(s): B,C
To ensure that only HR Managers have read access to a candidate's reference letter attachment, the tasks involved include restricting read access according to a When condition (B) and configuring attribute-based access control on the Attachment Category (C). The When condition can specify criteria that must be met for the attachment to be accessible, such as the user's role being an HR Manager. Attribute-based access control allows for the definition of access rules based on attributes of the data or user, providing a flexible and granular approach to securing sensitive attachments like reference letters.
Pega Community documentation on attachment security and attribute-based access control.
Post your Comments and Discuss Pegasystems PEGACPSSA23V1 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PEGACPSSA23V1 content, but please register or login to continue.