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

When designing a worldwide application, it is important to consider various factors such as the number of languages and locales, the intent to market the framework layer, and the initial deployment region. These questions help validate the consultant's recommendation by addressing key aspects of the application's architecture and deployment strategy.References:

Pega Framework and Implementation Layers: Pega Framework

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

Next-Best-Action Reevaluation:When a customer rejects an offer, Pega Customer Decision Hub reevaluates the Next-Best-Action to determine the next most relevant action for the customer. This ensures that the customer's needs and preferences are continuously considered.

Process Steps:

Capture the rejection event.

Trigger the reevaluation process.

Determine the next best offer or action based on updated customer data and context.

References:Pega Documentation on Customer Decision Hub outlines the process of handling offer rejections and reevaluating Next-Best-Actions.

 Page List vs. Page Group: In Pega, a Page List is an ordered collection of pages indexed by position (e.g., 1, 2, 3). A Page Group, on the other hand, is an unordered collection of pages indexed by a string value (e.g., "CompanyA", "CompanyB").

 Sorting Requirement: Since the requirement specifies that the list must be sorted by company stock ticker, a Page List is more appropriate because it allows for sorting and ordered iteration.

 Implementation: Use a Data Transform or an activity to populate and sort the Page List. You can use Pega's built-in sorting functions to order the list by the stock ticker.

References:

Pega Academy: Data Management with Page Lists and Page Groups

Pega Documentation: Working with Collections

 Job Scheduler with SendEmailNotification Utility:

Running a job scheduler to pull customer records matching the current date and using the SendEmailNotification utility ensures that emails are sent out at midnight. Recording failures in a data type captures the necessary error information.

 Job Scheduler with CorrNew Utility:

Using the CorrNew utility to send emails and record any exceptions in a data type also satisfies the requirement for recording email delivery failures.

 References:

Pega documentation on job schedulers and email utilities provides guidelines for implementing scheduled tasks and handling email delivery.

 Therefore, the correct answers are:

B. Run a job scheduler, and pull the customers that match the current date. For each record, invoke the SendEmailNotification utility. If any exception is received in email delivery, mark the failure in a data type.

D. Run a job scheduler, and pull the customers that match the current date. For each record, invoke the CorrNew utility. If any exception is received in email delivery, mark the failure in a data type.

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

 Dynamic Layout: This layout allows for flexible arrangements of items within the form. It supports wrapping content based on screen size, making it ideal for responsive design.

 Row Configuration: Within a dynamic layout, elements can be configured to flow like words in a sentence, wrapping to the next line as necessary. This is essential for displaying book covers in a row that adapts to different screen widths.

 Responsive Behavior: Dynamic layouts are designed to handle varying screen sizes seamlessly, ensuring that the UI remains user-friendly on all devices.

 Reference: Pega documentation emphasizes the use of dynamic layouts for creating flexible and responsive UI designs (Pega Platform 8.7 Documentation, User Interface - Layouts).

To understand the valid statements regarding the field group list:

An auto loan application can extend MyCo-Data-Loan-Auto without affecting a sum performed against .Loans.Amount:

Since MyCo-Data-Loan-Auto extends MyCo-Data-Loan, it can be included in the field group list. Calculations like sums on .Loans.Amount will not be affected as they are based on the common superclass.

All pages within the .Loans field group must be the same class, either MyCo-Data-Loan-Auto or MyCo-Data-Loan-Mortgage:

The field group list should maintain consistency in the class type for its pages. Mixing classes within the field group can lead to errors and unpredictable behavior.

A rule in MyCo-Data-Loan-Mortgage can only be referenced through .Loans if also defined in MyCo-Data-Loan:

To reference rules through the field group list, they must be accessible via the common superclass (MyCo-Data-Loan). This ensures that rules can be consistently applied across different subclasses.

References:

Pega Documentation on Field Groups: Field Groups

Pega Documentation on Class Inheritance: Class Inheritance

The Skin rule in Pega is used to define the look and feel of the application. By configuring the importance field for each column included in a repeating layout, you can control how information is displayed on different devices. Additionally, specifying the width of the sidebar on desktops ensures that the application is optimized for various screen sizes and resolutions.References:

Pega Documentation on Skin Rules: Pega Skin Rules

Navigate to Field Level Auditing:

Go to the work management landing page in Pega.

Field Level Auditing Tab:

On the Field Level Auditing tab, configure the source field with "suggested generic substitute (.GenericCode)".

This ensures both the label and property name are recorded in the history details.

Runtime Class Variability:

At runtime, the .Loans page list can contain instances of different classes (e.g., MyCo-data-Loan-Auto and MyCo-data-Loan-Mortgage).

Class Consistency:

While the page list can contain different instances, all pages must conform to the defined class structure.

Specialized Rule Reference:

Specialized rules in MyCo-Data-Loan-Mortgage can be referenced through .Loans, provided they are defined within the class hierarchy.

Enable Security Auditing:

Navigate to the Pega Platform's security settings.

Enable security auditing by configuring the security policies.

This setting will track and log any unauthorized access attempts and failed login attempts.

Configure Audit Log Settings:

Go to the "Security Policies" section under the "System" category in the Dev Studio.

Ensure that logging for authentication events is enabled. This includes both successful and failed login attempts.

Generate Reports:

Utilize the built-in reporting capabilities of Pega to create custom reports.

These reports can be configured to display logs of failed login attempts, providing visibility into unauthorized access attempts.

References:

Pega Platform User Guide on Security Policies

Pega Academy Course on Security and Access Control

Use the Optimistic Locking Option: Optimistic locking ensures that updates are handled efficiently in a multimode system without causing contention.

Override DetermineLockString: Override the DetermineLockString to use .AccountID instead of .pyID as the lock string to ensure that the correct customer account is locked during updates. References:

Pega Locking Mechanisms: Locking Mechanisms

Pega Advanced Agent Configuration: Advanced Agent Configuration

The Localization wizard in Pega is designed to facilitate the process of localizing an application. It extracts string values from various parts of the application, ensuring that all text is available for translation. It also creates field value rules for labels used throughout the application, allowing for easy updates and translations. These capabilities are crucial for maintaining a consistent user experience across different languages and locales.References:

Pega Documentation on Localization Wizard: Pega Localization Wizard

Tax Case Type and Specialization:

Create a new tax case type within the Pega Platform application to handle the independent tax processing functionality.

Utilize case type specialization to define different processes for each country. This means creating specialized versions of the tax case type based on the country property.

Country-specific Processes:

Each specialized tax case type will have its own processes tailored to the specific tax regulations and requirements of the respective country.

This allows for the flexibility to handle different tax processing rules and ensures compliance with country-specific tax laws.

Routing and Assignment:

Configure routing rules to assign the tax cases to the appropriate tax consultants based on the country.

Use decision tables or decision trees to determine the correct tax consultant for each case, ensuring that the case is handled by a consultant with the relevant expertise.

Efficiency and Maintenance:

By using case type specialization, the application maintains a clear and organized structure where each country’s tax processing logic is encapsulated within its own specialized case type.

This makes the system easier to maintain and update, as changes to tax processing rules can be made within the specific country’s specialized case type without affecting others.

 Engagement Policy Condition: This condition is used to specify the criteria that a customer must meet to be eligible for an offer, such as having an annual income above USD 150,000 for a Gold credit card.

 Implementation: In the Next-Best-Action Designer, configure the engagement policy to include an income threshold check to ensure only eligible customers receive the offer.

 Reference: Pega documentation outlines how to set up engagement policies to define conditions under which offers are presented (Pega Customer Decision Hub, Engagement Policies).

Setting the Rule security mode on the access group to Deny ensures that:

Privileged Access Only: It enforces that all rules which can specify a privilege must have a privilege assigned. This ensures that only users with the appropriate privileges can execute these rules.

Security Compliance: This setting helps in maintaining strict security compliance by not allowing default access to rules without explicit privilege checks.

References:

Pega Rule Security Mode

Next-Best-Action Configuration:

In Pega, configure the Next-Best-Action strategy to include customer lifetime value as a factor.

Set Thresholds:

Define thresholds for customer lifetime value to determine what constitutes a high-value proposition.

Prioritization Logic:

Implement logic within the strategy to prioritize actions or offers that align with high customer lifetime value.