Pega Marketing Consultant study plan

Pega Marketing Consultant · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Next-Best-Action and decision management design

Map the Next-Best-Action lifecycle from customer interaction through arbitration, and write a one-paragraph description of each stage in your own words
Define the core NBA building blocks (proposition, action, treatment, eligibility, suitability, prioritization) and give one concrete business example for each
Explain how engagement policy and contact limits influence which action finally reaches the customer
Draw a decision flow diagram showing where business rules, predictive models, and adaptive learning each enter the process

A one-page annotated diagram of the NBA lifecycle with all six building blocks defined and one worked business example

Week 2

Identify the four standard NBA arbitration stages and describe the input and output of each
Explain the difference between eligibility, applicability, suitability, and prioritization rules and predict which stage a given rule belongs to
Describe how adaptive models produce propensity scores and how those scores feed prioritization
Translate three sample business requirements into candidate NBA design decisions with trade-offs noted

A table of 10 sample business rules, each classified by arbitration stage with a one-sentence justification

Week 3

Decompose a decision strategy into its strategy components (data, proposition, prioritization, and output) and describe the role of each
Explain how a decision strategy differs from a decision table and when each is appropriate
Trace how customer properties, interaction history, and model scores flow through a strategy to produce a final ranked action list
Design the strategy skeleton for a simple cross-sell scenario, naming every component and its inputs

A written strategy design for one cross-sell scenario, listing each component, its inputs, and its expected output

Week 4

Describe how proposition and action data are modeled and referenced inside a decision strategy
Explain the role of the decision data store and how strategies read and write to it
Identify where simulation and strategy testing fit in the development cycle and what each validates
Configure the data and proposition components of a strategy so they resolve correctly for a test customer

A working strategy skeleton in a development environment that returns a ranked action list for at least three test customers, with results documented

Week 5

Describe the purpose of each major Customer Decision Hub configuration area: data, propositions, strategies, and engagement policies
Explain how operator roles and access groups control who can change what in a decisioning application
Outline the steps to onboard a new proposition from data setup through to it being available in arbitration
Identify the configuration artifacts that must be versioned and promoted between environments

A configuration checklist covering the end-to-end onboarding of one new proposition, with the responsible operator role named for each step

Week 6

Describe how adaptive models are monitored and what signals indicate a model needs attention
Explain the difference between a design-time configuration change and a run-time data change and how each is governed
Identify the main integration points between Customer Decision Hub and surrounding systems (customer data, interaction channels, outbound delivery)
Describe how real-time container and batch execution differ in when decisions are made and what data is available

A monitoring and governance summary that names three model health signals, three integration points, and the owner of each

Week 7

Outline a phased delivery approach from requirements through design, build, test, and go-live for a decisioning solution
List the environment topology (development, staging, production) and describe what is promoted at each stage
Identify the testing layers (unit, strategy, simulation, user acceptance) and what each layer is responsible for proving
Describe the risks of changing engagement policies or arbitration logic in production and how to mitigate them

A delivery plan for a hypothetical two-month decisioning rollout, naming environments, promotion gates, and test layers

Week 8

Re-derive the NBA lifecycle and arbitration stages from memory and check against your week 1 and 2 notes
Redesign one decision strategy end to end, justifying each component against a stated business requirement
Answer a set of mixed-domain practice questions and record every miss with the underlying concept it exposed
Write a short explanation of how a design decision in domain 1 constrains configuration choices in domains 3 and 4

A consolidated review sheet of weak concepts plus a rewritten strategy design that addresses each recorded gap

Week 2: You can classify any given business rule into the correct arbitration stage without notes and explain why

Week 4: A strategy skeleton runs in a development environment and returns a ranked action list for multiple test customers

Week 6: You can describe proposition onboarding, model monitoring, and the main integration points from memory in under ten minutes

Week 8: Practice-question accuracy is above 75 percent across all four domains, with every miss traced to a named concept