Free Practice Questions for the Pegasystems Certified Lead System Architect (CLSA) PEGACPLSA88V1 Exam (2026 Updated)

To ensure that private information is secured and only visible to limited users, creating an access control policy is the recommended approach. Access control policies allow you to define specific conditions and constraints under which sensitive data can be accessed, ensuring that only authorized users can view or modify this information.

References:

Pega Security: Access Control Policies

Pega Data Security: Securing Sensitive Information

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

For Pega Web Mashup to follow the same-origin policy, both the web application page URL and the Pega gadget URL must have the same origin, which includes the same scheme (HTTP/HTTPS), host, and port.

Configuration A and Configuration B :

Web application page URL: https://www.pega.com/MyWebApp/home.html

PEGA Gadget URL: https://www.pega.com/MyWebApp/gadgetA.html

In both configurations A and B, the scheme (https), host (www.pega.com), and port (default HTTPS port 443) are the same, which adheres to the same-origin policy.

References:

Pega Web Mashup and Same-Origin Policy

Max Attempts: The maximum number of retry attempts set is 4.

Initial Delay: The initial delay before the first retry attempt is 2 minutes.

Delay Factor: The delay factor is set to 2, which means the delay doubles with each retry.

Calculating Delays:

First attempt fails, delay before second attempt = Initial delay = 2 minutes.

Second attempt fails, delay before third attempt = Initial delay * Delay factor = 2 minutes * 2 = 4 minutes.

Third attempt fails, delay before fourth attempt = 4 minutes * Delay factor = 4 minutes * 2 = 8 minutes.

Delay Between Attempts: The question specifically asks for the delay between the second and third attempt, which is calculated as 8 minutes.

References:

Pega documentation on queue processor configuration.

Pega Platform 8.x help files related to processing retries and delay factors.

To change the threshold value for the USD2000 credit limit from < 175 to < 200 in Pega Customer Decision Hub:

Locate the Scorecard Model :

Navigate to the scorecard model that calculates the customer credit score.

Modify the Cutoff Value :

Go to the Results tab of the scorecard model.

Find the condition for the USD2000 credit limit which is currently set to .pxSegment < = 175.

Change this condition to .pxSegment < = 200.

Save and Validate :

Save the changes in the scorecard model.

Validate the scorecard model to ensure it reflects the new threshold.

This approach directly modifies the threshold within the scorecard model ' s configuration.

References: Pega Customer Decision Hub Implementation Guide

Configure Temporary Case:

Set the case type to be instantiated as a temporary case in the starting flow. This ensures that the case is not persisted unless necessary.

Conditional Persistence:

Apply a when condition to determine whether the case should be persisted based on the comparison results. Only cases that require updates are persisted.

References:

Pega Academy: Case Type Design and Management.

Pega Documentation: Temporary Case Configuration.

D,B,C,A,E

 Senior Manager Role with Dependent Roles :

Creating a new Senior Manager role with Manager and Vice President as dependent roles ensures that the Senior Manager inherits access from both roles. Overriding the Access of Role to Object rules from the Vice President role as required provides the necessary fine-tuning.

 References :

Pega documentation on role-based access control recommends defining new roles with dependencies to inherit access rights and customize as needed.

 Therefore, the correct answer is:

D. Create a new Senior Manager role with Manager and Vice President as dependent roles, and override the Access of Role to Object rules from the Vice President role as required.

Use PR cipherGenerator:

Utilize the PR cipherGenerator tool to generate an encrypted password.

This can be done through Pega ' s utility tools or via command line.

Encrypt Password:

Replace the unencrypted password in the prconfig.xml file with the generated encrypted password.

Configuration:

Ensure that the encrypted password is correctly referenced in the connection information within prconfig.xml .

References:

Pega Academy: Configuration and Deployment.

Pega Documentation: Encrypting Passwords and PR cipherGenerator.

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

 Increasing Stage Upweighting : This technique involves gradually increasing the priority or weight of offers in a specific stage of the customer journey, promoting active engagement and progression through the journey stages.

 Second Stage : In the second stage, which presents available offers, enabling increasing stage upweighting ensures that offers are promoted more actively over time, enhancing visibility and uptake.

 Reference : Pega ' s customer journey framework and decision strategies documentation detail how to use stage upweighting to optimize customer engagement and offer promotion (Pega Customer Decision Hub, Customer Journey and Engagement Strategies).

Create Site-Specific Encrypting Cypher:

Go to Designer Studio > Data Model > Classes > Class Groups.

Select the class group for MyOrg-HR-Work-RFP .

In the Security section, configure the site-specific encrypting cypher.

Select Encrypt BLOB?:

Check the option Encrypt BLOB? to ensure the storage stream for the class is encrypted.

Configuration:

Ensure the encrypting cypher is correctly set up and applied to the specific class.

Validate the configuration by checking the encryption of data in the database.

References:

Pega Academy: Data Encryption.

Pega Documentation: Encrypting the Storage Stream.

Security Token Identification:

Add steps in the IAC authentication activity to identify and validate the security token provided by the external module.

Token Verification:

Implement additional steps to return the security token to the external authentication module for verification, ensuring it is the authenticating source.

PegaUnit testing best practices include:

A test ruleset is placed at the top of an application ' s ruleset stack:

Ensuring the test ruleset is at the top makes sure that the latest test rules are executed first, which helps in isolating and testing changes effectively.

A test case groups relevant assertions together:

Grouping relevant assertions in a test case ensures that related conditions are checked together, providing a more comprehensive and organized test output.

A test case focuses on a single area of functionality:

Focusing on a single area of functionality per test case simplifies testing and debugging. It ensures that each test case is specific and clear in its purpose.

References:

Pega Documentation on PegaUnit Testing: PegaUnit Testing

Pega Documentation on Best Practices for Testing: Testing Best Practices

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

To ensure consistent formatting of phone numbers and improve usability, you can use the following options:

B. Configure an Edit Validate rule:

Edit Validate rules are used to enforce specific data formats and validations. By configuring an Edit Validate rule, you can ensure that phone numbers adhere to a consistent format.

D. Configure an Edit Input rule:

Edit Input rules allow you to transform and standardize data before it is processed by the system. Using an Edit Input rule, you can automatically reformat phone numbers to a consistent format upon input.

References:

Pega Documentation on Edit Validate Rules: Edit Validate Rules

Pega Documentation on Edit Input Rules: Edit Input Rules

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.

To restrict the ability to withdraw a case to specific users, the following rule types can be used in combination:

Access When (Answer B) :

Explanation : An Access When rule can be created to conditionally grant or deny access to the withdraw action based on the user ' s role and whether they are the creator of the case or a work group manager.

To address complaints about irrelevant offers and products:

Pega Marketing (A) : This solution helps create targeted marketing campaigns and personalized offers, ensuring that customers receive relevant and timely promotions.

Customer Decision Hub (D) : This solution uses real-time analytics and decisioning to determine the best action or offer for each customer, ensuring relevance and improving customer satisfaction.

References:

Pega Marketing: Pega Marketing Overview

Customer Decision Hub: Pega Customer Decision Hub

 Declare Expression: Use a Declare Expression to calculate the sum of the columns and store the result in an additional property. This ensures that the sum is always updated when any of the contributing values change.

 Report Configuration: Configure the report to group by the columns to be summed and use the SUM function for aggregation. This approach leverages Pega’s reporting capabilities to dynamically compute and display the sum based on the selected columns.

References:

Pega Academy: Advanced Reporting Techniques

Pega Documentation: Declare Expressions and Reporting

Graphical user interface, application Description automatically generated

 Page List vs. Page Group: In Pega, a Page List is an ordered collection of pages indexed by position (e.g., 1, 2, 3). A Page Group, on the other hand, is an unordered collection of pages indexed by a string value (e.g., " CompanyA " , " CompanyB " ).

 Sorting Requirement: Since the requirement specifies that the list must be sorted by company stock ticker, a Page List is more appropriate because it allows for sorting and ordered iteration.

 Implementation: Use a Data Transform or an activity to populate and sort the Page List. You can use Pega ' s built-in sorting functions to order the list by the stock ticker.

References:

Pega Academy: Data Management with Page Lists and Page Groups

Pega Documentation: Working with Collections

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.

 Using the PropertyRead access control policy for the SSN and date of birth ensures that only users with the appropriate access (e.g., HR Manager) can view these details. This approach masks the information for other users.

 References :

Pega best practices for data security and access control recommend using PropertyRead policies to restrict access to sensitive information.

 Therefore, the correct answer is:

A. Use the PropertyRead access control policy for the SSN and date of birth.

Pega ' s Center-out business architecture involves:

Case Management Feature (A) :

Utilizing case management allows organizations to manage, automate, and improve work processes efficiently. This ensures that every step in the Microjourney®—a complete customer interaction or process—is executed correctly and consistently.

DX API Synchronization (C) :

Pega ' s DX API helps in keeping the front-end channels and back-end logic in sync. This avoids the creation of silos, ensuring seamless and consistent interaction across different channels.

References:

Pega ' s Center-out Business Architecture Overview

Pega Documentation on Case Management

Pega DX API Documentation

The optimal solution to route the mortgage case to the specialist when the credit report is complete is to add a wait shape to the mortgage flow with a case dependency. This ensures that the mortgage flow advances to the next assignment only when the credit report case is resolved. This method is straightforward and leverages Pega ' s built-in case dependency management. References:

Pega Case Management: Case Management

 Loading Customer Data in Parallel :

Using the Load-DataPage and Connect-Wait methods to load customer data in parallel ensures that the data is retrieved efficiently and concurrently from multiple sources.

 System of Record (SOR) Data Access Pattern :

Using the SOR data access pattern to reference customer data ensures that the data is always current and consistent across all child cases.

 References :

Pega documentation on data management and integration patterns recommends these approaches to maintain data integrity and performance.

 Therefore, the correct answers are:

A. Load the customer data in parallel using the Load-DataPage and Connect-Wait methods.

C. Use the System of Record (SOR) data access pattern to reference the customer data.

To format required fields with red labels using a custom style in the skin rule:

Reference the custom style in the required field labels (Answer D) :

Explanation : Applying the custom style directly to the required field labels ensures that they are formatted according to the defined style (e.g., red color).

Team A publishes branch,

Automation server merges three branch,

Team B and C rebase the application

To determine which option is always true based on the case structure, let ' s analyze each option:

A. Resolution of the Event Booking case requires the Parking case to be resolved.

This may not always be true unless explicitly defined in the case dependencies or resolution conditions within the application.

B. Parking, Weather, and Hotel cases must be instantiated for the Event case to process correctly.

This is not necessarily true unless the Event Booking case is designed to always require these sub-cases.

C. The Weather case can be instantiated without a parent Event Booking case.

This is always true as sub-cases can typically be instantiated independently of their parent cases. The Weather case can be a standalone case type or instantiated through other means.

D. The Parking class must inherit from the Event Booking class.

This is not always true as class inheritance depends on the application design and how classes are structured in the hierarchy.

Based on this analysis, the verified answer is:

C. The Weather case can be instantiated without a parent Event Booking case.

References:

Pega Documentation on Case Types: Case Types

Pega Documentation on Sub-Cases: Sub-Cases

When configuring a mobile application to function correctly while offline, it ' s essential to ensure that data used to populate drop-down lists is available offline. This requires adding the relevant data pages to the whitelist. The data pages will then be downloaded and cached on the mobile device, ensuring that drop-down lists can be populated without requiring an active network connection.

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.

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.

 Ensuring Quality with Automated Testing :

Automated testing programmatically ensures the quality of rules, maintaining the integrity of the CI/CD pipeline. This is crucial for consistent and reliable deployments.

 References :

Pega Lead System Architect documentation emphasizes the importance of automated testing in CI/CD models to ensure rule quality and pipeline integrity.

 Therefore, the correct answer is:

B. Automated testing programmatically ensures quality of rules to maintain the integrity of the pipeline.

 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

To minimize potential development conflicts and ensure that both development teams work with the most current version of the Policy Administration application, the following best practices should be followed:

Perform Branch Reviews when Merging Branches (A) :

Regularly review and validate changes made in branches before merging them into the mainline. This ensures that any conflicts or issues are identified and resolved early in the development process.

Branch reviews help maintain code quality and prevent integration problems.

Periodically Sync the Policy Administration Application Code (D) :

Synchronize the Policy Administration application code regularly to ensure that the Quoting application team is working with the latest version.

This practice helps to avoid discrepancies and ensures that enhancements and updates in the Policy Administration application are consistently reflected in the Quoting application.

References:

Pega Platform Best Practices for Branching and Merging

Pega Application Development Guide

Activities and functions in Pega share certain common features which are vital for their flexibility and maintainability.

Parameterization : Both activities and functions can be parameterized, allowing them to accept input values when they are invoked. This makes them reusable in different contexts by simply changing the parameters.

Versioning : Both activities and functions support versioning. This means you can maintain different versions of an activity or function, which is useful for keeping track of changes and ensuring compatibility with different versions of the application.

References: Pega Platform documentation on activities and functions.

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.

Using AccessGroup for conditional visibility is optimal because AccessGroups manage the user’s access to different applications and features. This approach provides flexibility and ease of maintenance, allowing changes to user roles or permissions to be managed centrally without modifying individual rules. AccessGroups encapsulate roles, privileges, and access controls, making it simpler to control UI elements based on user groups.

References:

Pega Security: Access Group Configuration

Pega UI Authoring: Conditional Visibility

Ensuring that new team members adhere to best practices can be efficiently managed through:

Have new team members create and run Pega automated unit tests against their rules (Answer A) :

Explanation : Automated unit tests help verify that rules are functioning as intended and conform to best practices. This process also aids in early detection of issues.

 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

Robotic Desktop Automation (RDA) is recommended in this scenario because it enables Customer Service Representatives (CSRs) to launch and interact with multiple applications from a single interface. RDA automates repetitive tasks and integrates different systems without requiring backend changes, making it an ideal solution for environments where applications are built on diverse technologies. This approach improves efficiency by reducing the manual effort needed to synchronize data across systems, ensuring real-time updates and data consistency.

References:

Pega Robotics: Pega Robotics Overview

Pega Customer Service: Pega Customer Service Capabilities

 Responsive Layouts :

Using responsive layouts helps ensure that the application aligns well with different device screen sizes, enhancing accessibility for all users.

 Link Controls :

Using link controls instead of buttons can improve readability and accessibility, making it easier for screen readers and other assistive technologies to interpret the interface.

 References :

Pega best practices for designing accessible applications emphasize the use of responsive designs and appropriate controls to ensure accessibility.

 Therefore, the correct answers are:

B. Use responsive layouts to help align with device screen size.

C. Use link controls instead of buttons, for readability.

When moving an application to Pega Cloud, network security configuration is crucial to ensure secure communication between the cloud environment and the on-premise systems. Proper network security measures, including VPNs, firewalls, and secure access protocols, need to be established to protect data integrity and confidentiality during and after the migration.

References:

Pega Cloud Services: Pega Cloud Environment Setup

Pega Cloud Security: Pega Cloud Security Best Practices

Several factors can contribute to delays in sending correspondence in a Pega application:

Queued SLA Objects : The number of Service Level Agreement (SLA) objects queued can affect the timing of correspondence. If there are many SLA objects queued, the system may take longer to process them, leading to delays.

Error Handling for Locked Items : If there are errors in handling locked items, this can also cause delays. When an item is locked and an error occurs, the system needs to manage these exceptions, which can impact the overall processing time.

References: Pega Platform documentation on SLA and error handling mechanisms.

To meet the requirement that only the work group manager can read and write purchase request cases when the total amount exceeds USD 10,000, the following configurations can be used:

Reads Access Control Policy : Use a reads access control policy with a condition that checks if the amount is less than USD 10,000. This restricts access based on the purchase request amount.

Conditional Access in Access Manager : Configure conditional access in Access Manager to allow read and write permissions for purchase request cases only when the amount is less than USD 10,000. References:

Pega Documentation on Access Control Policies: Access Control Policies

Pega Access Manager: Access Manager

To allow three physicians to review the orders in parallel, you need to use the " Split For Each " shape. This shape enables parallel processing for each item in a list, such as the list of physicians.

Understanding Split For Each Shape in Pega: The " Split For Each " shape allows you to create instances of a subprocess for each item in a specified list. This means each physician can independently review and evaluate the surgical procedure requests simultaneously.

Configuration Steps:

Step 1: Create a list of physicians who will be performing the evaluations.

Step 2: Add a " Split For Each " shape to the process flow.

Step 3: Configure the " Split For Each " shape to iterate over the list of physicians.

Step 4: Define the evaluation subprocess to be called for each physician.

Step 5: Ensure that each physician ' s evaluation subprocess is independent of the others.

Advantages of Using Split For Each: This approach allows all three physicians to perform their evaluations simultaneously, reducing the overall processing time and ensuring that the process can advance as soon as two out of three evaluations are completed.

References: Pega Documentation on Split For Each shape provides detailed steps on how to configure and use this shape in your process flows.

To ensure basic functionality behaves as expected before inviting users to start acceptance testing after importing a Rule-Admin-Product (RAP) file:

Create a regression test suite. Run the test suite using the automation server (Answer D) :

Explanation : A regression test suite helps verify that the new features do not break existing functionality. Running these tests using an automation server ensures that the process is repeatable, reliable, and efficient.

To address the requirement of handling tasks from both Pega and non-Pega applications seamlessly, the best approach is:

Pega Process Fabric Hub (B) :

Pega Process Fabric Hub integrates multiple applications, whether they are Pega or non-Pega, providing a unified view of work. It allows users to manage tasks from different systems in a single interface, avoiding the need to switch between applications.

This approach supports a unified worklist, enhancing productivity and user experience by consolidating tasks into a single accessible place.

References:

Pega Process Fabric Hub Overview

To ensure that the insurance company can meet the 24-hour response time requirement for claims submitted by email, the best recommendation is to use an email listener with concurrent threads. This configuration allows the system to process multiple emails simultaneously, thereby handling the high volume of 500 emails per hour efficiently. References:

Pega Documentation on Email Listener: Email Listener

 Queue Status " Available " : When the queue status for an item is " Available, " it indicates that the item is ready for processing but has not yet been picked up by the agent.

 Failed Processing: If the agent attempted to process an item but failed, it can be reflected in the status. The item remains in the queue, and the system logs may indicate the failure reason.

 Scheduled Processing: The status " Available " can also mean that the item is scheduled for future processing based on the agent ' s schedule.

References:

Pega Academy: System Queue Management

Pega Documentation: Understanding Agent Status and Queue Management

To avoid creating unnecessary case-level properties and views in Pega Express:

Define case type views using " * page, property " syntax for the majority of the fields (Answer A) :

Explanation : Using this syntax allows you to reference existing data types and properties, reducing redundancy and the need for additional case-level properties.

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.

To avoid creating unnecessary case-related properties and views:

Work Pool Level Definitions : Define most properties and sections at the work pool level to ensure they are reusable across multiple case types. This approach reduces redundancy and simplifies maintenance.

Data Types : Create data types that correspond to the case type when necessary. This helps in organizing related data and promotes reuse.

Data Reference Field Type : Use the data reference field type in the case type ' s data model tab. This allows you to link to existing data types without duplicating properties, maintaining data integrity and reducing redundancy.

References: Pega Platform documentation on data modeling, work pools, and data reference field types.

For the webinar scenario, the best case design pattern is:

Answer: C. Data Instance First

Data Instance First: This pattern is suitable when the case is driven by data instances, such as tracking registrations for a webinar and initiating a case only when a sufficient number of registrations are received.

Segment: Segments are used to define high-level criteria for identifying the starting population. Conditions related to customer attributes like income and credit score are best suited for segment definitions because they help in broadly classifying customers based on these attributes.

Monthly Income: Customers with a monthly income less than 20000 can be grouped into a segment for targeted promotions.

Credit Score: Customers with a credit score higher than 200 can also be grouped into a segment to ensure that only creditworthy customers are considered for promotions.

Engagement Policy: Engagement policies are used to refine the targeting criteria further and define rules that must be met for engagement. Conditions related to customer consent and specific financial ratios are better suited for engagement policies.

Opt-in Status: Checking if the customer is opted in to receive promotional emails ensures compliance with communication preferences.

Debt to Income Ratio: A higher debt to income ratio might indicate higher financial risk, and this should be considered before engaging the customer with offers.

Opt-out Status: Ensuring customers are not opted out of receiving credit card promotions on mobile phones is crucial for effective communication and compliance with customer preferences.

References: Pega Academy modules on Segmentation and Engagement Policies provide detailed guidance on best practices for defining and using segments and engagement policies in customer decisioning.

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.

 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

In a highly available system with crash recovery enabled:

Yes, If the authentication cookie was lost (Answer C) :

Explanation : If the authentication cookie, which maintains the user’s session, is lost during the crash, the user will need to be reauthenticated to establish a new session.

My Performance Details Report:

Use the My Performance Details report to get insights into the user’s session performance metrics.

Alerts Log:

Review the Alerts log for any alerts that were triggered during the user’s session that could indicate performance issues.

Test for Completeness:

Ensure that all possible conditions and outcomes are covered in the decision rule. This involves checking that there are no missing branches or conditions that could result in an undefined outcome.

Unit Testing:

Conduct unit tests to verify that all scenarios return the expected results. This helps in identifying any gaps or missing conditions in the rule.

References:

Pega Academy: Decision Rules and Validation.

Pega Documentation: Testing and Debugging Decision Rules.

Increase Weights of Conditions:

Adjust the weights of the conditions to make them more significant in the duplicate detection process. This can help in reducing false positives.

Adjust Threshold:

Increase the threshold for the weighted condition sum to ensure that only cases with a higher likelihood of being duplicates are flagged.

References:

Pega Academy: Duplicate Case Management.

Pega Documentation: Configuring Duplicate Detection Rules.

When designing a worldwide application, it is important to consider various factors such as the number of languages and locales, the intent to market the framework layer, and the initial deployment region. These questions help validate the consultant ' s recommendation by addressing key aspects of the application ' s architecture and deployment strategy. References:

Pega Framework and Implementation Layers: Pega Framework

When defining an embedded list property with a specific data type:

Changing pxObjClass at Runtime (A) :

The pxObjClass of any page within the .Loans list can be modified at runtime. This provides flexibility to change the class of individual pages if needed.

Inheritance and Calculation (C) :

Extending the data model, such as a car loan application extending MyCo-Data-Loan-Auto, does not impact aggregate functions like sum performed on properties (e.g., .Loans().Amount).

Class Consistency within the List (E) :

All pages within the .Loans list must adhere to the same class type, ensuring consistency and correct behavior of operations on the list.

References:

Pega Data Modeling Guidelines

Pega Clipboard and Page Management Documentation

 Node Association: To control which nodes in a cluster an agent runs on, you need to associate the agent with specific node types. This ensures that the agent runs only on the nodes that match the specified type.

 Configuration: In the agent rule configuration, specify the node type under the " Node " settings. This allows for precise control over the agent ' s execution environment.

References:

Pega Academy: Configuring Agents for Node Types

Pega Documentation: Agent Configuration and Node Types

 Extending Core Pega Classes :

Extending existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal ensures that the application adheres to standard Pega data models.

Persisting instances of these extended classes in the PegaData schema aligns with best practices for data persistence and reuse.

 References :

Pega Lead System Architect documentation on data modeling recommends extending core Pega classes to maintain consistency and leverage built-in functionalities.

 Therefore, the correct answer is:

A. Extend existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal, persisting instances of the extended classes in the PegaData schema.

 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

To define Authentication Service data instances in Pega, the following rule types are used:

Data pages: Used to retrieve and store authentication-related data.

Activities: Perform operations such as authentication logic and integration with external systems.

Data transforms: Used to map and transform authentication data.

References:

Defining Authentication Services in Pega

When deciding between a wait shape and an assignment with an SLA, consider the following requirements where a wait shape is simpler:

Adjust the Case Urgency: The wait shape allows you to adjust the urgency of a case when the wait condition is defined, which is simpler than configuring an SLA.

Manual Override: The wait shape provides an option to manually step past the waiting point if necessary, making it more flexible for certain scenarios.

References:

Wait Shape

Service Level Agreements