Pegasystems PEGAPCDC87V1 Exam Questions

Configuring Ethical Bias Policy:

To configure bias fields, the context of the bias must be selected, which usually pertains to customer-related properties.

Selecting Bias Fields:

Bias fields such as age, gender, and ethnicity are typically customer properties.

These properties are analyzed to detect and measure bias in decision strategies.

Detailed Explanation:

By selecting the Customer context, you can add and configure relevant customer properties to the bias policy.

This allows for comprehensive bias testing and ensures fairness in action distribution.

Verification from Pega Documentation:

Pega documentation confirms that customer-related properties are the primary context for configuring bias fields in ethical bias policies.

Requirement Analysis: U+ Bank wants to display a specific credit card offer (Standard Card) to every customer who logs in to the bank website using Pega Customer Decision Hub.

Identify Mandatory Artifacts: To implement this requirement in Pega Customer Decision Hub, certain artifacts are necessary:

Business Structure: This defines the business hierarchy in Pega CDH, such as issues and groups. For this scenario, a relevant business issue and group must be defined (e.g., Credit Cards -> Standard Card).

Action and Associated Web Treatment: The specific credit card offer (Standard Card) must be created as an action, and it must have an associated web treatment to display on the bank's website.

Real-time Containers: These containers facilitate real-time interactions by displaying the appropriate offers to customers when they log in to the website.

Not Mandatory Artifacts:

Customer Contact Policies: These policies are used to limit the number of interactions with customers over a period. However, they are not mandatory for simply displaying an offer upon login.

Customer Engagement Policies: While important for determining eligibility, applicability, and suitability of offers, they are not specifically mandatory for the basic requirement of displaying an offer upon login.

Conclusion: The three mandatory artifacts to implement the requirement are a business structure, an action and the associated web treatment, and real-time containers.

To limit the number of emails sent to customers irrespective of past outcomes with a particular offer and customer, customer contact limits should be implemented. Customer contact limits help control the frequency of communications with customers across different channels, ensuring that they do not receive an excessive number of messages.

Setting constraints and customer contact policy limits (Page 34-35)

Creating and managing contact policies (Page 66-67)

Identifying the Requirement:

The bank has chosen an email service provider that prefers receiving customer batches through a cloud storage location on either Microsoft Azure or Amazon S3.

The task is to find out how Pega Customer Decision Hub can integrate with these cloud storage solutions.

Evaluating Pega CDH Capabilities:

Pega Customer Decision Hub provides robust capabilities for integrating with various external systems and cloud storage solutions.

The documentation for Pega CDH supports writing action details directly to cloud storage solutions like Microsoft Azure and Amazon S3, which is in line with modern cloud infrastructure practices.

Process Overview:

Configuration:

Configure the external storage location (Azure Blob Storage or Amazon S3) within Pega CDH.

Action Flow:

Define the action flow to include steps for writing data to the specified cloud storage.

External Integration:

Use built-in connectors or custom integration points to handle data transfer securely and efficiently.

Reference and Supporting Documentation:

According to the Pega Customer Decision Hub User Guide, you can configure Pega CDH to write action details directly to cloud storage solutions like Microsoft Azure and Amazon S3 (refer to the section on configuring the delivery of multiple treatments and external integration points).

Pega-Customer-Decision-Hub-User-Guide-85.pdf

Pega-Customer-Decision-Hub-User-Guide-86.pdf

Pega-Customer-Decision-Hub-User-Guide-87.pdf

Identifying the Requirement:

The bank wants to leverage Pega CDH's Next-Best-Action capability to promote new offers on their website.

The task is to determine what information Pega CDH sends back to the website in response to a real-time container request.

Evaluating Pega CDH Capabilities:

Pega CDH's Next-Best-Action Designer is designed to handle real-time interactions and provides personalized recommendations.

The system returns comprehensive details to ensure the website can properly display and execute the recommended actions.

Process Overview:

Real-Time Container Request:

When the website sends a real-time container request, Pega CDH processes the request and identifies the most relevant actions based on customer data and engagement policies.

Response Details:

The response includes treatment details such as the action's visual elements (image URLs, descriptions) and relevant action attributes (e.g., offer type, benefits, eligibility criteria).

Reference and Supporting Documentation:

The Pega Customer Decision Hub User Guide clearly outlines that in response to a real-time container request, the system sends back the treatment details and relevant action attributes to ensure the offer can be presented accurately on the website.

Pega-Customer-Decision-Hub-User-Guide-85.pdf

Pega-Customer-Decision-Hub-User-Guide-86.pdf

Pega-Customer-Decision-Hub-User-Guide-87.pdf