Pegasystems PEGACPLSA88V1 - Certified Pega Lead System Architect (CPLSA) Exam 8.8

The out-of-memory error occurring shortly after 3:00 P.M. is likely caused by a job scheduler running on a single Web Tier node and pulling a large number of records onto a clipboard page. This operation consumes a significant amount of memory, leading to the node running out of available memory and crashing.

References:

Pega Performance: Diagnosing Memory Issues

Pega Schedulers: Job Scheduler Configuration

For implementing Dynamic Class Referencing (DCR):

VehicleDCR PageGroup (A):

Create a VehicleDCR PageGroup property where the vehicle type is used as the subscript.

Use the pyLabel property to store the class name, enabling dynamic referencing based on the vehicle type.

Implementation:

This setup allows for dynamic class referencing where different vehicle types can be managed within the same PageGroup structure, simplifying the dynamic handling of classes.

References:

Pega Dynamic Class Referencing Guide

Pega Property and Class Management Documentation

Pega's Center-out business architecture involves:

Case Management Feature (A):

Utilizing case management allows organizations to manage, automate, and improve work processes efficiently. This ensures that every step in the Microjourney®—a complete customer interaction or process—is executed correctly and consistently.

DX API Synchronization (C):

Pega's DX API helps in keeping the front-end channels and back-end logic in sync. This avoids the creation of silos, ensuring seamless and consistent interaction across different channels.

References:

Pega's Center-out Business Architecture Overview

Pega Documentation on Case Management

Pega DX API Documentation

ï‚· Responsive Layouts:

Using responsive layouts helps ensure that the application aligns well with different device screen sizes, enhancing accessibility for all users.

ï‚· Link Controls:

Using link controls instead of buttons can improve readability and accessibility, making it easier for screen readers and other assistive technologies to interpret the interface.

ï‚· References:

Pega best practices for designing accessible applications emphasize the use of responsive designs and appropriate controls to ensure accessibility.

ï‚· Therefore, the correct answers are:

B. Use responsive layouts to help align with device screen size.

C. Use link controls instead of buttons, for readability.

To address the requirement of handling tasks from both Pega and non-Pega applications seamlessly, the best approach is:

Pega Process Fabric Hub (B):

Pega Process Fabric Hub integrates multiple applications, whether they are Pega or non-Pega, providing a unified view of work. It allows users to manage tasks from different systems in a single interface, avoiding the need to switch between applications.

This approach supports a unified worklist, enhancing productivity and user experience by consolidating tasks into a single accessible place.

References:

Pega Process Fabric Hub Overview

Pega Customer Service functions as the customer interaction system of record within the enterprise architecture. It manages customer interactions and provides a comprehensive view of customer information and history, facilitating efficient and effective customer service.

References:

Pega Customer Service: Customer Interaction Management

Pega System of Record: Defining System of Record

Segment:Segments are used to define high-level criteria for identifying the starting population. Conditions related to customer attributes like income and credit score are best suited for segment definitions because they help in broadly classifying customers based on these attributes.

Monthly Income: Customers with a monthly income less than 20000 can be grouped into a segment for targeted promotions.

Credit Score: Customers with a credit score higher than 200 can also be grouped into a segment to ensure that only creditworthy customers are considered for promotions.

Engagement Policy:Engagement policies are used to refine the targeting criteria further and define rules that must be met for engagement. Conditions related to customer consent and specific financial ratios are better suited for engagement policies.

Opt-in Status: Checking if the customer is opted in to receive promotional emails ensures compliance with communication preferences.

Debt to Income Ratio: A higher debt to income ratio might indicate higher financial risk, and this should be considered before engaging the customer with offers.

Opt-out Status: Ensuring customers are not opted out of receiving credit card promotions on mobile phones is crucial for effective communication and compliance with customer preferences.

References:Pega Academy modules on Segmentation and Engagement Policies provide detailed guidance on best practices for defining and using segments and engagement policies in customer decisioning.

To populate a data page with a list of bank offices in a postal code from the REST service:

Configure a REST connector data source.

Set the Endpoint on the data source to include the postal code parameter value at the end of the URL, ensuring that the correct data is retrieved based on the provided postal code.

ï‚· Job Scheduler:

Configuring a job scheduler to record monthly case status in a separate table ensures that the data is consistently updated and available for reporting.

ï‚· References:

Pega best practices for reporting strategies recommend using job schedulers to handle periodic data collection and reporting tasks.

ï‚· Therefore, the correct answer is:

A. Configure a job scheduler to record monthly case status in a separate table and report on that table.

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.