In attribute-based access control (ABAC) configuration, if you need to evaluate attributes from a data page, you should use the data page as the policy condition value in the access control policy condition. This allows the system to evaluate the current value from the data page when enforcing access control rules.

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

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

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

Graphical user interface, application Description automatically generated

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

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.

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

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

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

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

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

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

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

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

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

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