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

Kubernetes is a powerful orchestration platform for managing containerized applications across a cluster of machines. The two statements that are true about Kubernetes capabilities are:

Auto Scaling Pods Up and Down (C):

Kubernetes can automatically scale the number of pods up or down based on the resource usage and demand. This is done using the Horizontal Pod Autoscaler, which adjusts the number of pod replicas based on CPU utilization or other select metrics.

Orchestrate Pods and Their Dependencies (D):

Kubernetes orchestrates the deployment, scaling, and operations of application containers across clusters of hosts. It manages the scheduling of pods, ensuring that containerized applications are running as desired and can handle the orchestration of dependencies between containers.

References:

Kubernetes Documentation on Horizontal Pod Autoscaler

Kubernetes Documentation on Pod Lifecycle

To satisfy requirements using Skin rule customizations:

In the Skin rule, configure the importance field for each column included in a repeating layout (Answer A):

Explanation: Setting the importance field helps manage how columns are displayed on different devices, ensuring a responsive design.

 Identify and configure the right set of test suites to test early and often to identify the defects in the early stages of project life cycle:

Testing early and frequently helps in identifying and fixing defects at the initial stages, reducing the cost and effort required for fixing them later.

 Identify and configure the right set of test suites that need to run at different stages of release pipeline:

Different stages of the release pipeline require different sets of tests to ensure comprehensive testing coverage and quality assurance.

 Identify and configure the automation test suite by using Pega Platform features and industry best practices:

Leveraging Pega Platform's features and adhering to industry best practices ensures that the automated test suites are effective and reliable.

 Service Request Processor for Asynchronous Processing:

Configuring a REST service to run asynchronously using a service request processor ensures that the service runs without making the external application wait. The system returns a unique identifier instantly and processes the request in the background.

 References:

Pega's best practices for REST services and asynchronous processing recommend using service request processors for handling long-running processes.

 Therefore, the correct answer is:

B. A REST service that runs asynchronously by using a service request processor.

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 dotted line between a "Group By" component and a "Filter" component indicates:

Reference Relationship:

The dotted line shows that a property created or aggregated in the "Group By" component is being used in the "Filter" component.

This means the Filter component depends on the output of the Group By component for its logic.

Component Dependency:

It highlights a dependency where the Filter component uses data processed by the Group By component.

References: Pega Decisioning Design Patterns

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

To ensure claim processors work on the most urgent claims first, consider the following approach:

Advanced Agent: Implement an advanced agent on a dedicated node to increment the pyUrgencyAssignAdjust value by 1 for each assignment that meets the selection criteria. This agent can run at the start of each day to update the urgency of all claims in the PendingProcessing workbasket.

Dedicated Node: Using a dedicated node ensures that the urgency update process does not interfere with other application processes and can handle the large volume of claims efficiently.

References: Pega Platform documentation on advanced agents and configuring assignment urgency.

For back-to-back processing on the follow action form to ensure that getnextwork processing does not occur, configure it to "Look for the assignment to perform." This ensures that the system checks for the next assignment within the current context without moving to the next item in the work queue. References:

Pega Get Next Work Configuration: Get Next Work

In attribute-based access control (ABAC) configuration, if you need to evaluate attributes from a data page, you should use the data page as the policy condition value in the access control policy condition. This allows the system to evaluate the current value from the data page when enforcing access control rules.