PEGACPDC88V1 Certified Pega Decisioning Consultant Practice Questions

The Segment rule is the mechanism used to define the target audience for a campaign or schedule. It contains the criteria (e.g., 'All customers in the Gold loyalty tier' or 'Customers who have not made a purchase in 90 days') that Pega uses to query the customer base and create the list of individuals who are eligible to be processed for next-best-actions within that specific outbound schedule.

This is false. The Set Property component can set values on properties within the strategy's current context, which includes properties from the primary class, properties on the proposition (SR) class, and properties on any joined data pages or data sets. It is commonly used to set proposition-level properties, such as a calculated score or an eligibility flag.

The 'Engagement policies' step within the action creation process is where a business user defines the conditions that govern when an action is shown. This includes defining or selecting existing rules for Eligibility, Applicability, and Suitability. A rule based on credit score to determine appropriateness is a classic example of a Suitability rule.

This is a standard pattern for integrating with third-party distributors like ESPs. An outbound schedule or campaign is configured to run in Pega. Instead of using the built-in email treatment, the output of the decisioning process (customer ID, action ID, and any personalization attributes) is written to a file. This file is then securely transferred to the ESP, which uses the data to assemble and send the final emails. Pega provides connectors and templates to support this file-based handoff.

The diagram shows that the "Is Homeowner" component is a Decision Table. It takes the enriched customer data from the preceding Data Join component and applies a set of conditions to determine an outcome (in this case, true or false). This represents the application of a business rule, which then dictates the value of the Eligible property.

This is the most efficient approach. It first narrows down the set of potential actions using a Filter component, which reduces the data volume. It then makes a single, targeted real-time API call using a Data Join shape configured with a Connect-REST rule. The retrieved volatility data is then mapped to a property, which is subsequently used in a Decision Table to evaluate suitability. This sequence minimizes external API calls and processes only the relevant propositions, ensuring low latency and high scalability.

Adaptive models learn by analyzing the outcomes of actions recorded in the Interaction History. If the success outcome ('Accepted') is not being captured correctly, the model receives no positive evidence. It only sees impressions and possibly rejections ('Clicked' but not 'Accepted'). Without positive responses, the model cannot identify the predictors that lead to success and will therefore fail to improve its predictions, causing propensity scores to stagnate.

This is necessary to handle the distinct limits for each channel (3 emails in 7 days, 1 SMS in 24 hours).

This is required to implement the cross-channel dependency (no email for 48 hours after an SMS).

This is the best practice for handling urgent or emergency changes. Revision Manager allows for multiple revisions to be worked on in parallel. Creating a separate, dedicated revision for the urgent change isolates it from the larger, less urgent campaign work. This allows the critical regulatory change to be tested and deployed rapidly without pulling in unfinished and untested features from the other revision, minimizing risk. After deployment, the change can be incorporated into the main revision to ensure consistency.