PEGACPLSA88V1 Questions and Answers

To configure the data page to satisfy all the requirements in the scenario:

Create a thread-level data page with parameters that uses a connector as its source (Answer B):

Explanation: A thread-level data page ensures that the data is specific to the current user session and not shared across multiple sessions. Using parameters allows for flexibility in filtering and retrieving the required transactions. The connector source ensures data is fetched from the external service as needed.

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

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

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.

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.

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.

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

Applicability:Applicability rules ensure that the right offers are presented to the right customers. If Anna holds a higher value card (Premier Rewards), the new Rewards card offer might not be applicable to her because it is a lower-tier product.

Configuration Steps:

Define applicability criteria for each offer.

Ensure that offers are presented based on customer profiles and existing products.

References:Pega Academy lessons on Offer Management explain the role of applicability rules in ensuring that relevant offers are presented to customers.

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

To avoid recalculating declarative properties when extracting data with BIX:

BIX Command Line Options:

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

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

Configuration:

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

References:

Pega Business Intelligence Exchange (BIX) User Guide

Pega Documentation on Declarative Rules

Circumstancing: This technique allows for creating variations of a rule based on specific conditions, such as different products, without duplicating the rule for every possible product scenario.

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

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

The out-of-memory error occurring shortly after 3:00 P.M. is likely caused by a job scheduler running on a single Web Tier node and pulling a large number of records onto a clipboard page. This operation consumes a significant amount of memory, leading to the node running out of available memory and crashing.

References:

Pega Performance: Diagnosing Memory Issues

Pega Schedulers: Job Scheduler Configuration

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.

Next-Best-Action Reevaluation:When a customer rejects an offer, Pega Customer Decision Hub reevaluates the Next-Best-Action to determine the next most relevant action for the customer. This ensures that the customer's needs and preferences are continuously considered.

Process Steps:

Capture the rejection event.

Trigger the reevaluation process.

Determine the next best offer or action based on updated customer data and context.

References:Pega Documentation on Customer Decision Hub outlines the process of handling offer rejections and reevaluating Next-Best-Actions.

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

To create a new control with a shortcut key:

Create a new autogenerated button control and alter its caption to support a shortcut key (Answer A):

Explanation: Using autogenerated controls ensures consistency with Pega’s UI framework, and adding a shortcut key to the caption makes the button accessible via keyboard shortcuts.

 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

To implement integration of system of record data for account information in a Pega Customer Service application:

Specialize the Pega Customer Service data pages that use account data to ensure they are tailored to fetch the required data.

Integrate with the system of record to populate an Account data class, ensuring that account information is correctly retrieved and stored.

Create a data transform to map the Account data class to the Pega Customer Service Account class, ensuring that data is correctly transformed and utilized within the Pega application.

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

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

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

References:

Database Maintenance

Data Archiving

To ensure that 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

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

Determine target budget to retain a customer

Component: Decision table

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

Divide customers into risk segments

Component: Scorecard

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

Compute sum of profit

Component: Group By

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

Determine customer credit score

Component: Scorecard

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

Step by Step Comprehensive Detailed Explanation with References:

Decision Table:

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

Create Access When Rule:

Go to Records Explorer > Security > Access When.

Create a new Access When rule that checks if the current user is either the primary or secondary owner of the account. Use conditions like current user = primary owner or current user = secondary owner.

Configure the Access When Rule:

Open the Account case type.

Go to the Security tab and in the Case Type rules, apply the created Access When rule to ensure that only users who meet the conditions (primary or secondary owners) can view or update the case.

Apply Access Control:

In the Access Role configuration, apply the Access When rule for read and write instances of the Account class.

Ensure that the roles assigned to the users have the necessary permissions configured.

Testing and Validation:

Test the implementation by logging in with users who are primary or secondary owners and verifying access.

Try logging in with users who are not owners to ensure access is denied.

References:

Pega Academy: Security and Access Control.

Pega Documentation: Access Control Policies and Access When Rules.

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.

To configure the application to handle the requirement where employees can designate alternate operators to perform their work while they are on vacation, follow these steps:

Define a custom Access When rule:

Create an Access When rule named pxAssignedToMeOrAlternate. This rule will allow the system to check whether the assignment is for the current user or their designated alternate.

The rule should include logic to determine if the assignment belongs to the operator or the operator’s alternate.

Modify the pyUserWorkList Report Definition:

Access the pyUserWorkList report definition which is used to display the worklist for the current user.

Modify this report to include a filter condition using the pxAssignedToMeOrAlternate Access When rule. This ensures that the report displays assignments for both the current user and any assignments for which they are an alternate.

Assign Worklist assignments to alternate operators:

Ensure that the assignments visibility is adjusted accordingly by modifying the security settings to allow access to assignments for alternate operators.

Testing and Verification:

Test the configuration to ensure that alternate operators can see and access the worklist items of the operators they are covering for.

This approach leverages Pega’s Access When rules to dynamically adjust the visibility of assignments based on operator relationships, ensuring that alternate operators can perform work as needed without requiring manual assignment transfers.

References:

Pega Documentation on Access When rules: Access When Rules

Pega Documentation on Report Definitions: Report Definitions

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.

The Localization wizard in Pega is designed to facilitate the process of localizing an application. It extracts string values from various parts of the application, ensuring that all text is available for translation. It also creates field value rules for labels used throughout the application, allowing for easy updates and translations. These capabilities are crucial for maintaining a consistent user experience across different languages and locales.References:

Pega Documentation on Localization Wizard: Pega Localization Wizard

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

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

 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

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.

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.

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.

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.

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.

Defining a case type within a case type-specific ruleset provides several advantages:

Branch Ruleset Association: By associating each branch ruleset with case-specific user stories, you can better manage development and testing. This allows for more targeted reviews and testing, ensuring that changes are isolated and easily traceable.

Component Application Conversion: If there is a possibility that the case type might be converted to a component application in the future, having a case-specific ruleset simplifies the process. It allows the case type to be more easily packaged and reused across different applications.

References: Pega Platform best practices for ruleset management and case type design.

Enable Auditing:

On the Rule-Declare-Decision Table RuleForm, check the option to enable auditing.

Monitor Changes:

This configuration will track changes made to the decision table in the production environment.

To minimize development conflicts and work with the most current version of the Policy Administration application:

Periodic Rebasing: Regularly rebase the Policy Administration application to ensure that the Quoting application is built on the most recent version. This practice helps in keeping the applications synchronized and reduces integration issues.

Branch Reviews: Conduct branch reviews when merging branches. This ensures that all changes are thoroughly reviewed and validated before they are integrated, reducing the likelihood of conflicts and maintaining code quality.

References: Pega Platform documentation on branching, rebasing, and branch review processes.

 Service Request Processor for Asynchronous Processing:

Configuring a REST service to run asynchronously using a service request processor ensures that the service runs without making the external application wait. The system returns a unique identifier instantly and processes the request in the background.

 References:

Pega's best practices for REST services and asynchronous processing recommend using service request processors for handling long-running processes.

 Therefore, the correct answer is:

B. A REST service that runs asynchronously by using a service request processor.

Edit Organization Name:

Go to the application settings in Pega Express.

Edit the Organization name field to "BCO" to match the company's NASDAQ trading name.

Edit Division Name:

Edit the Division name field to "UK" to reflect the geographical location where the application will be used initially.

Validation:

Ensure that the changes are saved and reflected in the application's organization settings.

References:

Pega Academy: Setting Up Your Application.

Pega Documentation: Application Structure and Organization Settings.

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

 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

Analyzing alert logs using the Pega Log Analyzer (PLA) is a critical step in diagnosing performance issues. The alert logs contain detailed information about performance alerts, which can help identify bottlenecks or specific rules causing delays. By reviewing the logs from each node, you can pinpoint the time and nature of the performance issues and take corrective actions.

References:

Pega Troubleshooting: Pega Log Analyzer

Pega Performance: Monitoring and Troubleshooting

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.

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

Continuous integration (CI) is a DevOps practice where developers frequently merge their code changes into a central repository, followed by automated builds and tests. The primary goal is to detect and address integration issues early.

Leveraging release toggles (Answer B):

Explanation: Release toggles (or feature toggles) are a technique to enable or disable features within a software application without deploying new code. This allows teams to integrate new features incrementally and safely, supporting continuous integration and delivery.

Creating a Separate Ruleset:

It is considered best practice to isolate customizations in a separate ruleset to simplify future migrations and upgrades.

Benefits of Separate Ruleset:

Easier to identify and manage customizations.

Simplifies the process of moving custom rules between environments.

Reduces the risk of conflicts during upgrades.

Implementation:

Define a new ruleset specifically for the custom GetNextWork functionality.

Override the necessary rules within this ruleset.

References:

Pega Best Practices Guide

Pega Academy Course on Rule Management and Versioning

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.

Configure Authentication Activity:

Go to Records Explorer > Security > Activities.

Create or configure the authentication activity to map the authenticated user to the operator ID in Pega.

LDAP Attributes Mapping:

Go to Designer Studio > Security > Authentication Service.

Configure the LDAP attributes to map to Pega operator properties, ensuring that attributes like cn, sn, mail, etc., are correctly mapped.

Validation:

Test the Single Sign-On (SSO) setup to ensure the authentication and attribute mappings work correctly.

Verify that users can log in using SSO and their LDAP attributes are correctly reflected in Pega.

References:

Pega Academy: Single Sign-On Configuration.

Pega Documentation: LDAP and SSO Configuration.

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

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

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

Next-Best-Action Configuration:

In Pega, configure the Next-Best-Action strategy to include customer lifetime value as a factor.

Set Thresholds:

Define thresholds for customer lifetime value to determine what constitutes a high-value proposition.

Prioritization Logic:

Implement logic within the strategy to prioritize actions or offers that align with high customer lifetime value.

 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 queue an item for a queue processor, you can use the following methods:

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

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

References:

Queue-for-processing method

Run in Background smart shape

Priority Communication:Priority communications are used for urgent and important messages that need to reach all customers immediately. Configuring this type of outbound interaction ensures that the temporary contact details are promptly communicated to all customers.

Configuration Steps:

Define the priority communication in the outbound strategy.

Ensure that the message content is clear and concise.

Schedule the communication to be sent out immediately to all customers.

References:Pega Academy courses on Outbound Campaign Management explain the different types of outbound interactions, including priority communications, and their appropriate use cases.

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.

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 understand the valid statements regarding the field group list:

An auto loan application can extend MyCo-Data-Loan-Auto without affecting a sum performed against .Loans.Amount:

Since MyCo-Data-Loan-Auto extends MyCo-Data-Loan, it can be included in the field group list. Calculations like sums on .Loans.Amount will not be affected as they are based on the common superclass.

All pages within the .Loans field group must be the same class, either MyCo-Data-Loan-Auto or MyCo-Data-Loan-Mortgage:

The field group list should maintain consistency in the class type for its pages. Mixing classes within the field group can lead to errors and unpredictable behavior.

A rule in MyCo-Data-Loan-Mortgage can only be referenced through .Loans if also defined in MyCo-Data-Loan:

To reference rules through the field group list, they must be accessible via the common superclass (MyCo-Data-Loan). This ensures that rules can be consistently applied across different subclasses.

References:

Pega Documentation on Field Groups: Field Groups

Pega Documentation on Class Inheritance: Class Inheritance

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

Configure Add Party User Action:

Go to the user actions section in the case type configuration.

Local Action Configuration:

Ensure that the addparty user action is available as a local action during case creation to allow case workers to add a work party.

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.