Customer Decision Hub solution configuration
Domain focus
This domain tests configuration of a working Customer Decision Hub application: proposition content, data flows, prediction assets, and channel integration. The exam favors concrete configuration knowledge over abstract theory.
Core rules
- CDH runs as an application stack on Pega Platform. Know which rulesets and data sets belong to the decisioning layer versus the channel layer.
- Proposition management covers actions, treatments, and proposition data. Treatments define channel-specific content; action rules and treatment rules control when each is available.
- Data flows populate the customer profile, interaction history, and proposition catalog. Real-time containers use decision data flows for inbound requests; batch data flows support outbound.
- Prediction Studio holds adaptive models, scorecards, and strategies. Monitor model performance and refresh predictors when data changes.
- Channel configuration connects the NBA widget or Real-Time Container API to a strategy and returns ranked actions with treatments.
Worked example
To show an NBA banner on a web page, create an action and a web treatment, expose the action through proposition data, build a decision data flow that loads the customer and catalog, attach a strategy, and call the Real-Time Container from the page. Reasoning: the channel only renders what the strategy returns; a missing treatment or proposition mapping produces no banner even when the strategy ranks an action.
Traps
Hard-coding offers in a strategy instead of using proposition data; forgetting to map treatment content; confusing a data flow with a strategy; and letting adaptive models go unmonitored.