Pegasystems PEGACPLSA88V1 Certified Pega Lead System Architect (CPLSA) Exam 8.8 Exam Practice Test

BIX Integration:

Use Pega's Business Intelligence Exchange (BIX) to export the Index-WorkPartyUri data. This method allows real-time data export without impacting case worker performance.

Configure BIX to export the required data to the report database at scheduled intervals.

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.

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

Scenario Tests Can Include Another Scenario Test (A):

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

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

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

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

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

References:

Pega Scenario Testing Guide

Pega Platform Test Automation Documentation

To troubleshoot chronic performance issues in a cloud-based production application, you can use the following techniques:

Performance Alerts and Exceptions in PDC: Review the alerts and exceptions in Pega Predictive Diagnostic Cloud (PDC). PDC provides real-time monitoring and insights into performance issues.

Performance Alerts and Exceptions using PLA: Use the Pega Log Analyzer (PLA) to review alerts and exceptions. PLA helps in identifying and diagnosing performance bottlenecks by analyzing log files.

References:

Pega Predictive Diagnostic Cloud (PDC)

Pega Log Analyzer (PLA)

Pega's Center-out business architecture involves:

Case Management Feature (A):

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

DX API Synchronization (C):

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

References:

Pega's Center-out Business Architecture Overview

Pega Documentation on Case Management

Pega DX API Documentation

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 configure a process where three physicians can independently perform evaluations and ensure that only two evaluations are necessary to advance the case to the medical director, you should use the "Some" join condition in Pega.

Understanding Join Conditions in Pega:Pega provides various join conditions to handle subprocesses. The join conditions include "Any," "Some," and "All." These conditions dictate how and when the main process can proceed based on the completion of subprocesses.

Some Join Condition:The "Some" join condition allows the main process to advance once a specified number of subprocesses have been completed successfully. In this scenario, since only two out of the three physicians need to complete their evaluations for the case to move forward, the "Some" join condition is appropriate.

Configuration Steps:

Step 1: Define the subprocesses for the physicians' evaluations.

Step 2: Use the "Split For Each" shape to create multiple subprocesses.

Step 3: Configure the "Some" join condition and set the number of required completions to 2.

Step 4: Ensure that the main process waits for two evaluations before moving to the medical director review.

References:Pega Documentation on Join Conditions provides detailed steps and examples for configuring different join conditions, including the "Some" join condition.

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

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

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

References: Pega Platform documentation on activities and functions.

To address the requirement where users working in one application need to create cases in another application, the recommended approach is to implement Federated Case Management (FCM).

Federated Case Management: FCM allows different Pega applications to share and manage cases across multiple systems. This approach enables seamless case creation and management, ensuring that users can interact with cases regardless of the application they are working in.

Synchronization and Communication: FCM facilitates synchronization and communication between different Pega instances, ensuring that case data is consistent and accessible across the applications.

References: Pega Platform documentation on Federated Case Management.

Text Description automatically generated with low confidence

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.

Kubernetes is a powerful orchestration platform for managing containerized applications across a cluster of machines. The two statements that are true about Kubernetes capabilities are:

Auto Scaling Pods Up and Down (C):

Kubernetes can automatically scale the number of pods up or down based on the resource usage and demand. This is done using the Horizontal Pod Autoscaler, which adjusts the number of pod replicas based on CPU utilization or other select metrics.

Orchestrate Pods and Their Dependencies (D):

Kubernetes orchestrates the deployment, scaling, and operations of application containers across clusters of hosts. It manages the scheduling of pods, ensuring that containerized applications are running as desired and can handle the orchestration of dependencies between containers.

References:

Kubernetes Documentation on Horizontal Pod Autoscaler

Kubernetes Documentation on Pod Lifecycle

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

For U+ Bank's project to present credit card offers based on engagement policies, the conditions should be matched with the appropriate engagement policy criteria as follows:

The customer must not be flagged as a defaulted borrower

Engagement Policy: Eligibility

Explanation: This condition ensures that only customers who meet basic eligibility criteria, such as not having defaulted on previous loans, are considered for the offers.

Customer already owns a higher-value offer

Engagement Policy: Suitability

Explanation: This condition checks if the offer is suitable for the customer, ensuring that the customer does not already have a better offer, which would make the new offer irrelevant or less attractive.

Must be a resident of New York City

Engagement Policy: Applicability

Explanation: This condition pertains to the applicability of the offer, ensuring that the offer is relevant to the customer's location, which in this case is specific to residents of New York City.

The savings product offers are relevant only if the customer has not explicitly opted out of direct marketing

Engagement Policy: Eligibility

Explanation: This condition is part of the eligibility criteria, ensuring that only those customers who have not opted out of direct marketing are eligible to receive the offers.

Inappropriate for customers with a credit score < 300 as they are likely to default

Engagement Policy: Suitability

Explanation: This condition ensures the suitability of the offer, filtering out customers with a low credit score who are at a higher risk of defaulting, making them unsuitable for certain offers.

Step by Step Comprehensive Detailed Explanation with References:

Eligibility Conditions:

Conditions that determine the basic qualifications or permissions for receiving offers fall under eligibility. This includes criteria such as not being flagged as a defaulted borrower and not opting out of direct marketing.

Applicability Conditions:

Conditions that ensure the offer is applicable to the customer's specific situation or context fall under applicability. This includes location-based criteria like being a resident of New York City.

Suitability Conditions:

Conditions that determine if the offer is appropriate for the customer's current status or needs fall under suitability. This includes ensuring the customer does not already have a better offer and checking the credit score to prevent offering products to those at high risk of default.

References: According to Pega’s best practices for engagement policies, eligibility criteria are used to filter out ineligible customers, applicability ensures the offer is relevant to the customer’s situation, and suitability checks ensure the offer is appropriate for the customer’s current needs and status.

To ensure the host system origin is trusted in a Pega web mashup implementation:

In the authentication service JNDI binding parameters, specify the protocol, host, and port (Answer A):

Explanation: Specifying these parameters ensures that the Pega system recognizes and trusts the origin of the mashup requests.

Wait Shape with Case Dependency:

The best practice in Pega for handling dependencies between cases is to use a Wait shape configured with case dependencies. This ensures that the mortgage case waits for the completion of the credit report case before proceeding.

By configuring the Wait shape to monitor the status of the credit report case, it ensures that the mortgage case automatically resumes once the credit report case is resolved.

Process Configuration:

In the mortgage case process, insert a Wait shape where the process needs to pause for the credit report.

Configure the Wait shape to depend on the resolution of the credit report case. This can be done by specifying the case ID of the credit report as a dependency.

Automation and Efficiency:

This method is efficient as it automates the waiting process without manual intervention. The mortgage case resumes automatically once the credit report case completes, ensuring smooth workflow automation.

It avoids the need for complex SLAs or additional activities to check the status of the credit report case, simplifying the process design.

Routing to Specialist:

Once the Wait shape condition is satisfied, the process flow continues to the step that routes the mortgage case to a specialist.

This ensures that the mortgage case is routed at the appropriate time, maintaining process integrity and efficiency.

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.

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.

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

Important points to follow while designing enterprise applications include:

Modular Architecture (A):

Implementing a modular architecture allows different parts of the application to be developed, maintained, and scaled independently. This minimizes the impact of changes, making the system more resilient and easier to manage.

Communication Channels (B):

Focusing on required communication channels ensures that the application meets the needs of its users, enhancing user productivity and satisfaction. This involves integrating the necessary communication tools and channels directly into the application workflow.

References:

Pega Best Practices for Application Design

Enterprise Architecture Principles

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.

To configure a report definition that lists new customer cases created in a given day and the average opening balance for all account child cases for each customer, you should use the "class join" feature in Pega. This feature allows you to join data from different classes, which is essential when dealing with cases and their child cases. Specifically, you can create a join between the customer case class and the account child case class to aggregate the average opening balance.

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

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

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

 Dynamic Layout: This layout allows for flexible arrangements of items within the form. It supports wrapping content based on screen size, making it ideal for responsive design.

 Row Configuration: Within a dynamic layout, elements can be configured to flow like words in a sentence, wrapping to the next line as necessary. This is essential for displaying book covers in a row that adapts to different screen widths.

 Responsive Behavior: Dynamic layouts are designed to handle varying screen sizes seamlessly, ensuring that the UI remains user-friendly on all devices.

 Reference: Pega documentation emphasizes the use of dynamic layouts for creating flexible and responsive UI designs (Pega Platform 8.7 Documentation, User Interface - Layouts).

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.

Team A publishes branch,

Automation server merges three branch,

Team B and C rebase the application

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

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

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

References:

Pega Academy: System Queue Management

Pega Documentation: Understanding Agent Status and Queue Management

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.

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.

Regarding inbound email processing:

An incoming email reply is linked to its original case by the case ID in the subject of the email (Answer A):

Explanation: The case ID in the subject line allows the system to match the incoming email with the existing case, ensuring proper tracking and processing.

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.

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.

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

Advanced Mode Configuration:

Configure the agent to run in Advanced mode to gain more control over its execution.

Periodic Pattern:

Set the agent to run with a Periodic pattern, scheduling it to execute daily at midnight.

Ensure the agent checks for customer birthdays and sends out emails accordingly.

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

 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

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.

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.

 Setting pxThread.isWebMashup:

In the pyDefault Data Transform for a case, setting pxThread.isWebMashup to True ensures that App Studio users see the same views displayed by a Mashup interface.

 Associated Privilege Visibility Conditions:

Using associated privilege visibility conditions allows App Studio users to view and configure sections only shown to external personas at design time.

 References:

Pega documentation on Mashup interface development in App Studio outlines these practices to ensure seamless integration and development.

 Therefore, the correct answers are:

B. In the pyDefault Data Transform for a case, set pxThread.isWebMashup to True by using an Application Setting. App Studio users then see the same views that are displayed by a Mashup interface when it is configured to use the Create a case option.

C. Use associated privilege visibility conditions. At design time, an App Studio user is able to view and configure sections that are only shown to external personas.

Graphical user interface, text, application Description automatically generated

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.

Pega Customer Service functions as the customer interaction system of record within the enterprise architecture. It manages customer interactions and provides a comprehensive view of customer information and history, facilitating efficient and effective customer service.

References:

Pega Customer Service: Customer Interaction Management

Pega System of Record: Defining System of Record

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.

To avoid recalculating declarative properties when extracting data with BIX:

BIX Command Line Options:

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

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

Configuration:

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

References:

Pega Business Intelligence Exchange (BIX) User Guide

Pega Documentation on Declarative Rules

To 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

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

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.

When deciding between using a Wait shape or an assignment with an SLA in a Pega case flow:

Assignment with SLA (C):

An assignment with an SLA is preferred when there is a requirement to adjust the case urgency at the time of assignment creation. SLAs allow you to specify goals, deadlines, and escalation actions that can modify the urgency of the case.

This approach is suitable when you need to ensure that the case is handled within a certain timeframe and that the urgency can dynamically change based on business rules.

References:

Pega Case Management Best Practices

Pega SLA Configuration Guide

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

Pega Case Management: Case Management

Create a New Mapping Servlet:

Go to the servlet configuration section in Pega.

Define the New URL Pattern:

Create a unique URL pattern that will be mapped to the new LDAP authentication servlet.

Implement the Servlet Logic:

Ensure the new servlet contains the necessary logic for LDAP authentication.

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.

The system will consider the assignments with urgency value equal to and greater than the specified value in the Operator rule. Once all assignments are processed from the work queue based on the threshold urgency value, the lower urgency assignments are then considered.

Urgency Thresholds: The system checks the urgency of assignments in each work queue. Assignments with an urgency equal to or greater than the threshold are considered first.

Get from Work Queues First: With this option selected, the system prioritizes processing work queues before considering individual workbaskets.

Lower Urgency Assignments: After processing assignments meeting the urgency thresholds, the system will then consider lower urgency assignments if there are no higher urgency tasks left.

 Engagement Policy Condition: This condition is used to specify the criteria that a customer must meet to be eligible for an offer, such as having an annual income above USD 150,000 for a Gold credit card.

 Implementation: In the Next-Best-Action Designer, configure the engagement policy to include an income threshold check to ensure only eligible customers receive the offer.

 Reference: Pega documentation outlines how to set up engagement policies to define conditions under which offers are presented (Pega Customer Decision Hub, Engagement Policies).

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 ensure claim processors work on the most urgent claims first, consider the following approach:

Advanced Agent: Implement an advanced agent on a dedicated node to increment the pyUrgencyAssignAdjust value by 1 for each assignment that meets the selection criteria. This agent can run at the start of each day to update the urgency of all claims in the PendingProcessing workbasket.

Dedicated Node: Using a dedicated node ensures that the urgency update process does not interfere with other application processes and can handle the large volume of claims efficiently.

References: Pega Platform documentation on advanced agents and configuring assignment urgency.

To enable support for both case types (expense report and purchase requests) for offline users on a mobile device:

Configure the application record to enable offline access. This setting prepares the application for offline capability.

Configure the user's access group to enable offline access. This step ensures that users have the necessary permissions and configurations to use the application offline.

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

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

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

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

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.

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.

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.

Text, letter Description automatically generated

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

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.

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