PEGACPDC88V1 Sample Questions & Answers

This is true. An Action represents the core offer or proposition (e.g., '15% Off Home Insurance'). Treatments are the specific ways that Action is rendered in different channels. You would define a Web treatment (e.g., a banner image) and an Email treatment (e.g., HTML content) and associate both with the same Action.

Suitability rules are used to determine if an action is appropriate for the customer based on their individual circumstances, often related to risk, affordability, or ethical considerations. A high debt-to-income ratio is a classic example of a suitability condition designed to ensure the bank is offering products responsibly. Eligibility (e.g., age) and Applicability (e.g., not having the product already) were both met.

Real-time containers are configured with a 'Max number of actions' setting. For a web page with a large banner area or carousel, you might return 3-5 offers. However, for a mobile app where screen real estate is at a premium, it is a best practice to configure the container to return only one or two of the absolute best actions to avoid cluttering the user interface.

Context Weighting ('C') allows the system to dynamically increase or decrease the priority of an action based on the current context of the interaction. For example, if a customer is on the 'Billing' page of a website, a 'Paperless Billing' offer's context weight can be increased, making it more relevant and likely to be shown at that specific moment.

The Proposition Data component is required to import the available welcome package actions ('Standard', 'Silver', 'Gold') into the strategy.

A Data Join component is needed to query the external database table and enrich the strategy with the customer's loyalty status.

A Decision Table is the ideal component to implement the business logic that maps combinations of policy type and loyalty status to the correct welcome package.

The Issue/Group hierarchy provides the fundamental structure, or taxonomy, for all actions. It allows the business to organize actions logically (e.g., Issue: 'Acquisition', Group: 'Credit Cards'). This structure is then used by Next-Best-Action Designer to control which actions are considered, how engagement policies are applied, and how results are reported.

Relying on a daily batch process creates a window of time where the customer data is stale. The best practice for handling near real-time suppression is to capture the business event (the return) as it happens and stream it into Pega. A data flow can listen to this stream and update a dedicated data set (like a Decision Data Store) that the suppression logic can check during a real-time decision, ensuring immediate suppression.

This is the most effective design. First, a Predictive Model component is used to execute the churn model and add the 'Churn Risk Score' to the strategy context. This score is then used as an input to a single Decision Table. The Decision Table can efficiently handle the multiple conditions (Churn Risk, Policy Type) in a clear and maintainable format, returning the appropriate action ('10% Discount', 'Free Upgrade', 'Standard Renewal'). This approach cleanly separates the predictive analytics from the business rules.

Pega's treatment rules allow the use of expressions and functions directly within the content fields to achieve dynamic personalization. You can use a standard function like @if(Primary.Customer.FirstName != '', 'Hello ' + Primary.Customer.FirstName + ', here is an offer for you!', 'A special offer for our valued customer!'). This evaluates the condition and renders the appropriate text directly, making it the most direct and efficient method for this type of simple conditional logic within a treatment.