PEGACPDC25V1 Questions and Answers

Pega Customer Decision Hub is a dynamic and adaptive system that constantly reevaluates the Next-Best-Action for each customer based on their interactions and feedback. If a customer rejects an offer, the system will update the customer profile and the offer performance, and then reapply the Next-Best-Action strategy to select and prioritize another offer that is more relevant and valuable for the customer. Verified References: [Pega Decisioning Consultant | Pega Academy]

Volume constraints allow you to limit the number of times an action is presented to customers across one or more channels. You can use volume constraints to implement the requirement that customers do not receive more than four promotional emails per quarter, regardless of past responses to that action by the customer. You can configure the volume constraint to limit the number of actions per channel per quarter and select the option to ignore previous responses. Outbound channel limits are used to limit the number of customers contacted per channel per run, not per quarter. Suppression policies are used to exclude customers from receiving an action based on certain conditions, such as opt-out preferences or recent purchases, not based on the number of times the action is presented. Suitability rules are used to determine whether an action is suitable for a customer based on their propensity, priority, or other criteria, not based on the number of times the action is presented. 

The propensity is a measure of how likely a customer is to accept an offer, based on their attributes and behaviors. The propensity is calculated by using predictive analytics models that learn from historical data and feedback. A low propensity value indicates that the offer is not relevant or attractive for the customer, and that similar customers have ignored or rejected the offer in the past. Therefore, if the offer click-through propensity decreased to 0.42, it most likely indicates that similar customers ignore the offer. Verified References: Pega Decisioning Consultant | Pega Academy

To achieve this requirement, you need to ensure that two tasks are complete in the Channel tab of the Next-Best-Action Designer: enable a web channel and map the real-time container to a business structure level. A web channel is a type of channel that allows you to deliver actions and treatments to your customers through your website or web app. You need to enable a web channel and configure its settings, such as authentication, security, and response format. A real-time container is a configuration that defines how to deliver actions and treatments to a specific channel. You need to map the real-time container that contains the Reward Card offer to a business structure level, such as Top-level or Issue-level, so that it can be available for delivery through the web channel. Verified References: [Pega Academy - Decisioning Consultant - Configuring channels], [Pega Academy - Decisioning Consultant - Configuring real-time containers]

A priority communication is a type of outbound interaction that allows you to send urgent messages to customers that are not related to any specific offer or proposition. You can use priority communications to inform customers about important events or changes that affect their relationship with your organization. In this case, the bank wants to share the new temporary contact details with all customers over an SMS, so creating a priority communication is the best option. Verified References: [Pega Decisioning Consultant | Pega Academy]

To access a property from an unconnected component, you use the component-dot-property construct. For example, if you want to access the property .Rank from an unconnected component named ActionRanking, you use ActionRanking.Rank. Verified References: Pega Academy - Decisioning Consultant - Accessing properties from unconnected components

A screenshot of a computer screen AI-generated content may be incorrect.

To test the visualization and the rendering of the email content, including replacing of the placeholders with customer information, you use a seed list from the Test email tab. A seed list is a predefined set of customers that you can use to test your email treatments before sending them to your target audience. You can select one or more customers from the seed list and send them a test email with your treatment. You can then verify how the email looks in their inbox and how the placeholders are replaced with their actual values. Verified References: [Pega Academy - Decisioning Consultant - Testing email treatments]

To enable access to customer properties in a Filter component, you need to use a Data Import component. A Data Import component allows you to read data from various sources, such as data sets, data pages, or data flows, and make it available for other components in the strategy. In this case, you need to use a Data Import component that reads from a customer data source that contains income and age properties. Verified References: Pega Academy - Decisioning Consultant - Importing data

Suppression rules are used to prevent customers from seeing offers that are not relevant or appropriate for them. For example, if a customer already has a higher value card, they should not see a lower value card offer. Therefore, suppression rules are the most likely condition that prevents Anna from seeing the new Rewards card offer. Verified References: [Pega Decisioning Consultant | Pega Academy]

A customer might receive an action that they already accepted if the volume constraint for that action is not configured to exclude previously accepted offers. This option can be enabled by selecting the Exclude previously accepted actions checkbox in the volume constraint configuration. The action suitability conditions are used to determine whether an action is suitable for a customer based on their propensity, priority, or other criteria, not based on their previous responses. The suppression rules are used to exclude customers from receiving an action based on certain conditions, such as opt-out preferences or recent purchases, not based on their previous responses. The actions are filtered based on eligibility before applying the volume constraints, so this option does not explain why a customer might receive an action that they already accepted. Verified References: Certified Pega Decisioning Consultant | Pega Academy, Volume constraints

Using the decision table, you can find the label for a customer with a credit score of 240 and an average balance of 35000 by following these steps:

Start from the top row and check if the customer’s credit score is less than 150. If yes, then the label is Very Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 175 and their average balance is less than 25000. If yes, then the label is Poor. If no, then move to the next row.

Check if the customer’s credit score is less than 200 and their average balance is less than 50000. If yes, then the label is Fair. If no, then move to the next row.

Check if the customer’s credit score is less than 250 and their average balance is less than 75000. If yes, then the label is Good. If no, then move to the last row.

The last row applies to all other cases that do not match any of the previous conditions. The label for this row is Very Poor.

In this case, the customer’s credit score is not less than 150, so the first row does not apply. The customer’s credit score is less than 175, but their average balance is not less than 25000, so the second row does not apply either. The customer’s credit score is not less than 200, so the third row does not apply. The customer’s credit score is less than 250 and their average balance is less than 75000, so the fourth row applies. Therefore, the label for this customer is Poor.

Volume constraints allow you to limit the number of times an action is presented to customers across one or more channels. You can use volume constraints to implement a policy that restricts the number of emails sent per day. Outbound channel limits are used to limit the number of customers contacted per channel per run, not per day. Suppression rules are used to exclude customers from receiving an action based on certain conditions, such as opt-out preferences or recent purchases. Applicability rules are used to determine whether an action is relevant for a customer based on their profile or context, not based on the number of times the action is presented. Verified References: Certified Pega Decisioning Consultant | Pega Academy, Volume constraints

To implement this requirement, you need to create an external email treatment and use an external tool to design the email. An external email treatment is a type of treatment that allows you to use a third-party email service provider to send emails to your customers. You can configure the external email treatment with the name of the provider, the authentication details, and the template ID that corresponds to the email content that you design using an external tool. This way, you can leverage your existing tools and processes for sending emails, while still using Customer Decision Hub to select the best actions and treatments for your customers. Verified References: Pega Academy - Decisioning Consultant - Creating external treatments

A screenshot of a survey AI-generated content may be incorrect.

Paul cannot see the Reward card offer because he rejected other credit card offers twice on the web channel and once in contact center in the past 15 days. This triggers the first contact policy that suppresses a group of credit card offers for 30 days if any credit card offer is rejected three times in any channel in the past 15 days. The Reward card offer is part of the credit card group, so it is suppressed for Paul for 30 days. The second contact policy that suppresses the Reward card offer for 7 days if it is rejected twice in any channel in the last 7 days does not apply because Paul did not reject the Reward card offer twice in any channel in the last 7 days. Verified References: [Certified Pega Decisioning Consultant | Pega Academy], Suppression policies system Following is the description of the image that was sent with question no:5:

This is a screenshot of a table with four columns and two rows.

The table has a header row with white text on a blue background.

The header row reads “Constraint name”, “Constraint mode”, “Constraint value”, and “Channel”.

The second row has black text on a white background.

The second row reads “Standard card”, “Return any action that does not exceed”, “100”, and “Daily”.

The table has a gray border and a light blue background.