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

Certain scenarios do not require an application server restart:

When deploying rule only hotfixes (Answer A):

Explanation: Rule-only hotfixes update rules in the application without requiring a full server restart, allowing changes to take effect immediately.

To address performance issues and ensure optimal application performance, the following actions are recommended:

Dedicated a node to background processing (Answer A):

Explanation: By dedicating a node specifically for background processing tasks (such as agents and batch processes), you can reduce the load on nodes handling user interactions, thereby improving overall performance.

ï‚· Advanced Agent: An advanced agent is used for tasks that require precise scheduling or conditional execution based on external events or conditions.

ï‚· Scheduled Service Call: Using an advanced agent to call a service every day at a specific time (e.g., 5:00 am) to get market times and record the result is a typical use case.

ï‚· Conditional Execution: Another use case for an advanced agent is to execute a trade case only when a stock reaches a certain price, which involves monitoring stock prices and triggering actions based on specific conditions.

References:

Pega Academy: Advanced Agent Configuration

Pega Documentation: Implementing Scheduled and Conditional Agents

For managing a 30-person development team located across the globe:

C. Large development instance:

A large development instance in Pega Cloud is designed to support extensive development activities for large teams. It provides the necessary resources, scalability, and performance required for a 30-person development team working globally.

References:

Pega Documentation on Pega Cloud Environments: Pega Cloud Environments

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

When designing a solution that requires customer data from multiple external systems and ensuring it is as current as possible, consider the following:

Parallel Data Loading: Use the Load-Data Page and Connect-Wait methods to load the data in parallel. This approach improves performance by reducing the time taken to gather the required customer data since multiple data sources are queried simultaneously.

System of Record (SOR) Pattern: Employ the System of Record (SOR) data access pattern to fetch the most current customer data from the external systems directly. This ensures that the data used is up-to-date and reflects the latest information available from the source systems.

References: Pega Platform documentation on data pages, Connect-Wait methods, and data access patterns.

Applicability:Applicability rules ensure that the right offers are presented to the right customers. If Anna holds a higher value card (Premier Rewards), the new Rewards card offer might not be applicable to her because it is a lower-tier product.

Configuration Steps:

Define applicability criteria for each offer.

Ensure that offers are presented based on customer profiles and existing products.

References:Pega Academy lessons on Offer Management explain the role of applicability rules in ensuring that relevant offers are presented to customers.

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