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

Content Security Policies (CSP) are defined to enhance the security of web applications by preventing the browser from loading content from untrusted sources. This helps mitigate cross-site scripting (XSS) and other code injection attacks.

Prevention of Untrusted Sources: CSPs are primarily used to specify which sources of content are trusted and can be loaded by the browser. This includes scripts, stylesheets, images, etc.

References:

Content Security Policy (CSP)

To create a report that lists all rows in Table A where the number of related rows in Table B is greater than in Table C per customer, define two subreports. One subreport counts rows in Table B relative to Table A, and the other counts rows in Table C relative to Table A. In the main report, include only rows from Table A where the Table B count is greater than the Table C count. This method ensures optimal performance by avoiding complex joins. References:

Pega Reporting: Reporting

 The Adaptive Model decision component automatically computes a property called Propensity.

 Propensity is the likelihood or probability that a particular action will result in the desired outcome.

 This property is used to rank and prioritize decisions based on predicted customer behavior.

To ensure the performance of the Pega application does not degrade over time, consider the following recommendations:

Maintain Fragmented Tables: Schedule scripts to regularly maintain and defragment tables that are frequently updated. This helps in optimizing database performance.

Purge and Archive Records: Implement purging and archiving strategies based on the company's record retention policy. This practice helps in managing data growth and ensures that the system remains performant over time.

References:

Database Maintenance

Data Archiving

To ensure that all development teams (A, B, and C) are working with the latest version of the shared rulebase, the tasks should be ordered as follows:

Team A publishes the branch to the system of record.

The system of record triggers the job on the automation server.

Automation server requests conflict detection.

The automation server merges the branch to the system of record.

Teams B and C import the application rules within their local environment.

Step by Step Comprehensive Detailed Explanation:

Team A publishes the branch to the system of record:

Explanation: Team A needs to publish their changes to the central repository (system of record) to make them available for integration and further processing.

The system of record triggers the job on the automation server:

Explanation: Once the branch is published, the system of record initiates an automated process to handle the new changes. This step triggers the automation server to start its job.

Automation server requests conflict detection:

Explanation: The automation server needs to check for any conflicts between the newly published branch and the existing codebase. This ensures that any issues are identified and resolved before merging.

The automation server merges the branch to the system of record:

Explanation: After conflict detection and resolution, the automation server merges the changes from the branch into the main codebase in the system of record.

Teams B and C import the application rules within their local environment:

Explanation: Once the merge is complete, Teams B and C can import the updated application rules into their local environments to ensure they are working with the latest version of the rulebase.

References: According to Pega’s best practices for managing distributed development teams, this sequence ensures that changes are properly integrated and conflict-free before being distributed to other teams, promoting consistency and minimizing integration issues.

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

 Standard Agent Behavior: A standard agent in Pega with auto queue management enabled will manage its own queue and handle retries automatically.

 Retry Mechanism: If a task fails, the agent sets the task status to "broken-process" and retries the task according to the specified retry settings.

 One Retry: Since the agent is set to retry once, it will automatically attempt to reprocess the task one more time before taking further action.

References:

Pega Academy: Managing Agents and Queues

Pega Documentation: Standard Agents and Queue Management

When defining a report that shows detail about each product associated within a given order case, you need to optimize the detail properties for the product in the product class. This is because the detailed information about the products is inherently part of the product class. By optimizing these properties in the product class, you ensure that the report can directly reference the necessary details without needing additional lookups or joins, thus improving performance and report accuracy.

To queue an item for a queue processor, you can use the following methods:

Queue-for-processing method: This method queues items for background processing directly within an activity. It is a straightforward way to add items to the queue.

Run in Background smart shape: This smart shape can be used within the process flow to queue items for background processing, providing an easy-to-use visual representation in the flow.

References:

Queue-for-processing method

Run in Background smart shape

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

To improve the guardrails compliance score of an application, you can perform the following actions:

Ensure keyed data classes are not mapped to pr-other where possible:

Pega recommends avoiding the use of the pr_other table for keyed data classes as it can lead to performance issues and complicate data retrieval.

Instead, ensure that keyed data classes are mapped to dedicated tables. This enhances data management and improves compliance with Pega’s best practices.

Convert activities that only retrieve data to data transforms that invoke data pages:

Activities in Pega can be complex and harder to maintain. When activities are only used to retrieve data, it’s better to convert them to data transforms that call data pages.

Data pages are reusable and declarative. They help in maintaining consistency and reducing the complexity of the application.

References:

Pega Documentation on Data Classes: Data Classes

Pega Documentation on Data Pages and Data Transforms: Data Pages

To create custom workspaces for different user roles and display custom formatted properties:

Separate Portals and Harnesses: Define separate portals, harnesses, and sections for each access group (managers and customer service representatives). This approach allows you to tailor the user interface and functionality according to the specific needs of each role.

Specialty Components and XML: Use Specialty Components to create custom formats for properties. XML can be used to pass data in and out of these components, allowing for complex and specialized data handling.

References: Pega Platform documentation on portals, harnesses, and using Specialty Components with XML.

Create Decision Table:

Go to Records Explorer > Decision > Decision Table.

Create a new decision table that evaluates LDAP attributes (role and application properties) and maps them to access groups.

Authentication Mapping Configuration:

Go to Designer Studio > Security > Authentication Service.

In the mapping tab, configure the authentication service to evaluate the decision table created.

Testing:

Test the configuration by logging in with different users and verifying that the correct access group is assigned based on the LDAP attributes.

References:

Pega Academy: Authentication and Access Control.

Pega Documentation: Decision Table and LDAP Integration.

Graphical user interface, text, application Description automatically generated

Identifying and resolving out-of-memory errors in a cluster node involves understanding the alerts that typically precede such conditions.

PEGA0004 – Quantity of data received by database query exceeds limit (Answer A):

Explanation: This alert indicates that a database query is returning more data than expected, which can lead to memory issues as the system tries to handle large data sets.

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

To configure a data page that accepts either a postal code or a city name as a parameter and calls the appropriate REST connector:

Use separate REST connectors for each parameter type and a when rule to determine which connector to use based on the input parameter.

Alternatively, use an activity to evaluate the parameter and dynamically select the appropriate REST connector at runtime.

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.

To populate a data page with a list of bank offices in a postal code from the REST service:

Configure a REST connector data source.

Set the Endpoint on the data source to include the postal code parameter value at the end of the URL, ensuring that the correct data is retrieved based on the provided postal code.