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

Rule Configuration:

Set the availability of the data transform rule to "Blocked".

Testing with Previous Versions:

This allows you to save and check in the record despite validation errors and lets previous versions of the rule execute during testing.

Graphical user interface, application Description automatically generated

To avoid recalculating declarative properties when extracting data with BIX:

BIX Command Line Options:

The BIX extraction process can be configured to disable recalculating declarative properties by using specific command line options.

The options disableBackwardChaining and disableForwardChaining prevent the recalculation of declarative properties during the extraction.

Configuration:

Include these options in the BIX command line execution to ensure that declarative properties are not recalculated from their source properties during the extraction process.

References:

Pega Business Intelligence Exchange (BIX) User Guide

Pega Documentation on Declarative Rules

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.

 Field Value Rule: Field value rules in Pega are used to manage localized text for various properties. By creating a field value rule for the instruction text, you can define translations for multiple languages without altering the application logic.

 Localization Process: Use the Localization wizard in Pega to export the field values for translation. Once the translations are completed, they can be imported back into the application.

 Dynamic Display: When the application is accessed by users in different locales, Pega dynamically displays the instructions in the appropriate language based on the user’s locale settings.

References:

Pega Academy: Localizing Applications

Pega Documentation: Field Value Rules

 Personas and Channels:

Personas represent the people involved in the Microjourney, defining access roles and privileges.

Channels represent how personas interact with the application, defining the technology used for these interactions.

 References:

Pega Express delivery approach focuses on designing and delivering outcomes quickly by defining key personas and the channels they use to interact with the application.

 Therefore, the correct answers are:

F. The three pillars define Personas and Channels, as Personas represent the people that are involved in the Microjourney, and the channels represent how personas interact with the application.

A. The three pillars define Personas and Channels, as Personas represent the access roles and privileges that are required in the Microjourney, and the channels represent the technology that the personas use to interact with the application.

 Defining Greetings: In Pega, create two separate greeting messages, one for satisfied customers and one for unsatisfied customers. Each greeting should be tailored to address the specific sentiment of the customer.

 Applying When Rule: A When rule is used to conditionally execute actions based on certain criteria. Create a When rule that evaluates the customer's satisfaction status. This can be based on data points such as customer feedback scores, recent interaction history, or sentiment analysis results from their messages.

 Configuring the Response: In the process configuration for handling Facebook Messenger interactions, apply the When rule to decide which greeting message to send. This ensures that when a customer initiates a conversation, the system checks their satisfaction status and responds with the appropriate greeting.

References:

Pega Academy: Configuring Chatbots and Virtual Assistants

Pega Documentation: Using When Rules

Scenario testing in Pega is used to create UI-based, end-to-end tests for applications. The following statements are true about scenario testing:

Scenario Tests Can Include Another Scenario Test (A):

Scenario tests can be nested, allowing one scenario test to include another. This enables the reuse of common test steps and enhances the modularity of test cases.

Scenario Tests Do Not Support File Uploads or Downloads (C):

Scenario tests are designed to simulate user interactions but do not support file uploads or downloads as part of the test execution. This limitation ensures tests focus on UI interactions and business logic.

Scenario Tests Support the Setup or Cleanup of Test Data (E):

Scenario tests allow for the setup or cleanup of test data before or after the test execution. This capability ensures that the test environment is correctly prepared and that any test data is appropriately managed.

References:

Pega Scenario Testing Guide

Pega Platform Test Automation Documentation

Summarize Function with Filter Condition After Aggregation:

Using a report with a summarize function on Quantity and a filter condition applied after aggregation ensures that the report accurately displays categories with more than 5 items ordered.

References:

Pega documentation on report definitions and aggregation functions outlines how to apply filters after summarizing data to meet reporting requirements.

Therefore, the correct answer is:

C. A report with a summarize function on Quantity and filter condition Sum (Quantity) > 5 that the system applies after aggregation.

For matching the requirements with the correct components, the answers are as follows:

Determine target budget to retain a customer

Component: Decision table

Explanation: A decision table is used to define and evaluate multiple conditions to determine outcomes, such as calculating a target budget based on various customer attributes.

Divide customers into risk segments

Component: Scorecard

Explanation: A scorecard assesses and scores customer attributes to classify them into different risk segments, such as low, medium, or high risk.

Compute sum of profit

Component: Group By

Explanation: The Group By component aggregates data to compute sums, averages, and other statistics, such as the sum of profit across customer segments.

Determine customer credit score

Component: Scorecard

Explanation: A scorecard is used to calculate a customer's credit score by evaluating various financial and behavioral attributes.

Step by Step Comprehensive Detailed Explanation with References:

Decision Table:

Use Case: Decision tables are used to evaluate multiple conditions and determine an appropriate action or value. They are suitable for calculating budgets where multiple criteria need to be considered.