Pass the Pegasystems Certified Lead System Architect (CLSA) PEGACPLSA88V1 Questions and answers with CertsForce

Step by Step Comprehensive Detailed Explanation with References:To perform extensive analysis on work party information while minimizing impact on case workers:

Configure a reports database for the Class Group and Index WorkPartyUri Data Admm DB-Table records (B): Setting up a separate reports database helps offload reporting activities from the transactional database, reducing the load on the operational system.

Use BIX to export Case and related Work Party data to a data warehouse (D): BIX (Business Intelligence Exchange) can be used to export data in bulk to a data warehouse where extensive analysis can be performed without affecting the performance of the operational Pega applications.

References:

Pega Reporting: Using a Reports Database

Pega BIX: Business Intelligence Exchange

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 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.

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

A rule defined in myco-data-shape-rectangle can modify the .Color property because .Color is defined in the parent class (myco-data-shape) and is inherited by its subclasses.

A rule existing in myco-data-shape can be overridden in myco-data-shape-circle, allowing for specific behavior in the subclass while maintaining the inheritance structure.

To improve performance during synchronization for users of an offline-enabled mobile app, it's crucial to manage the data pages that are synchronized. Declaring large data pages in the data page whitelist ensures that only necessary data is preloaded and cached on the device, reducing the amount of data transferred during synchronization and thus improving performance.

A rule-utility-function (RUF) has the advantage of being directly callable from a decision table, which is a common requirement in Pega applications for implementing business logic. This direct invocation capability simplifies the design and execution of decision rules. References:

Pega Rule-Utility-Functions: Rule-Utility-Functions

 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

Text Description automatically generated with medium confidence

Create Access When Rule:

Go to Records Explorer > Security > Access When.

Create a new Access When rule that checks if the current user is either the primary or secondary owner of the account. Use conditions like current user = primary owner or current user = secondary owner.

Configure the Access When Rule:

Open the Account case type.

Go to the Security tab and in the Case Type rules, apply the created Access When rule to ensure that only users who meet the conditions (primary or secondary owners) can view or update the case.

Apply Access Control:

In the Access Role configuration, apply the Access When rule for read and write instances of the Account class.

Ensure that the roles assigned to the users have the necessary permissions configured.

Testing and Validation:

Test the implementation by logging in with users who are primary or secondary owners and verifying access.

Try logging in with users who are not owners to ensure access is denied.

References:

Pega Academy: Security and Access Control.

Pega Documentation: Access Control Policies and Access When Rules.