PEGAPCDC87V1-QUESTION Practice Questions

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

Reference:

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

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

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

 Arbitration Factors: In Pega, arbitration is the process of prioritizing actions based on multiple

factors.

 Action Value: This is a specific arbitration factor that allows assigning financial values to actions.

 Purpose: Action value helps in determining the prioritization of actions based on their financial

impact or benefit to the business.

 Reference: According to Pega Customer Decision Hub documentation, the action value is indeed the

term used for this specific arbitration factor.

Decision Table Processing: The decision table is configured to evaluate the customer's credit score

and average balance to determine the risk segmentation.

Conditions Evaluation:

For a credit score of 240 and an average balance of 35,000:

The first condition checks if the credit score is >= 400 and = 30,000,

which does not match.

The second condition checks if the credit score is >= 200 and = 20,000,

which matches both the credit score (240) and the average balance (35,000).

Therefore, the correct result for these conditions is "Fair".

Reference: This is derived from typical Pega Decision Table configuration and logical evaluation as

described in Pega documentation on using decision tables for such scenarios .

 Identify the issue: When a customer receives an offer they have already accepted, it suggests that

the decision strategy did not consider previous interactions.

 Check strategy customization: Strategies in Pega CDH can be customized to include rules that

prevent the same offer from being presented again.

 Confirm the exclusion of previous offers: Specifically, you need to ensure that there is a suppression

rule or a logic to check the Interaction History to exclude previously accepted offers.

 Reference: Refer to the section on "Next-Best-Action Designer constraints" and "Engagement

policies" in the Pega Customer Decision Hub User Guide. These sections explain how to configure

rules to prevent repetitive offers.

To select the best offer from both groups based on customer behavior, you should ensure that the

propensity is enabled in the Arbitration tab. Propensity scores predict the likelihood of a customer

accepting a particular offer, and by enabling propensity, you can prioritize offers that have a higher

likelihood of acceptance, thus aligning offers with customer behavior.

Reference: Pega Customer Decision Hub User Guide, section on understanding Next-Best-Action

Designer arbitration.

Decision Table Results: In Pega, the standard property that holds the result of a decision table

evaluation is pxOutcome.

Property Usage: This property can be used to reference the result of the decision table within a

decision strategy.

Reference: This usage of pxOutcome is consistent with Pega's approach to handling results from

decision tables and mapping these results into strategies .

To access a property from an unconnected component in Pega Customer Decision Hub, you use the

component-dot-property construct. This allows you to reference properties from other components

within your strategy by specifying the component name followed by the property name. This

construct helps in accessing and using data across different components without directly connecting

them.

Reference: Pega Customer Decision Hub User Guide, section on strategy framework and property

access methods.

Goal of Next-Best-Action: The primary goal of Next-Best-Action is to balance customer needs with

business objectives. This approach ensures that actions taken are beneficial for both the customer

and the business, leading to better engagement and outcomes.

Reference: Pega's Next-Best-Action Designer documentation states that the strategy is designed to

align customer interactions with business goals.

 Best Practice for Emails: To ensure that emails load quickly and correctly across various email

clients, it's best practice to provide links to images rather than embedding them directly or attaching

them. This method ensures better compatibility and avoids large email sizes.

 Implementation: Including image links allows the email client to fetch images from a server,

ensuring that the email content remains lightweight and is displayed properly.

Reference: Pega's documentation on email treatments and best practices for including images in

emails recommends using links to images hosted externally .