PEGACPLSA88V1 Practice Exam Questions with Answers Certified Pega Lead System Architect (CPLSA) Exam 8.8 Certification

? Next-Best-Action (NBA): This concept in Pega Customer Decision Hub involves recommending the best possible action for each customer interaction, which often includes decisions in customer service, marketing, sales, and risk management.

? Loan Decision: NBA is frequently applied in financial services to determine creditworthiness and loan approval, leveraging predictive analytics and customer data to make informed decisions.

? Reference: Pega Customer Decision Hub documentation outlines the application of NBA in making critical customer decisions, such as loan approvals, to enhance customer experience and operational efficiency (Pega Customer Decision Hub Documentation, Decision Strategies).

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

? 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).

Use the Optimistic Locking Option: Optimistic locking ensures that updates are handled efficiently in a multimode system without causing contention.

Override DetermineLockString: Override the DetermineLockString to use .AccountID instead of .pyID as the lock string to ensure that the correct customer account is locked during updates. References:

Pega Locking Mechanisms: Locking Mechanisms

Pega Advanced Agent Configuration: Advanced Agent Configuration

Switch Application When Modifying Rules:

Ensure that developers switch to the appropriate application context when making changes to avoid conflicts.

Use Pega's application switcher to toggle between the Quoting and Policy Administration applications as needed.

Perform Branch Reviews:

Conduct regular branch reviews to ensure that changes are correctly merged and validated.

Use Pega's branch review tools to facilitate this process and minimize conflicts.

References:

Pega Academy: Best Practices for Application Development.

Pega Documentation: Branching and Merging in Pega.

To implement the business requirement for risk segmentation using age and credit score:

Create a decision table that defines the risk segmentation rules.

Add this decision table to a decision strategy.

Pass the customer's credit score as a parameter to the decision table to determine the appropriate risk segment.

? Embedded List with Declare Index:

Both Case Types A and B possess an embedded list of line items. Using a Declare Index against each embedded list ensures efficient data retrieval and indexing.

Changing the direct inheritance class for each Declare Index class to the Line Item data type allows for proper data management and querying.

? References:

Pega best practices for data modeling and indexing recommend using Declare Index for embedded lists to enhance performance and data organization.

? Therefore, the correct answer is:

D. Case Types A and B both possess an embedded list of line items. Define a Declare Index against each embedded list. Change the direct inheritance class for each Declare Index class to the Line Item data type.

Handling reference data from external systems efficiently is crucial to minimize system resource usage.

Use the System of Record (SOR) data access pattern to populate the page contents (Answer C):

Explanation: The SOR pattern ensures that the application fetches data directly from the external system when needed, rather than storing and maintaining copies of the data. This approach minimizes memory usage and keeps the data up-to-date.

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

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

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.

? In a decision strategy, to use a customer property in an expression, you need to prefix the property with the keyword Customer.

? This ensures that the property is correctly identified and retrieved from the customer data page.

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

For validating the BenefitType property value, the recommended approach is:

When Rule and Relevant Record (D):

A System Architect creates a When rule in Dev Studio, referencing the ClaimBenefit Clipboard page on the Pages & Classes tab.

The rule is marked as a relevant record, making it available for Citizen Developers to use. This approach ensures that the validation logic is centrally defined and easily accessible for reuse.

References:

Pega Dev Studio Documentation on Creating When Rules

Pega Documentation on Marking Rules as Relevant Records

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.

Enable Security Auditing:

Navigate to the Pega Platform's security settings.

Enable security auditing by configuring the security policies.

This setting will track and log any unauthorized access attempts and failed login attempts.

Configure Audit Log Settings:

Go to the "Security Policies" section under the "System" category in the Dev Studio.

Ensure that logging for authentication events is enabled. This includes both successful and failed login attempts.

Generate Reports:

Utilize the built-in reporting capabilities of Pega to create custom reports.

These reports can be configured to display logs of failed login attempts, providing visibility into unauthorized access attempts.

References:

Pega Platform User Guide on Security Policies

Pega Academy Course on Security and Access Control

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

Step by Step Comprehensive Detailed Explanation with References:To perform extensive analysis on work party information while minimizing impact on case workers:

Configure a reports database for the Class Group and Index WorkPartyUri Data Admm DB-Table records (B): Setting up a separate reports database helps offload reporting activities from the transactional database, reducing the load on the operational system.

Use BIX to export Case and related Work Party data to a data warehouse (D): BIX (Business Intelligence Exchange) can be used to export data in bulk to a data warehouse where extensive analysis can be performed without affecting the performance of the operational Pega applications.

References:

Pega Reporting: Using a Reports Database

Pega BIX: Business Intelligence Exchange

The Exclude Operators option in the Security Policies landing page allows administrators to specify certain operators, such as Admin or Executive roles, who should be exempt from the lockout policy. This ensures that critical users retain access even after multiple failed login attempts, aligning with the requirement to exclude specific roles from lockout policies.

References:

Pega Security Policies: Configuring Security Policies

Pega Authentication: Authentication and Access Control

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.

Enable CAPTCHA Security Policy:

Navigate to the security settings in Pega.

Enable CAPTCHA to prevent automated login attempts.

Authentication Lockout Policy:

Configure the authentication lockout policy to lock accounts after a certain number of failed attempts within a specified timeframe.

To extend a native mobile app to allow customers to create claims using a claims management application on the Pega platform, you should configure a service that can be called from the native mobile app to create claim cases. This approach allows the native app to interact with the Pega application seamlessly. The Pega platform can then handle the claim processing and push notifications to the mobile app as updates occur.

A rule defined in myco-data-shape-rectangle can modify the .Color property because .Color is defined in the parent class (myco-data-shape) and is inherited by its subclasses.

A rule existing in myco-data-shape can be overridden in myco-data-shape-circle, allowing for specific behavior in the subclass while maintaining the inheritance structure.

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

Check Weighted Conditions:

Ensure that the combined weights of the conditions meet or exceed the threshold set for identifying duplicates. This can be done in the Duplicate Search settings.

Verify Basic Conditions:

Confirm that each of the basic conditions (non-weighted) are met for the cases being compared. If these conditions are not satisfied, the duplicate search will not proceed to evaluate the weighted conditions.

Configuration Review:

Review the configuration of the duplicate search rule to ensure it is correctly set up and that the property values being compared are correct.

References:

Pega Academy: Case Management and Duplicate Detection.

Pega Documentation: Configuring Duplicate Case Search Rules.

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

? 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

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

The primary reason for developing a set of unit test cases and automated testing suites in a CI/CD model is:

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

Automated testing helps ensure the quality and correctness of the rules being deployed. It verifies that changes do not introduce errors and maintains the integrity of the pipeline by catching issues early in the development cycle.

References:

Pega Documentation on CI/CD: CI/CD

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.

Data Transform Configuration:

Create a data transform that copies the selected items to the page list property.

Post-Processing Action:

In the flow action, add the data transform as a post-processing action to ensure it executes after the form submission.

Testing:

Test the form submission to verify that the selected items are correctly copied to the page list property.

References:

Pega Academy: Data Transform and Flow Actions.

Pega Documentation: Configuring Post-Processing Actions.

To create a report that shows the number of employees with varying years of service, the best approach is to use a SQL function:

SQL Function: Create a SQL function that categorizes the employees based on their years of service. This function can then be used in the report definition to generate the desired output.

Implementation: Implement the function to return different categories such as more than 20 years, between 15 and 20 years, etc.

References:

Creating SQL functions in Pega

The load-datapage activity method is used to initiate the loading of a data page. This method ensures that the data page is populated with the required data by executing its defined source. References:

Pega Documentation on Data Pages: Data Pages

? Indexing: Adding indexes to columns involved in equality comparisons can significantly improve query performance by reducing the need for full table scans.

? Implementation: Identify the columns frequently used in WHERE clauses and create indexes for these columns in the database. This optimization reduces query execution time and enhances overall application performance.

References:

Pega Academy: Database Optimization Techniques

Pega Documentation: Indexing Database Tables

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

? In Pega, to access a property from an unconnected component within a decision strategy, you use the component-dot-property construct.

? This construct allows you to reference properties of other components within the strategy, ensuring that all necessary data is accessible for decision-making.

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.

The class structure in Pega defines how different case types and sub-cases relate to each other. EventBooking cannot be a subcase of Auto if the business logic does not support such a relationship. Ensuring the correct hierarchy is crucial for maintaining logical and functional consistency in the application.References:

Pega Class Structure Guidelines: Pega Class Structure

Tax Case Type and Specialization:

Create a new tax case type within the Pega Platform application to handle the independent tax processing functionality.

Utilize case type specialization to define different processes for each country. This means creating specialized versions of the tax case type based on the country property.

Country-specific Processes:

Each specialized tax case type will have its own processes tailored to the specific tax regulations and requirements of the respective country.

This allows for the flexibility to handle different tax processing rules and ensures compliance with country-specific tax laws.

Routing and Assignment:

Configure routing rules to assign the tax cases to the appropriate tax consultants based on the country.

Use decision tables or decision trees to determine the correct tax consultant for each case, ensuring that the case is handled by a consultant with the relevant expertise.

Efficiency and Maintenance:

By using case type specialization, the application maintains a clear and organized structure where each country’s tax processing logic is encapsulated within its own specialized case type.

This makes the system easier to maintain and update, as changes to tax processing rules can be made within the specific country’s specialized case type without affecting others.

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.

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

To help users find rules from the BCO-Data-Quote class when working in APP Studio, you should:

Relevant Records Configuration: Mark each rule you want to reuse as a relevant record. This makes these rules easily discoverable and reusable within APP Studio.

Implementation in APP Studio: Navigate to the data type and mark the necessary rules as relevant records. This action ensures that these rules are available in the relevant contexts when users work within the application.

References:

Using relevant records in App Studio

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

When deploying an application to a production environment, the following security tasks are performed:

Delete the Unauthenticated access group: To prevent unauthorized access to the application.

Restrict access to ruleset configuration: Ensures only authorized users can make changes to the ruleset configurations, protecting the application from unintended modifications.

Update standard dynamic system settings: Ensure that all system settings are correctly configured for production, enhancing the application's security and performance.

References:

Pega Security Best Practices

Graphical user interface, application Description automatically generated

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.

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

D,B,C,A,E

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.

A rule-utility-function (RUF) has the advantage of being directly callable from a decision table, which is a common requirement in Pega applications for implementing business logic. This direct invocation capability simplifies the design and execution of decision rules. References:

Pega Rule-Utility-Functions: Rule-Utility-Functions

To ensure the property contains the correct customer information at runtime:

Configure the property to refer to a data page using the System of Record (SOR) pattern. This pattern ensures that the property always reflects the current data from the external database, maintaining data consistency and accuracy.

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

To address difficulty in creating a customer service request through Facebook Messenger:

Change the text analyzer configured for the channel (Answer C):

Explanation: The text analyzer is responsible for interpreting user input. Improving its configuration can enhance its ability to understand and process customer requests more accurately.

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.

Graphical user interface, application Description automatically generated

Text Description automatically generated with low confidence

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 extend the Pega Foundation for Healthcare (PFH) data model:

Direct Inheritance for Extension (B):

Use direct inheritance to extend the foundation data model provided by PFH. This ensures that the core data model remains intact while allowing for the addition of new fields and data classes specific to the company's needs.

Pattern Inheritance for Behavior (B):

Utilize pattern inheritance to extend application-specific behavior. This allows for customization and the addition of application-specific logic while maintaining a clear separation from the core data model.

References:

Pega Foundation for Healthcare Implementation Guide

Pega Inheritance Models Documentation

? Automated Pega Unit Tests:

Having new team members create and run automated Pega unit tests against their rules ensures that they adhere to best practices and catch errors early.

? Rule Check-In Approval Process:

Using the rule check-in approval process allows for a review of changes made by new team members, ensuring that all rules meet the required standards and best practices.

? References:

Pega best practices for rule management and team collaboration recommend these approaches to maintain code quality and adherence to standards.

? Therefore, the correct answers are:

A. Have new team members create and run automated Pega unit tests against their rules.

C. Use the rule check-in approval process to review the changes that the new team members make.

For processing weekly CSV files of customer insurance quotes and creating policy cases:

File Listener and Job Scheduler (D):

Use a file listener to read the incoming CSV file and feed the data into a data type.

Configure a job scheduler to read the records from the data type and create cases. This approach decouples the file reading and case creation processes, allowing for better control and error handling.

References:

Pega File Listener Configuration Guide

Pega Job Scheduler Documentation

Separate Application for Reusable Component:

Placing the component in a separate application ensures modularity and reusability.

Departments can integrate with this application as needed, ensuring consistency and reducing redundancy.

Benefits:

Centralized maintenance and updates.

Easier to manage and deploy across various departments.

Avoids embedding the component directly in multiple applications, which could lead to version control issues.

References:

Pega Best Practices Guide

Pega Academy Course on Reusable Components and Modular Design

These answers and explanations have been verified according to the Pega Lead System Architect guidelines and best practices.

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.

Limited Availability and Concurrency: This pattern handles situations where resources (like ferry seats) are limited, and concurrency needs to be managed to ensure fair allocation.

Divide and Conquer: This pattern involves breaking down a case into sub-cases or steps, such as managing bookings for both the outbound and return trips separately.