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

To use customer properties like income and age in a Filter component:

Direct Access:

Customer properties such as income and age are directly available for use in decisioning components.

There's no need for additional components to enable access.

Using the Filter Component:

Simply drag and drop the Filter component into the decision strategy.

Use the customer properties directly in the filter logic (e.g., Customer.Income > 50000).

This is because Pega Customer Decision Hub typically provides direct access to commonly used customer properties.

References: Pega Decision Strategy Documentation

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

Define Privilege:

Create a privilege specific to the section containing personal data.

Assign Privilege:

Assign this privilege to roles associated with managers in the HR organization.

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

Single Advanced Agent Configuration:

Create a single advanced agent and configure its schedule based on the server's local time zone.

Modify Agent Schedule:

For the Eastern US server, set the agent schedule to the Eastern US time zone.

For the India server, adjust the agent schedule to the India time zone.

Time Synchronization:

Ensure that both servers' clocks are synchronized using a standard time protocol to maintain consistent execution times.

The system will consider the assignments with urgency value equal to and greater than the specified value in the Operator rule. Once all assignments are processed from the work queue based on the threshold urgency value, the lower urgency assignments are then considered.

Urgency Thresholds: The system checks the urgency of assignments in each work queue. Assignments with an urgency equal to or greater than the threshold are considered first.

Get from Work Queues First: With this option selected, the system prioritizes processing work queues before considering individual workbaskets.

Lower Urgency Assignments: After processing assignments meeting the urgency thresholds, the system will then consider lower urgency assignments if there are no higher urgency tasks left.

When the GetNextWork_WorkBasketUrgencyThreshold setting is overridden, the system behavior changes as follows:

Urgency Threshold: The system will search for assignments in the work queue that have an urgency higher than the specified threshold value. This means that only the assignments meeting or exceeding this urgency level will be considered for processing.

Filtering Assignments: This filtering ensures that only the most urgent tasks are prioritized and assigned, improving efficiency and focus on critical work items.

References: Pega Platform documentation on GetNextWork and system settings.

Queue Processors in Pega: Queue processors are responsible for asynchronous processing of queued tasks. They can be configured to run on different types of nodes.

Types of Nodes:

Web user nodes: Handle user requests.

Real-time nodes: Handle real-time processing tasks.

Background nodes: Handle background processes such as agents and queue processors.

Stream nodes: Handle stream processing and Kafka services.

Potential Root Cause: If a queue processor is not running, it is likely due to an issue with the node type that handles background processes, which are the background nodes. If the background node is down, the queue processor will not function properly.

References:

Pega documentation on node types and their functions.

Pega Platform 8.x help files related to queue processors and background processing.

 Job Scheduler:

Using a job scheduler on a dedicated node is a robust solution for incrementing the urgency of claims. The scheduler can run daily to update the value of pyUrgencyAssignAdjust by 1 for every assignment in the PendingProcessing workbasket.

 References:

Pega documentation on job schedulers and background processing highlights the use of job schedulers for periodic updates and batch processing.

 Therefore, the correct answer is:

C. Use a job scheduler on a dedicated node to increase the value of pyUrgencyAssignAdjust by 1 for every assignment that matches the selection criteria.

To diagnose the cause of a reported performance issue:

Download the alert log file from each node and analyze the contents in the Pega Log Analyzer (D): The alert log contains detailed information about performance issues. Analyzing this data using the Pega Log Analyzer (PLA) helps identify the root causes of performance problems.

References:

Pega Troubleshooting: Pega Log Analyzer

Pega Performance: Monitoring and Troubleshooting