PEGACPLSA88V1 Certified Pega Lead System Architect (CPLSA) Exam 8.8 Questions and Answers

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

Certain scenarios do not require an application server restart:

When deploying rule only hotfixes (Answer A) :

Explanation : Rule-only hotfixes update rules in the application without requiring a full server restart, allowing changes to take effect immediately.

 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 improve performance when fetching data from an external source in a cloud-deployed application, you should configure the data page to use a predefined key. This approach allows the data to be loaded once and then accessed quickly for subsequent requests.

Understanding Data Pages in Pega: Data pages in Pega are used to cache data, so it doesn ' t have to be retrieved from the source every time it is needed. Using a predefined key means that the data page is loaded with specific data that can be reused.

Configuring Data Pages with Predefined Keys:

Step 1: Define a data page and configure it to use a key for accessing data.

Step 2: Ensure the data page is set to load on demand or at a specific point in the process.

Step 3: Once the data is loaded with the predefined key, subsequent accesses to this data page will be faster because the data is already available in the cache.

Advantages of Using Predefined Keys: This approach reduces the need to repeatedly fetch data from the external source, thereby improving performance and reducing network latency issues in cloud environments.

References: Pega Documentation on Data Pages and best practices for caching and data retrieval provides detailed steps and examples on how to configure data pages with predefined keys for optimized performance.

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

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.

Text, letter Description automatically generated

When extending the data model provided by a Pega industry framework:

Specialize the data model as little as possible (Answer A) :

Explanation : Minimizing specialization helps maintain compatibility with future updates to the framework and reduces the complexity of the application.

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

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

 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

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

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

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.

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.

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.

Configure Table Edit:

Go to the .Title property in the Data Model.

Set the table edit option to reference the valid field values.

Decision Table Validation:

Ensure that the decision tables are set up to validate against these field values automatically.

This will help prevent incorrect spellings and ensure data integrity.

References:

Pega Academy: Data Validation and Integrity.

Pega Documentation: Decision Tables and Field Value Validation.

 Edit Input Rule: Create an Edit input rule on the customerinfo property. This rule will automatically convert the first and last names to upper case when the data is entered or updated, ensuring consistency.

 Data Transform: Develop a post-processing Data Transform that converts the names to upper case. This Data Transform can be invoked in the flow action to ensure that the names are converted after the user submits the form.

References:

Pega Academy: Configuring Data Transforms and Edit Input Rules

Pega Documentation: Data Transform Rules

Criterion 1: Owns a smart mobile

Engagement Policy Level: Group level

Explanation: The criterion " Owns a smart mobile " applies to all data plans and can be considered a group-level policy. It filters the audience at a broader level to ensure they have a smart mobile device.

Criterion 2:

Under graduation student

Engagement Policy Level: Issue level

Explanation: The criterion " Under graduation student " applies to multiple data plans (1 GB and 3 GB) and is more specific to the issue of targeting educational segments. Thus, it is suitable at the issue level.

Criterion 3:

Post graduation student

Engagement Policy Level: Action level

Explanation: The criterion " Post graduation student " is specific to the 5 GB plan and is most appropriate at the action level. This level ensures the targeting is precise for this particular plan.

New customer

Engagement Policy Level: Group level

Explanation: The criterion " New customer " can be applied across multiple offers and thus is suitable for the group level to broadly target new customers.

Existing customer

Engagement Policy Level: Action level

Explanation: The criterion " Existing customer " is applied at the action level to ensure specific offers (3 GB and 5 GB plans) are appropriately targeted to customers who already have a relationship with the company.

Step by Step Comprehensive Detailed Explanation with References:

Group Level Engagement Policy:

Conditions that apply broadly across multiple offers or groups of offers fall under group-level policies. Examples include owning a smart mobile and being a new customer.

Issue Level Engagement Policy:

Conditions that are relevant to a specific issue, such as educational status for specific data plans, are categorized under issue-level policies. This ensures that offers targeting undergraduates are consistently managed.

Action Level Engagement Policy:

Conditions that are specific to individual actions or offers are best managed at the action level. This includes targeting post-graduation students for the 5 GB plan and existing customers for specific plans to ensure precise targeting.

References: Pega ' s best practices for engagement policies recommend using group-level policies for broad criteria, issue-level for segment-specific conditions, and action-level for highly specific targeting to ensure effective and relevant customer engagement.

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.

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

To maximize flexibility for business users to create reports that retrieve data from several related classes in Pega Platform:

Association Rules :

Association rules define the relationships between different classes. They allow users to create reports that join data from multiple classes.

The Lead System Architect (LSA) is responsible for ensuring these association rules are defined and maintained in the application.

Creating Reports :

Once the associations are in place, business users can leverage these relationships to create complex reports without needing deep technical knowledge.

This enables users to pull in data from various related classes seamlessly.

References:

Pega Platform Reporting Guide

Pega Best Practices for Data Modeling

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

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

When tuning the agent configuration on a production system, it is important to review and adjust default agents because:

Not Necessary for Every Application : Some default agents are not necessary for every application and can be disabled to improve performance.

Should Never Run in a Production Environment : Certain agents are intended for development or testing environments and should not be active in production to avoid unnecessary processing and potential security risks. References:

Pega Agent Configuration Guidelines: Agent Configuration

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.

Add Justification to ARO Instances:

When configuring ARO instances, ensure that you add justifications whenever a privilege is not visible from the ARO’s ruleset. This improves transparency and adherence to security guidelines.

Navigate to the security settings in Pega and update the ARO instances accordingly.

Change Security Type for Activities:

For activities used for simulations, change their security type from " Activity " to " Utility " . This aligns with best practices and reduces unnecessary warnings.

Update the security settings for these activities through the Pega Developer Studio.

Custom Split-for-Each Process Step:

In the case designer, add a new step in the Processing stage where you need to create child cases.

Select the " More " option and then " Split for Each " .

Configure the split to create a separate child case for each item in the page list property.

Configure Data Propagation:

Ensure that data from the parent case is propagated to each child case.

In the case designer, go to the data propagation settings and map the relevant properties from the parent case to the child cases.

Use Page List Property:

Create a page list property in the parent case to store the list of suspected fraudulent charges.

Configure the case type to iterate over this page list property when creating child cases.

References:

Pega Academy: Implementing Case Management.

Pega Documentation: Split-For-Each and Data Propagation.

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.

Ensuring that new team members adhere to best practices can be achieved through the following methods:

Branch Review : Utilize the branch review feature in Pega, where senior team members can review the contents of the branch. This allows experienced developers to provide feedback and ensure that the new rules meet the required standards.

Branch Quality Review : Regularly review the quality of the branch to identify any rules that have guardrail warnings. Guardrails are best practice guidelines in Pega, and addressing these warnings helps maintain high-quality, robust rules.

References: Pega Platform documentation on branch development and guardrail compliance.

The best solution for maintaining discounts in an e-commerce application by a business manager is:

List Landing Page with Default Data Sources (D) :

A list landing page provides an intuitive interface for business users to view, manage, and update discount details. By defining default data sources, the data is automatically fetched and displayed, simplifying the maintenance process.

This approach ensures that business managers can easily access and modify discount information without needing deep technical knowledge.

References:

Pega Platform Help on Configuring Landing Pages

 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

For modeling different types of vehicles in an insurance quote application:

Separate Data Types :

Create a distinct data type for each vehicle type (e.g., Car, Motorcycle, Truck). This allows for specific properties and business logic for each vehicle type.

Single Vehicle Page List :

Maintain a single page list property in the quote case type to hold vehicle details.

At runtime, dynamically identify the page class for each entry in the list based on the type of vehicle being processed. This approach allows for flexibility and maintainability.

References:

Pega Data Modeling Best Practices

Pega Case Management Guide

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

 Elasticsearch Query Support :

Elasticsearch queries support operations such as " Starts with " , " Contains " , and " Greater than " , which are useful for various search and filtering needs.

 References :

Pega ' s use of Elasticsearch for indexing and searching data provides support for these operations to enhance report definitions.

 Therefore, the correct answers are:

A. Starts with

B. Contains

E. Greater than

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.

Setting Purpose:

Prepend prconfig/ to the setting purpose and append /default to ensure the dynamic system setting is recognized correctly.

Owning Ruleset:

Set the owning ruleset to one of your application-specific rulesets to maintain proper configuration and versioning.

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

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

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

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.

To address the complaints from customers and prospects about receiving irrelevant offers and products, the following two Pega solutions can be implemented:

Pega Marketing: This solution helps in creating personalized marketing campaigns. By leveraging predictive analytics and customer data, it ensures that the marketing efforts are relevant and targeted. This reduces the chances of customers receiving irrelevant offers.

Customer Decision Hub: This hub centralizes the decision-making process by using real-time data and analytics to personalize interactions with customers. It helps in understanding customer needs and preferences better, thus preventing the delivery of irrelevant offers.

References:

Pega Marketing Overview

Customer Decision Hub

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

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.

Identifying the Error Flow:

When stages are altered in a case type, in-flight cases can encounter issues if they try to advance to a now-missing stage.

pzStageProblems Flow:

This flow is initiated when there are problems advancing stages due to missing or reconfigured stages.

It helps to manage and resolve issues related to stage progression.

References:

Pega Platform Case Management Documentation

Pega Academy Course on Advanced Case Design

To design a reporting strategy that displays the number of cases by status at the end of each month for a 12-month period, follow these steps:

Configure an Agent: Set up an agent to run at the end of each month to capture the status of all cases.

Record Data: The agent records the case statuses in a separate table specifically created for this purpose.

Reporting: Generate reports based on the data stored in this table to provide an accurate month-end snapshot of case statuses.

References:

Configuring agents in Pega

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.

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

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.

Future Component Application:

Define the case type within a specific ruleset to facilitate its future conversion to a component application.

This allows for better modularization and reuse across different applications.

True Component Conversion:

Structuring the case type in a specific ruleset makes it easier to convert it into a true component in the future.

This approach supports scalability and maintainability of the application.

References:

Pega Academy: Advanced Case Management.

Pega Documentation: Ruleset and Component Management.

 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

To meet the requirement of displaying the current label associated with each code in a report, use a custom section in the report definition to display the rows. Use a Keyed-access Data Page to source the label values dynamically from the external system of record whenever the report is run. This ensures that the latest labels are always displayed without needing to persist them locally. References:

Pega Documentation on Data Pages: Data Pages

Pega Report Definitions: Report Definitions

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

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.

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

To ensure that every attempt by a developer to check a rule into a certain ruleset version is reviewed before that rule is allowed to be checked in:

C. Override the FindReviewers decision tree to invoke a when rule that evaluates the criteria, if the when rule returns true, the decision tree returns SendBack.

By overriding the FindReviewers decision tree and incorporating a when rule, you can enforce criteria such as complete history tab fields and justified warnings. If the criteria are not met, the decision tree returns SendBack , preventing the rule from being checked in.

References:

Pega Documentation on Rule Check-In: Rule Check-In

Pega Documentation on Decision Trees: Decision Trees

For managing a 30-person development team located across the globe:

C. Large development instance:

A large development instance in Pega Cloud is designed to support extensive development activities for large teams. It provides the necessary resources, scalability, and performance required for a 30-person development team working globally.

References:

Pega Documentation on Pega Cloud Environments: Pega Cloud Environments

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

 Identify and configure the right set of test suites to test early and often to identify the defects in the early stages of project life cycle :

Testing early and frequently helps in identifying and fixing defects at the initial stages, reducing the cost and effort required for fixing them later.

 Identify and configure the right set of test suites that need to run at different stages of release pipeline :

Different stages of the release pipeline require different sets of tests to ensure comprehensive testing coverage and quality assurance.

 Identify and configure the automation test suite by using Pega Platform features and industry best practices :

Leveraging Pega Platform ' s features and adhering to industry best practices ensures that the automated test suites are effective and reliable.

Using Data Flows:

Leverage data flows to read and process data efficiently.

Utilize datasets to source the required data.

Option A:

Use a utility to post data to a queue processor.

The queue processor will then handle posting the data to the data warehouse over REST.

Option B:

Alternatively, the utility can synchronously post data directly to the data warehouse.

This ensures immediate transfer of data upon resolution of a case.

References:

Pega Platform Data Flow Documentation

Pega Academy Course on Integration and Data Synchronization

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