Pegasystems Certified Pega Decisioning Consultant 25 (PEGACPDC25V1)

The requirement is to suppress a specific credit card offer if it has been shown three times within seven days.

When configuring a Contact Policy, the Tracking Level determines the granularity at which the policy is applied:

• Action: Tracks individual offers. This is necessary to suppress a specific credit card offer.
• Group: Tracks a collection of offers. This would be too broad for the stated requirement.

• Impressions: Means the offer was presented or shown to the customer, which directly matches the problem description of the offer being "shown".
• Clicks: Means the customer interacted with the offer by clicking it, which is not what the problem describes.

A new suppression policy, which is a type of contact policy in Pega Customer Decision Hub, needs to be applied to specific actions. After defining the contact policy, it must be associated with the relevant business structure where those actions reside. In Pega CDH, this association occurs within the Engagement policy tab of the corresponding Business Issue or Group (e.g., 'Home Loans' group). Here, you can link the defined contact policy to the actions or action groups it needs to govern, ensuring that the suppression rules are applied to home loan promotions. Options B, C, and D describe incorrect or insufficient methods for applying a contact policy to a specific action group.

Reference: https://docs-previous.pega.com/customer-decision-hub/87/configuring-contact-policies-customer-decision-hub

The volume constraint uses the 'Return any action that does not exceed constraint' mode. This mode ensures that if an action has remaining capacity (i.e., its limit has not been met), it can be selected. If an action's limit has been reached (0 remaining), it will not be returned.

• Protect Your Device: Has 5 remaining limits (5 > 0), so it qualifies.
• MyFone Buds: Has 7 remaining limits (7 > 0), so it qualifies.
• MyFone AirPods Pro: Has 0 remaining limits (0 is not > 0), so it does not qualify.

✅ Option A (Correct)
Reasoning: Pega's Next-Best-Action Designer includes a feature specifically for managing customer contact limits across different channels. Configuring customer contact limits for the email channel with a two-message monthly restriction directly addresses the requirement of limiting each customer to two promotional emails per month for compliance.

❌ Why the other choices are incorrect:

• Option B is incorrect: Engagement policies are primarily used to define eligibility, applicability, and suitability rules for propositions. While they can contain logic, setting a global channel frequency limit for all customers is not their primary purpose, nor are they restricted to customer groups only for such limits.
• Option C is incorrect: Suppression policies are used to prevent specific actions or offers from being presented, often based on previous interactions, customer opt-outs, or other specific criteria. While they involve thresholds and tracking, the dedicated feature for channel-wide frequency limits is 'Customer Contact Limits'.
• Option D is incorrect: Establishing context-level limits that track interactions across all channels would impose a limit on the total number of interactions regardless of channel. The requirement specifically targets the 'email channel' and 'promotional emails', necessitating a channel-specific limit, not a cross-channel aggregate limit.

The question states that an outbound run identifies a total of 150 Standard card offers, split evenly with 75 on the email channel and 75 on the SMS channel. A 'volume constraint' is then applied. Although the specific nature of the constraint is not detailed, the options provided offer insight.

Options A (75 emails, 25 SMS) and C (75 SMSes, 25 emails) both result in a total of 100 delivered actions (75 + 25 = 100). This strongly indicates that the applied volume constraint limited the total number of actions to 100.

Pega's volume constraints reduce the total number of propositions delivered. If the constraint was set to a maximum of 100 actions, then regardless of the specific distribution between email and SMS (which would depend on channel priorities or additional channel-specific constraints not provided), the total number of actions delivered would be 100.

Option D (150) is incorrect because a constraint was applied, implying a reduction from the initial identified offers. Options A and C describe potential distributions that sum to 100, but without specific channel prioritization or individual channel constraints, the exact distribution cannot be determined. Therefore, the most accurate answer regarding the total number of actions delivered is 100.

✅ Option D (Correct)

Reasoning: The system uses the "Return any action that does not exceed constraint" mode. This means that Pega will evaluate all qualified actions and return every action that passes its specific constraint checks. It does not stop at the first valid action or only return the highest priority valid action.

• Standard card (priority 60): While it has the highest priority, its volume is exhausted. Therefore, it exceeds its volume constraint (or fails the check for available volume) and will not be returned.
• Rewards card (priority 40): This card qualifies and has remaining volume. It does not exceed its volume constraint and will be returned.
• Premium card (priority 30): This card also qualifies and has remaining volume. It does not exceed its volume constraint and will be returned.

Therefore, both the Rewards card and the Premium card will be returned.

❌ Why the other choices are incorrect:

• Option A is incorrect: The Standard card's volume is exhausted, meaning it fails its constraint, despite being the highest priority.
• Option B is incorrect: The constraint mode "Return any action that does not exceed constraint" allows other actions to be returned if they pass their individual constraints, even if a higher priority action fails.
• Option C is incorrect: While the Premium card is available, the Rewards card is also available and meets its constraints, and the system is configured to return *any* action that does not exceed a constraint, not just the lowest priority available.

A decrease in the click-through propensity value directly indicates a reduced likelihood of customers engaging with or clicking on the offer. In the context of Pega's AI-driven decisioning, propensity scores predict customer behavior. A drop to 0.42 suggests that similar customers are less inclined to interact with the Gold credit card offer, effectively ignoring it. If customers were showing interest, the propensity would increase or remain high. If they were purchasing other offers, it might explain a lack of acceptance for the Gold card but not necessarily a decrease in click-through interest. Qualification issues relate to eligibility, not the initial propensity to click.

Reference: https://docs.pega.com/bundle/customer-decision-hub-88/page/customer-decision-hub/strategies/about-propensity.html

In Pega Customer Decision Hub (CDH), offers are prioritized using a formula that typically includes Propensity, Value, Business Weight, and Context Weight. The scenario describes a business need to 'boost' a specific offer (MyFone 14 Pro) to meet financial targets, implying a strategic override or temporary prioritization.

• A: Increase the business weight of the MyFone 14 Pro offer. Business weight is a primary lever for business users to explicitly boost or suppress offers based on current business objectives. Increasing the business weight directly increases the offer's overall prioritization score, making it more likely to be selected. This is the most direct and appropriate method for 'boosting' an offer to meet business goals.

Why the other choices are incorrect:

• B: Increase the business value of the MyFone 14 Pro offer. While increasing business value would also prioritize the offer, business value is generally intended to reflect the inherent monetary or strategic worth of the offer to the organization. Using it solely for 'boosting' might distort the actual financial reporting of the offer. Business Weight is specifically designed for tactical boosts.
• C: Increase the context weight of the MyFone 14 Pro offer. Context weight is similar to business weight but applies a prioritization factor based on specific contexts (e.g., channel, customer segment). The question implies a general boost, not one tied to a specific context, making a general business weight more suitable.
• D: Increase the starting propensity of the MyFone 14 Pro offer. Propensity represents the customer's likelihood to accept an offer, typically derived from predictive models. Manually increasing 'starting propensity' for a business objective would compromise the accuracy of customer behavior predictions. Business intent to boost an offer should be managed via business weights or value, not by artificially inflating propensity.

The AI Insight feature within the Customer Profile Viewer in Pega Customer Decision Hub provides transparent explanations for decisions, showing why certain actions were offered or filtered for a customer. Decisioning architects can leverage this by examining the filtering stages, including how engagement policies, applicability rules, and arbitration impact the outcome. By understanding which specific policies or conditions led to an action being filtered out, architects can identify misconfigurations or opportunities to refine their strategies. This direct insight into filtering mechanisms and policy application is crucial for optimizing overall strategy effectiveness and improving customer engagement.

The problem states that customers receive the wrong offer promotion 80% of the time when they call to check on bill status, leading to dissatisfaction. This highlights a contextual issue where the current offer prioritization formula is not adequately aligning with customer needs in a specific interaction context (calling about a bill).

To 'boost customers' needs in the prioritization formula' in such a scenario, particularly for a specific context, Context weighting is the most appropriate arbitration factor to configure. Context weighting allows you to adjust the relative importance of other arbitration factors (like Propensity, Business Value, and Business Weighting) based on the current interaction context. By configuring context weighting, the company can, for instance, increase the weight of Propensity (which reflects customer likelihood and thus, indirectly, their needs) during 'bill status' calls, thereby ensuring that more relevant offers (e.g., bill assistance, payment options) are prioritized over general sales promotions.

The other options are less suitable:

• Propensity (C): While Propensity measures the likelihood of a customer accepting an offer (a proxy for their needs), configuring Propensity usually refers to improving the underlying predictive model. The question asks for an arbitration factor to configure to *boost* customer needs in the formula, especially given a contextual problem. Context weighting provides the mechanism to adjust Propensity's influence in specific situations.
• Business value (B): This factor represents the value of an offer to the business, not directly to the customer's needs or satisfaction. Prioritizing based on business value alone would likely exacerbate the problem of irrelevant offers.
• Business weighting (D): This is a manual override to boost or suppress specific offers based on business rules. While it can be used to tactically push certain offers, it is a blunt instrument and not primarily designed to dynamically adapt to customer needs based on their current context in the prioritization formula. It doesn't inherently 'boost customer needs' but rather 'boosts specific offers determined by the business'.