Free Practice Questions for Pegasystems PEGACPLSA88V1 Exam

To meet the requirement that only the work group manager can read and write purchase request cases when the total amount exceeds USD 10,000, the following configurations can be used:

Reads Access Control Policy: Use a reads access control policy with a condition that checks if the amount is less than USD 10,000. This restricts access based on the purchase request amount.

Conditional Access in Access Manager: Configure conditional access in Access Manager to allow read and write permissions for purchase request cases only when the amount is less than USD 10,000. References:

Pega Documentation on Access Control Policies: Access Control Policies

Pega Access Manager: Access Manager

Based on the volume constraints and the outbound customer segment order, let's analyze the configuration:

Volume Constraints:

Channel Constraint: SMS has a maximum limit of 2.

Action Constraint: Silver card has a maximum limit of 1.

Customer Interaction Order:

CUST-01: Action - Gold Card, Channel - Push (No constraint limits reached)

CUST-02: Action - Gold Card (Email), Silver Card (Push)

Gold Card via Email: No constraints.

Silver Card via Push: Hits the Silver card constraint (1/1).

CUST-03: Action - Platinum Card (Email), Diamond Card (SMS)

Platinum Card via Email: No constraints.

Diamond Card via SMS: SMS limit not yet reached (1/2).

CUST-04: Action - Diamond Card (Direct Mail)

Diamond Card via Direct Mail: No constraints.

CUST-05: Action - Silver Card (SMS), Diamond Card (Push)

Silver Card via SMS: SMS limit reached (2/2) and Silver card constraint already hit.

Diamond Card via Push: No action constraints remaining for Diamond Card in Push.

Since both SMS channel limit and Silver card constraint are reached by the time CUST-05 is processed, no offers are left to be applied to CUST-05.

References: Pega Documentation on Volume Constraints

Ensuring that new team members adhere to best practices can be achieved through the following methods:

Branch Review: Utilize the branch review feature in Pega, where senior team members can review the contents of the branch. This allows experienced developers to provide feedback and ensure that the new rules meet the required standards.

Branch Quality Review: Regularly review the quality of the branch to identify any rules that have guardrail warnings. Guardrails are best practice guidelines in Pega, and addressing these warnings helps maintain high-quality, robust rules.

References: Pega Platform documentation on branch development and guardrail compliance.

Queue Processors in Pega: Queue processors are responsible for asynchronous processing of queued tasks. They can be configured to run on different types of nodes.

Types of Nodes:

Web user nodes: Handle user requests.

Real-time nodes: Handle real-time processing tasks.

Background nodes: Handle background processes such as agents and queue processors.

Stream nodes: Handle stream processing and Kafka services.

Potential Root Cause: If a queue processor is not running, it is likely due to an issue with the node type that handles background processes, which are the background nodes. If the background node is down, the queue processor will not function properly.

References:

Pega documentation on node types and their functions.

Pega Platform 8.x help files related to queue processors and background processing.

Identifying the Error Flow:

When stages are altered in a case type, in-flight cases can encounter issues if they try to advance to a now-missing stage.

pzStageProblems Flow:

This flow is initiated when there are problems advancing stages due to missing or reconfigured stages.

It helps to manage and resolve issues related to stage progression.

References:

Pega Platform Case Management Documentation

Pega Academy Course on Advanced Case Design

 Extending Core Pega Classes:

Extending existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal ensures that the application adheres to standard Pega data models.

Persisting instances of these extended classes in the PegaData schema aligns with best practices for data persistence and reuse.

 References:

Pega Lead System Architect documentation on data modeling recommends extending core Pega classes to maintain consistency and leverage built-in functionalities.

 Therefore, the correct answer is:

A. Extend existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal, persisting instances of the extended classes in the PegaData schema.

 Association Rules: Association rules in Pega are used to define relationships between different classes. By creating association rules for the set of classes used in reports, you streamline the process of joining these classes in various reports.

 Simplified Reporting: When managers create reports, they can easily include the necessary class joins by leveraging these predefined association rules, thus reducing complexity and the likelihood of errors.

References:

Pega Academy: Building Reports with Association Rules

Pega Documentation: Association Rules

Graphical user interface, application Description automatically generated

For Pega Web Mashup to follow the same-origin policy, both the web application page URL and the Pega gadget URL must have the same origin, which includes the same scheme (HTTP/HTTPS), host, and port.

Configuration A and Configuration B:

Web application page URL: https://www.pega.com/MyWebApp/home.html

PEGA Gadget URL: https://www.pega.com/MyWebApp/gadgetA.html

In both configurations A and B, the scheme (https), host (www.pega.com), and port (default HTTPS port 443) are the same, which adheres to the same-origin policy.

References:

Pega Web Mashup and Same-Origin Policy