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

To design a reporting strategy that displays the number of cases by status at the end of each month for a 12-month period, follow these steps:

Configure an Agent: Set up an agent to run at the end of each month to capture the status of all cases.

Record Data: The agent records the case statuses in a separate table specifically created for this purpose.

Reporting: Generate reports based on the data stored in this table to provide an accurate month-end snapshot of case statuses.

References:

Configuring agents in Pega

To address the requirement where users working in one application need to create cases in another application, the recommended approach is to implement Federated Case Management (FCM).

Federated Case Management: FCM allows different Pega applications to share and manage cases across multiple systems. This approach enables seamless case creation and management, ensuring that users can interact with cases regardless of the application they are working in.

Synchronization and Communication: FCM facilitates synchronization and communication between different Pega instances, ensuring that case data is consistent and accessible across the applications.

References: Pega Platform documentation on Federated Case Management.

 The decision table provided in the question lists rules for segmenting customers based on their credit score and average balance.

 For a customer with a credit score of 240 and an average balance of 35000:

The first rule checks if the credit score is >= 400 and < 600, and average balance >= 30000. This rule doesn't apply as the credit score is 240.

The second rule checks if the credit score is >= 200 and < 400, and average balance >= 20000. This rule applies since the credit score is 240 and average balance is 35000.

 According to this rule, the result is "Fair".

 Therefore, the label returned for a customer with a credit score of 240 and an average balance of 35000 is "Fair".

PegaUnit testing best practices include:

A test ruleset is placed at the top of an application's ruleset stack:

Ensuring the test ruleset is at the top makes sure that the latest test rules are executed first, which helps in isolating and testing changes effectively.

A test case groups relevant assertions together:

Grouping relevant assertions in a test case ensures that related conditions are checked together, providing a more comprehensive and organized test output.

A test case focuses on a single area of functionality:

Focusing on a single area of functionality per test case simplifies testing and debugging. It ensures that each test case is specific and clear in its purpose.

References:

Pega Documentation on PegaUnit Testing: PegaUnit Testing

Pega Documentation on Best Practices for Testing: Testing Best Practices

This comprehensive approach ensures that all the answers are verified and supported by references to Pega Lead System Architect documentation.

Switch Application When Modifying Rules:

Ensure that developers switch to the appropriate application context when making changes to avoid conflicts.

Use Pega's application switcher to toggle between the Quoting and Policy Administration applications as needed.

Perform Branch Reviews:

Conduct regular branch reviews to ensure that changes are correctly merged and validated.

Use Pega's branch review tools to facilitate this process and minimize conflicts.

References:

Pega Academy: Best Practices for Application Development.

Pega Documentation: Branching and Merging in Pega.

Enable Auditing:

On the Rule-Declare-Decision Table RuleForm, check the option to enable auditing.

Monitor Changes:

This configuration will track changes made to the decision table in the production environment.

For processing weekly CSV files of customer insurance quotes and creating policy cases:

File Listener and Job Scheduler (D):

Use a file listener to read the incoming CSV file and feed the data into a data type.

Configure a job scheduler to read the records from the data type and create cases. This approach decouples the file reading and case creation processes, allowing for better control and error handling.

References:

Pega File Listener Configuration Guide

Pega Job Scheduler Documentation

To determine which option is always true based on the case structure, let's analyze each option:

A. Resolution of the Event Booking case requires the Parking case to be resolved.

This may not always be true unless explicitly defined in the case dependencies or resolution conditions within the application.

B. Parking, Weather, and Hotel cases must be instantiated for the Event case to process correctly.

This is not necessarily true unless the Event Booking case is designed to always require these sub-cases.

C. The Weather case can be instantiated without a parent Event Booking case.

This is always true as sub-cases can typically be instantiated independently of their parent cases. The Weather case can be a standalone case type or instantiated through other means.

D. The Parking class must inherit from the Event Booking class.

This is not always true as class inheritance depends on the application design and how classes are structured in the hierarchy.

Based on this analysis, the verified answer is:

C. The Weather case can be instantiated without a parent Event Booking case.

References:

Pega Documentation on Case Types: Case Types

Pega Documentation on Sub-Cases: Sub-Cases

When extending the data model provided by a Pega industry framework:

Specialize the data model as little as possible (Answer A):

Explanation: Minimizing specialization helps maintain compatibility with future updates to the framework and reduces the complexity of the application.

Priority Communication:Priority communications are used for urgent and important messages that need to reach all customers immediately. Configuring this type of outbound interaction ensures that the temporary contact details are promptly communicated to all customers.

Configuration Steps:

Define the priority communication in the outbound strategy.

Ensure that the message content is clear and concise.

Schedule the communication to be sent out immediately to all customers.

References:Pega Academy courses on Outbound Campaign Management explain the different types of outbound interactions, including priority communications, and their appropriate use cases.

To address the complaints from customers and prospects about receiving irrelevant offers and products, the following two Pega solutions can be implemented:

Pega Marketing: This solution helps in creating personalized marketing campaigns. By leveraging predictive analytics and customer data, it ensures that the marketing efforts are relevant and targeted. This reduces the chances of customers receiving irrelevant offers.

Customer Decision Hub: This hub centralizes the decision-making process by using real-time data and analytics to personalize interactions with customers. It helps in understanding customer needs and preferences better, thus preventing the delivery of irrelevant offers.

References:

Pega Marketing Overview

Customer Decision Hub

To avoid creating unnecessary case-related properties and views:

Work Pool Level Definitions: Define most properties and sections at the work pool level to ensure they are reusable across multiple case types. This approach reduces redundancy and simplifies maintenance.

Data Types: Create data types that correspond to the case type when necessary. This helps in organizing related data and promotes reuse.

Data Reference Field Type: Use the data reference field type in the case type's data model tab. This allows you to link to existing data types without duplicating properties, maintaining data integrity and reducing redundancy.

References: Pega Platform documentation on data modeling, work pools, and data reference field types.

 In a decision strategy, to use a customer property in an expression, you need to prefix the property with the keyword Customer.

 This ensures that the property is correctly identified and retrieved from the customer data page.

Activities and functions in Pega share certain common features which are vital for their flexibility and maintainability.

Parameterization: Both activities and functions can be parameterized, allowing them to accept input values when they are invoked. This makes them reusable in different contexts by simply changing the parameters.

Versioning: Both activities and functions support versioning. This means you can maintain different versions of an activity or function, which is useful for keeping track of changes and ensuring compatibility with different versions of the application.

References: Pega Platform documentation on activities and functions.

Custom Split-for-Each Process Step:

In the case designer, add a new step in the Processing stage where you need to create child cases.

Select the "More" option and then "Split for Each".

Configure the split to create a separate child case for each item in the page list property.

Configure Data Propagation:

Ensure that data from the parent case is propagated to each child case.

In the case designer, go to the data propagation settings and map the relevant properties from the parent case to the child cases.

Use Page List Property:

Create a page list property in the parent case to store the list of suspected fraudulent charges.

Configure the case type to iterate over this page list property when creating child cases.

References:

Pega Academy: Implementing Case Management.

Pega Documentation: Split-For-Each and Data Propagation.

Advanced Mode Configuration:

Configure the agent to run in Advanced mode to gain more control over its execution.

Periodic Pattern:

Set the agent to run with a Periodic pattern, scheduling it to execute daily at midnight.

Ensure the agent checks for customer birthdays and sends out emails accordingly.

Configure Temporary Case:

Set the case type to be instantiated as a temporary case in the starting flow. This ensures that the case is not persisted unless necessary.

Conditional Persistence:

Apply a when condition to determine whether the case should be persisted based on the comparison results. Only cases that require updates are persisted.

References:

Pega Academy: Case Type Design and Management.

Pega Documentation: Temporary Case Configuration.

Test for Completeness:

Ensure that all possible conditions and outcomes are covered in the decision rule. This involves checking that there are no missing branches or conditions that could result in an undefined outcome.

Unit Testing:

Conduct unit tests to verify that all scenarios return the expected results. This helps in identifying any gaps or missing conditions in the rule.

References:

Pega Academy: Decision Rules and Validation.

Pega Documentation: Testing and Debugging Decision Rules.

 Column Importance: The importance setting helps define which columns are displayed on smaller screens. "Primary" ensures the column is always visible, "Secondary" is shown if there is enough space, and "Other" is hidden on smaller screens.

 Restaurant Name as Primary: Setting the restaurant name to primary ensures it is always visible, as it is crucial information for making a reservation.

 Image Column as Other: Setting the image column to "Other" hides it on small screens, which is acceptable as images are non-essential compared to textual information.

 Location and Reservation as Secondary: These columns are set to secondary, ensuring they are visible on medium to large screens but can be hidden on smaller screens if space is limited.

 Reference: Pega guidelines recommend using the importance settings to manage the visibility of columns in responsive layouts, ensuring critical information is prioritized (Pega Platform 8.7 Documentation, User Interface - Column Settings).