PEGAPCDC87V1 Exam Dumps - Pegasystems Pega Decisioning Consultant Questions and Answers

In Pega Customer Decision Hub, the property that is automatically recomputed for each decision component is "Priority." This property determines the order in which actions are evaluated and presented to the customer. The Priority property ensures that the most relevant and valuable actions are prioritized based on the defined criteria, including customer relevance, business rules, and real-time contextual data.

Correct Engagement Policy Configuration:

The customer must not be flagged as a defaulted borrower

Engagement policy: Eligibility

Customer already owns a higher-value offer

Engagement policy: Applicability

Must be a resident of New York City

Engagement policy: Eligibility

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

Engagement policy: Applicability

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

Engagement policy: Suitability

The customer must not be flagged as a defaulted borrower

Eligibility: Eligibility conditions determine whether a customer qualifies for an offer at a basic level. Being flagged as a defaulted borrower is a fundamental criterion to disqualify a customer from receiving certain offers.

To update the underlying decision strategy of an engagement policy condition, the change request should be created in the 1:1 Operations Manager Portal. This portal is designed for business users to manage changes and revisions in a controlled environment.

Understanding the Portals:

1:1 Operations Manager Portal: This portal allows business users to manage and implement business changes, such as updating decision strategies and engagement policies.

Pega Customer Decision Hub Portal: This portal is used for overall customer decision management but not specifically for creating change requests.

Dev Studio Portal: This portal is more technical and used for developing and configuring applications.

Development Manager Portal: This is generally used for deployment and managing development pipelines.

Steps to Create a Change Request:

Step 1: Log into the 1:1 Operations Manager Portal.

Step 2: Navigate to the section where you can create a new change request.

Step 3: Specify the details of the change request, including the engagement policy and the decision strategy that needs to be updated.

Step 4: Submit the change request for approval and implementation.

Benefits:

Using the 1:1 Operations Manager Portal ensures that changes are tracked, reviewed, and approved through a formal process, maintaining governance and control over business operations.

Example:

U+ Bank wants to update the decision strategy for credit card offers. A change request is created in the 1:1 Operations Manager Portal, detailing the required updates to the engagement policy conditions.

References:

Pega-Customer-Decision-Hub-User-Guide-85.pdf: "Managing business-as-usual changes with Pega 1:1 Operations Manager" section.

Pega documentation on "Revision management and change request process".

 Understanding the Decision Table:

The decision table provided returns a label based on a customer's credit score and average balance.

The rules are evaluated in order, and the first matching rule determines the result.

 Evaluating the Customer Data:

The customer has a credit score of 115 and an average balance of 15000.

We will evaluate each row of the decision table to see where these values fit.

 Rule Evaluation:

First Rule: Credit Score >= 130 and Average Balance >= 30000

Customer's Credit Score: 115 (not >= 130)

This rule does not match.

Second Rule: Credit Score >= 110 and Average Balance >= 20000

Customer's Credit Score: 115 (>= 110) but Average Balance: 15000 (not >= 20000)

This rule does not match.

Third Rule: Credit Score >= 90 and Average Balance >= 10000

Customer's Credit Score: 115 (>= 90) and Average Balance: 15000 (>= 10000)

Both conditions match, so the result is "C".

Fourth Rule: Credit Score >= 70 and Average Balance >= 1000

This rule is not evaluated because the previous rule matched.

 Conclusion:

According to the decision table, the result for a customer with a credit score of 115 and an average balance of 15000 is "B".

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.

In response to the real-time container request by Customer Decision Hub, the U+ Bank website receives only relevant action details and its treatment details. This information includes the specifics of the action to be displayed (such as the offer) and the associated treatment (such as the banner or message), enabling the website to present personalized and contextually relevant offers to customers.

Correct Action Hierarchy Levels:

Free 4G upgrade

Action Hierarchy Level: Action

Retention

Action Hierarchy Level: Business Issue

Tablets

Action Hierarchy Level: Group

Service

Action Hierarchy Level: Business Issue

Change address

Action Hierarchy Level: Action

Proactive retention

Action Hierarchy Level: Group

Free 4G upgrade

Action: This is a specific offering or initiative that can be presented to customers. It is a specific action within the broader strategy.

 Volume Constraints Implementation: To implement a policy that limits the sending of more than 500 emails per day, you need to configure volume constraints. Volume constraints allow you to set limits on the number of actions delivered within a specified period.

 Configuration: Create a volume constraint rule and set the maximum volume to 500 emails per day.

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.

Next-Best-Action Strategy Application: Pega's Next-Best-Action strategy can be applied to various business issues to optimize decision-making and enhance customer interactions.

Collections: Used to manage and optimize debt collection processes by determining the best actions to take with customers who have outstanding debts.

Service: Enhances customer service interactions by suggesting the most relevant actions or responses to customer inquiries and issues.

Retention: Focuses on retaining customers by identifying and executing actions that are most likely to keep them engaged and loyal.