PEGACPLSA88V1 Pegasystems Certified Pega Lead System Architect (CPLSA) Exam 8.8 Free Practice Exam Questions (2025 Updated)

To help users find rules from the BCO-Data-Quote class when working in APP Studio, follow these steps:

Relevant Records: By selecting each rule you want to reuse as a relevant record, you make these rules available and easily accessible in APP Studio.

Configuration: In the application, configure the data type and select the necessary rules as relevant records, ensuring that these rules are visible and usable in the required contexts.

References:

Using relevant records in App Studio

To restrict the ability to withdraw a case to specific users, the following rule types can be used in combination:

Access When (Answer B):

Explanation: An Access When rule can be created to conditionally grant or deny access to the withdraw action based on the user's role and whether they are the creator of the case or a work group manager.

To implement the business requirement for risk segmentation using age and credit score:

Create a decision table that defines the risk segmentation rules.

Add this decision table to a decision strategy.

Pass the customer's credit score as a parameter to the decision table to determine the appropriate risk segment.

Text, letter Description automatically generated

 Indexing: Adding indexes to columns involved in equality comparisons can significantly improve query performance by reducing the need for full table scans.

 Implementation: Identify the columns frequently used in WHERE clauses and create indexes for these columns in the database. This optimization reduces query execution time and enhances overall application performance.

References:

Pega Academy: Database Optimization Techniques

Pega Documentation: Indexing Database Tables

 Automated Pega Unit Tests:

Having new team members create and run automated Pega unit tests against their rules ensures that they adhere to best practices and catch errors early.

 Rule Check-In Approval Process:

Using the rule check-in approval process allows for a review of changes made by new team members, ensuring that all rules meet the required standards and best practices.

 References:

Pega best practices for rule management and team collaboration recommend these approaches to maintain code quality and adherence to standards.

 Therefore, the correct answers are:

A. Have new team members create and run automated Pega unit tests against their rules.

C. Use the rule check-in approval process to review the changes that the new team members make.

Retention:Retention strategies focus on keeping existing customers and preventing churn. Next-Best-Action can help identify at-risk customers and offer personalized incentives to retain them.

Service:Enhancing customer service by providing personalized and relevant recommendations can improve customer satisfaction and loyalty. Next-Best-Action helps in suggesting the best service actions based on customer data and context.

Collections:In collections, Next-Best-Action can be used to determine the most effective strategies for recovering debts, such as personalized payment plans or reminders.

References:Pega Customer Decision Hub documentation on business issues highlights the importance of Retention, Service, and Collections in decisioning strategies.

When defining an embedded list property with a specific data type:

Changing pxObjClass at Runtime (A):

The pxObjClass of any page within the .Loans list can be modified at runtime. This provides flexibility to change the class of individual pages if needed.

Inheritance and Calculation (C):

Extending the data model, such as a car loan application extending MyCo-Data-Loan-Auto, does not impact aggregate functions like sum performed on properties (e.g., .Loans().Amount).

Class Consistency within the List (E):

All pages within the .Loans list must adhere to the same class type, ensuring consistency and correct behavior of operations on the list.

References:

Pega Data Modeling Guidelines

Pega Clipboard and Page Management Documentation

To configure a process where three physicians can independently perform evaluations and ensure that only two evaluations are necessary to advance the case to the medical director, you should use the "Some" join condition in Pega.

Understanding Join Conditions in Pega:Pega provides various join conditions to handle subprocesses. The join conditions include "Any," "Some," and "All." These conditions dictate how and when the main process can proceed based on the completion of subprocesses.

Some Join Condition:The "Some" join condition allows the main process to advance once a specified number of subprocesses have been completed successfully. In this scenario, since only two out of the three physicians need to complete their evaluations for the case to move forward, the "Some" join condition is appropriate.

Configuration Steps:

Step 1: Define the subprocesses for the physicians' evaluations.

Step 2: Use the "Split For Each" shape to create multiple subprocesses.

Step 3: Configure the "Some" join condition and set the number of required completions to 2.

Step 4: Ensure that the main process waits for two evaluations before moving to the medical director review.

References:Pega Documentation on Join Conditions provides detailed steps and examples for configuring different join conditions, including the "Some" join condition.

Regarding inbound email processing:

An incoming email reply is linked to its original case by the case ID in the subject of the email (Answer A):

Explanation: The case ID in the subject line allows the system to match the incoming email with the existing case, ensuring proper tracking and processing.