A requirement states that the Manager role cannot open a purchase request during the Audit stage. How do you configure the case stage to satisfy this requirement?
Answer(s): B
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.
Pega Community documentation on Access When rules and stage-based access control.
DRAG DROP (Drag and Drop is not supported)Drag each security solution on the left to its appropriate use case.
Answer(s): A
To match the security solutions to their appropriate use cases:"Access of Role to Object" is typically used to specify what actions a particular role can perform on instances of a class. It would be appropriate for a use case where "Dealers can modify evaluations" since this is an action that a specific role (dealers) would be allowed to perform. "Access Control Policy" allows defining rules that enforce property and case access restrictions based on the user role and other conditions. It would be appropriate for a use case where "Customers can only view their own credit report" since this would be a restriction based on user-specific data. "Access Deny" is used to explicitly deny access to a rule or data instance. It fits the use case where "Dealers cannot run reports" because it is a restriction that prevents a specific action (running reports) for a specific role (dealers)."Access when" is a rule that defines conditions for whether certain access is allowed. It would be used in the scenario where "Dealers cannot modify orders in the Fulfillment stage" since this is a conditional restriction based on the stage of the process.Based on these explanations, here is the matched list:Access when -> Dealers cannot modify orders in the Fulfillment stage. Access Control Policy -> Customers can only view their own credit report.Access Deny -> Dealers cannot run reports.Access of Role to Object -> Dealers can modify evaluations.
What two actions must you perform to create a class join in a report definition? (Choose Two)
Answer(s): A,C
To create a class join in a report definition, you must select the type of match for key values (A) and create a prefix for the joined class (C). Selecting the type of match, such as Inner Join or Left Outer Join, determines how records from the primary class and the joined class are combined based on matching key values. Creating a prefix for the joined class helps in distinguishing properties from the joined class from those of the primary class, preventing naming conflicts and clarifying the report definition. These actions are fundamental steps in setting up class joins in report definitions to retrieve and display data from multiple related classes.
Pega Community documentation on report definition and class joins.
You are analyzing application performance and identify a data transform exceeding preferred performance parameters. Which performance tool do you use to help troubleshoot the issue?
Answer(s): C
When analyzing a data transform that is exceeding preferred performance parameters, the Performance Analyzer (PAL) (C) is the most suitable tool to use. PAL provides detailed metrics on various aspects of system performance, including CPU usage, database interactions, and rule execution times. By using PAL to analyze the performance of a data transform, you can identify specific areas where inefficiencies occur, such as excessive database reads or writes, loop iterations, or other resource-intensive operations. This insight allows for targeted optimizations to improve the performance of the data transform and the overall application.
Pega Community documentation on Performance Analyzer (PAL) and performance troubleshooting.
Which statement describes the appropriate use of the Purge/Archive wizard to address application performance?
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.
Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.
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.