PMP — PMI Project Management Professional - 2026 Exam Refresh Exam Blueprint
Independent exam blueprint for candidates preparing for the PMI Project Management Professional (PMP) - 2026 Exam Refresh.
How to Use This Exam Blueprint
Use this page as a practical readiness map for the PMI Project Management Professional (PMP) - 2026 Exam Refresh, exam code PMP. It is organized around the work a project manager must be ready to perform: choosing an approach, leading people, managing constraints, responding to change, protecting value, and using the right artifact at the right time.
This checklist does not assign exact official weights or imply a guaranteed section structure. Treat each area as a review checkpoint:
- Mark each topic as ready, needs review, or needs scenario practice.
- For every weak area, ask: “Can I decide what to do next in a messy project scenario?”
- Use the tables to connect terms, artifacts, actions, and judgment calls.
- Finish with mixed practice that forces you to choose between plausible actions, not just define vocabulary.
Exam identity and readiness focus
| Item | Checklist use |
|---|---|
| Vendor/provider | PMI |
| Official exam title | PMI Project Management Professional (PMP) - 2026 Exam Refresh |
| Exam code | PMP |
| Page purpose | Independent Exam Blueprint for study planning and final review |
| Main readiness question | Can you apply project management judgment across predictive, agile, and hybrid situations? |
| Best use | Identify weak topic areas before doing full-length or mixed scenario practice |
Topic-area readiness table
| Readiness area | What to review | You are ready when you can… | Scenario cues to practice |
|---|---|---|---|
| Project context and business need | Business case, project purpose, constraints, assumptions, success criteria, strategic alignment | Explain why the project exists and how decisions should support expected value | A sponsor asks for scope that does not support the business objective |
| Governance and decision rights | Sponsor role, project manager authority, steering groups, escalation paths, approvals, governance tailoring | Identify who should decide, who should be informed, and when escalation is appropriate | A conflict exceeds the project manager’s authority |
| Project charter and initiation | Charter purpose, high-level scope, objectives, risks, stakeholders, milestone assumptions | Distinguish pre-project analysis from authorized project work | A project manager is assigned before full requirements are known |
| Stakeholder engagement | Identification, analysis, prioritization, engagement strategies, communication preferences | Choose a stakeholder strategy based on influence, interest, resistance, and expectations | A powerful stakeholder becomes resistant late in delivery |
| Team leadership | Servant leadership, conflict management, motivation, coaching, empowerment, team development | Select leadership actions that improve ownership and performance without bypassing the team | A team member is underperforming or two specialists disagree |
| Communication | Communication methods, information needs, feedback loops, reporting, transparency, information radiators | Match communication style and frequency to stakeholder needs and project context | Executives want summaries while delivery teams need detailed blockers removed |
| Delivery approach selection | Predictive, agile, adaptive, iterative, incremental, hybrid | Justify an approach based on uncertainty, change frequency, stakeholder availability, risk, and product clarity | Requirements are evolving but a fixed regulatory date remains |
| Scope and requirements | Requirements elicitation, scope baseline, WBS, backlog, acceptance criteria, definition of done | Prevent gold plating, manage ambiguity, and verify that delivered work meets agreed needs | A customer requests “just one small addition” mid-delivery |
| Schedule and flow | Activities, dependencies, critical path, float, milestones, iteration planning, lead/lag, throughput | Interpret schedule data and choose recovery actions without ignoring risk or quality | A critical dependency slips and the team proposes overtime |
| Cost and resources | Budget, cost baseline, estimates, reserves, earned value, resource constraints | Interpret performance data and recommend corrective actions | CPI or SPI trends show performance drifting from plan |
| Quality | Quality planning, assurance, control, acceptance, prevention vs inspection, continuous improvement | Distinguish building quality in from checking quality after the fact | Defects are found repeatedly at the end of each release |
| Risk and uncertainty | Risk identification, qualitative/quantitative thinking, responses, triggers, residual risk, issue conversion | Choose appropriate risk responses and update the right artifact | A previously identified risk occurs and impacts the schedule |
| Change control | Change requests, impact analysis, approval, baselines, configuration management, backlog reprioritization | Decide whether a request needs formal change control or backlog refinement | A stakeholder asks the team to start work before approval |
| Procurement and vendors | Make-or-buy thinking, contracts, vendor performance, acceptance, claims, procurement closeout | Know when to involve procurement, legal, sponsor, or vendor management roles | A supplier delay threatens a milestone |
| Benefits and value delivery | Benefits realization, outcomes, value metrics, prioritization, minimum viable outcomes, transition | Connect delivery choices to business value, not only scope completion | The team can deliver more features, but the most valuable feature is at risk |
| Ethics and professionalism | Responsibility, respect, fairness, honesty, transparency, conflicts of interest | Choose actions that protect integrity, stakeholders, and the profession | A manager asks you to hide unfavorable project data |
| Closing and transition | Acceptance, handoff, lessons learned, final reporting, release of resources, archiving | Close work deliberately and preserve knowledge for future projects | The customer accepts delivery but operational support is not ready |
Can you do this?
Initiate and frame the work
- Explain the difference between a business need, project objective, deliverable, outcome, and benefit.
- Identify when a project charter is needed and what it authorizes.
- Recognize assumptions, constraints, exclusions, and high-level risks in a scenario.
- Determine whether a request belongs in initiation, planning, execution, monitoring/control, or closing.
- Identify the sponsor’s role versus the project manager’s role.
- Decide what to clarify before committing to scope, schedule, or budget.
- Connect project success criteria to business value rather than task completion alone.
Plan and tailor the approach
- Choose predictive, agile, or hybrid practices based on product uncertainty and delivery constraints.
- Tailor governance without removing accountability.
- Select planning artifacts that fit the delivery approach.
- Build a stakeholder engagement approach from influence, interest, expectations, and communication needs.
- Distinguish a risk response from an issue workaround.
- Explain how scope, schedule, cost, quality, resources, risk, and stakeholder expectations interact.
- Decide when progressive elaboration is appropriate.
Execute, monitor, and control
- Interpret project performance data and recommend a corrective action.
- Decide whether to update the risk register, issue log, change log, backlog, schedule, or lessons learned register.
- Recognize when to escalate and when to resolve at the team level.
- Distinguish quality assurance activities from quality control activities.
- Handle approved change without bypassing baselines or stakeholder communication.
- Manage dependencies, blockers, vendor delays, and resource conflicts.
- Keep project decisions aligned to value, risk, and agreed constraints.
Lead people and stakeholders
- Choose a conflict resolution approach based on urgency, stakes, relationship, and facts.
- Apply servant leadership by removing impediments and enabling team ownership.
- Support team formation, norms, psychological safety, and accountability.
- Coach rather than command when the team can solve the problem.
- Communicate bad news transparently and with options.
- Manage resistant stakeholders through engagement, not avoidance.
- Adapt communication for executives, customers, team members, vendors, and regulators.
Deliver value and close responsibly
- Confirm acceptance criteria before declaring work complete.
- Prioritize work using value, risk, dependencies, and stakeholder need.
- Support transition to operations, customer support, or business ownership.
- Capture lessons learned during the project, not only at the end.
- Verify closure of contracts, open issues, unresolved risks, and administrative records.
- Release resources appropriately.
- Evaluate whether expected benefits can be measured after delivery.
Delivery approach and tailoring checks
| Situation | Likely exam decision point | Be ready to decide… |
|---|---|---|
| Requirements are stable and compliance-heavy | Predictive planning and stronger baseline control may be appropriate | What must be planned before execution and what changes require approval |
| Requirements are uncertain and stakeholder feedback is frequent | Adaptive or iterative delivery may reduce risk | How to use backlog refinement, increments, reviews, and feedback |
| Fixed date with evolving feature detail | Hybrid approach may be needed | What should be baselined and what can remain adaptive |
| Senior leaders want certainty before discovery is complete | Progressive elaboration may be necessary | How to communicate uncertainty honestly without overcommitting |
| Team is self-organizing but blocked by external dependency | Servant leadership and escalation may both apply | Whether to remove impediments directly, facilitate, or escalate |
| Customer wants faster delivery | Trade-off analysis is required | Whether to adjust scope, resources, schedule, risk, quality, or approach |
| Frequent change requests are disrupting work | Governance or backlog discipline is needed | Whether changes are defects, new scope, reprioritization, or uncontrolled churn |
| Vendor work affects the critical path | Procurement and schedule risk intersect | How to monitor vendor performance and protect key milestones |
Predictive readiness prompts
- Can you identify baselines and explain how they are controlled?
- Can you separate planning from execution while still allowing progressive elaboration?
- Can you interpret critical path, float, milestones, and schedule compression choices?
- Can you explain when formal change control is required?
- Can you describe how acceptance, verification, and validation differ?
Agile and adaptive readiness prompts
- Can you explain why frequent feedback reduces delivery risk?
- Can you distinguish product backlog, sprint or iteration backlog, increment, acceptance criteria, and definition of done?
- Can you identify when the product owner, team, facilitator, sponsor, or customer should act?
- Can you choose between reprioritizing the backlog, removing an impediment, refining requirements, or escalating a constraint?
- Can you explain how transparency, inspection, and adaptation support value delivery?
Hybrid readiness prompts
- Can you identify which parts of a project should be governed predictively and which should remain adaptive?
- Can you manage fixed milestones while allowing evolving solution detail?
- Can you reconcile a formal change process with backlog reprioritization?
- Can you communicate hybrid expectations to stakeholders who assume only one approach is being used?
- Can you protect business value when teams use different delivery cadences?
Artifact checklist
| Artifact or information source | Purpose | Readiness cue |
|---|---|---|
| Business case | Explains why the project is worth doing | Use it to evaluate alignment and value trade-offs |
| Benefits management information | Defines expected benefits and how they may be realized | Use it when scope completion does not guarantee value |
| Project charter | Authorizes the project and project manager | Use it to identify objectives, sponsor, high-level scope, and constraints |
| Stakeholder register or analysis | Captures stakeholder details, influence, interest, and engagement needs | Use it when communication or resistance is central to the scenario |
| Communications plan | Defines what information goes to whom, when, and how | Use it when stakeholders are uninformed or overloaded |
| Team charter | Establishes team norms, working agreements, and expectations | Use it for team behavior, conflict, and collaboration questions |
| Requirements documentation | Captures stakeholder and product needs | Use it to clarify what should be delivered |
| Scope statement | Defines project and product scope boundaries | Use it when scope ambiguity or exclusions matter |
| WBS or scope decomposition | Breaks deliverables into manageable work | Use it for predictive scope planning and estimating |
| Product backlog | Ordered list of product work | Use it when value, feedback, and reprioritization are emphasized |
| Acceptance criteria | Conditions for accepting a deliverable or story | Use it to determine whether work is complete |
| Definition of done | Shared quality/completion standard | Use it when teams disagree about readiness or quality |
| Schedule baseline | Approved schedule model | Use it when measuring schedule variance or impact |
| Cost baseline | Approved budget over time | Use it when evaluating cost performance |
| Resource plan | Describes resource needs, roles, and availability | Use it when staffing or skill constraints affect delivery |
| RACI or responsibility matrix | Clarifies roles and accountability | Use it when ownership is unclear |
| Risk register | Tracks identified risks, owners, responses, and triggers | Use it before risks occur and after responses are updated |
| Issue log | Tracks current problems requiring action | Use it after a risk or problem has materialized |
| Change log | Tracks change requests and outcomes | Use it when formal changes are submitted or approved |
| Lessons learned register | Captures learning during the project | Use it for recurring problems or process improvement |
| Quality management information | Defines standards, methods, and acceptance expectations | Use it when prevention, inspection, or defects are central |
| Test results or quality control data | Shows whether deliverables meet requirements | Use it when deciding acceptance or corrective action |
| Procurement documents | Define vendor work, obligations, and acceptance | Use them when supplier performance or contract scope matters |
| Release or transition plan | Coordinates deployment, handoff, support, and adoption | Use it when delivery is complete but value is not yet realized |
Scenario decision path: what should you do next?
Use this simplified path when a PMP scenario gives you a problem, request, conflict, or performance signal.
flowchart TD
A[New situation appears] --> B{Is it a risk, issue, change, or information gap?}
B -->|Future uncertain event| C[Analyze risk and update risk information]
B -->|Current problem| D[Log or manage issue and assign owner]
B -->|Scope/baseline impact| E[Analyze impact before approval]
B -->|Unclear facts| F[Clarify with team, data, or stakeholder]
C --> G{Response within PM authority?}
D --> G
E --> H{Formal approval needed?}
F --> A
G -->|Yes| I[Act, communicate, and update artifacts]
G -->|No| J[Escalate with options and impact]
H -->|Yes| K[Submit through change control or governance]
H -->|No| L[Reprioritize or adjust within agreed process]
I --> M[Monitor outcome and capture lessons]
J --> M
K --> M
L --> M
Scenario and decision-point checks
| If the scenario says… | Do not jump straight to… | First exam-safe thinking path |
|---|---|---|
| A stakeholder requests new functionality | “Just add it” | Clarify, assess impact, follow change or backlog process |
| A team member is late repeatedly | Escalate immediately | Understand cause, coach, remove impediments, then escalate if needed |
| A risk trigger occurs | Create a new risk only | Treat it as an issue if it has happened; execute response and update records |
| A sponsor asks for an unrealistic date | Accept the date silently | Analyze options, constraints, trade-offs, risks, and communicate transparently |
| A vendor misses a deliverable | Blame the vendor | Review agreement, assess impact, communicate, and manage procurement risk |
| Defects are found after every release | Add more final inspection only | Improve quality practices earlier in the workflow |
| Stakeholders disagree about priorities | Let the loudest stakeholder decide | Use value, objectives, governance, and agreed prioritization criteria |
| Team morale is low | Replace the team | Investigate causes, improve safety, clarify goals, remove blockers |
| Requirements are unclear | Build the full solution anyway | Elicit, prototype, iterate, or clarify acceptance criteria |
| Executives request status | Send raw task details | Communicate concise status, risks, decisions needed, and business impact |
| Agile team is interrupted mid-iteration | Accept every interruption | Protect focus while using an agreed process for urgent work |
| Predictive project receives a major scope request | Ask the team to start immediately | Perform impact analysis and seek required approval |
Calculations and data interpretation checklist
You do not need to treat formulas as isolated memorization. Be ready to interpret what the number means and what action it suggests.
| Concept | Plain formula or rule | Ready when you can… |
|---|---|---|
| Cost variance | CV = EV - AC | Explain whether the project is under or over planned cost for earned work |
| Schedule variance | SV = EV - PV | Explain whether earned work is ahead or behind the planned value |
| Cost performance index | CPI = EV / AC | Interpret cost efficiency; below 1.0 usually signals unfavorable cost performance |
| Schedule performance index | SPI = EV / PV | Interpret schedule efficiency; below 1.0 usually signals unfavorable schedule performance |
| Estimate at completion | EAC = AC + bottom-up ETC, or EAC = BAC / CPI, depending on assumptions | Choose a forecast method based on whether past performance is expected to continue |
| Estimate to complete | ETC = EAC - AC | Estimate remaining cost from a forecast |
| Variance at completion | VAC = BAC - EAC | Identify expected budget overrun or underrun |
| To-complete performance index | TCPI = work remaining / funds remaining | Explain required future efficiency to meet a target |
| Three-point estimate | Expected value = (O + 4M + P) / 6 | Calculate a weighted estimate when optimistic, most likely, and pessimistic values are given |
| Communication channels | n(n - 1) / 2 | Recognize how communication complexity increases as people are added |
| Float or slack | Float = LS - ES, or LF - EF | Identify schedule flexibility and critical path sensitivity |
| Critical path | Longest path through dependent work | Determine which delays affect the project finish date |
| Lead and lag | Lead accelerates overlap; lag inserts waiting time | Interpret dependency adjustments correctly |
| Burnup or burndown trend | Visual trend, not a single formula | Explain whether work completed and work remaining support the target |
Formula readiness prompts
- Can you tell whether a variance is favorable or unfavorable?
- Can you explain why a project may be on budget but behind schedule?
- Can you choose the right EAC interpretation from the wording of the scenario?
- Can you identify the critical path from a small dependency table?
- Can you explain why adding people may increase communication complexity?
- Can you interpret trend data without assuming one metric tells the whole story?
People, leadership, and stakeholder checks
| Topic | What strong readiness looks like |
|---|---|
| Conflict management | You can choose collaboration, compromise, smoothing, forcing, or withdrawal based on context, while preferring constructive resolution when time allows |
| Servant leadership | You remove blockers, support autonomy, coach the team, and protect focus |
| Team development | You recognize forming, storming, norming, performing-style dynamics without overusing labels |
| Motivation | You look for causes such as unclear goals, lack of ownership, overload, poor recognition, or missing skills |
| Psychological safety | You promote openness, learning, and respectful disagreement |
| Stakeholder resistance | You engage early, listen, clarify concerns, and adapt communication |
| Escalation | You escalate when authority, risk exposure, conflict, or decision rights exceed the project manager or team |
| Virtual or distributed teams | You adapt communication, working agreements, collaboration tools, and cultural awareness |
| Negotiation | You seek mutually acceptable outcomes while protecting objectives and ethics |
| Ethics | You avoid hiding information, favoritism, conflicts of interest, and misleading reporting |
Risk, issue, and change distinction
| Situation | Classify as | Likely artifact or action |
|---|---|---|
| “This supplier might be late” | Risk | Risk register, response plan, owner, trigger |
| “The supplier is late now” | Issue | Issue log, impact analysis, corrective action |
| “The customer wants an added feature” | Change request or backlog item | Impact analysis, change control, or backlog prioritization |
| “The team found a defect” | Quality issue or nonconformance | Defect log, quality control, root cause analysis |
| “A law may change next quarter” | Risk and compliance concern | Risk response, monitoring, stakeholder communication |
| “The approved budget is insufficient” | Issue, possible change | Forecast, escalation, change request if baseline impact exists |
| “A stakeholder is not attending reviews” | Stakeholder engagement issue | Engagement strategy, communication adjustment |
| “Velocity is declining” | Performance signal | Inspect causes, remove impediments, improve flow |
Common weak areas and traps
| Weak area or trap | Why candidates miss it | Better exam habit |
|---|---|---|
| Treating every problem as a change request | Not all problems change scope, schedule, or cost baselines | Classify first: risk, issue, defect, change, or communication gap |
| Escalating too early | Escalation feels decisive but may bypass team responsibility | Try appropriate analysis, facilitation, and authority-based action first |
| Escalating too late | Some decisions exceed the project manager’s authority | Escalate with facts, options, impacts, and recommendation |
| Ignoring business value | Candidates focus only on completing tasks | Ask which option best protects outcomes and benefits |
| Confusing risk with issue | Future uncertainty versus current problem is easy to blur | If it has happened, manage it as an issue |
| Assuming agile means no planning | Agile uses adaptive planning, not absence of planning | Look for rolling wave planning, backlog refinement, and feedback loops |
| Assuming predictive means no change | Predictive projects still change through control processes | Use impact analysis and approved governance |
| Choosing the most authoritarian answer | Some options sound efficient but damage ownership or trust | Prefer facilitation, coaching, transparency, and collaboration when appropriate |
| Overlooking stakeholder analysis | Technical fixes may fail if stakeholder expectations are unmanaged | Revisit engagement, communication, and decision rights |
| Misreading EVM | Formula recall without interpretation leads to wrong actions | Translate numbers into cost, schedule, forecast, and response |
| Treating quality as inspection only | Inspection finds defects late | Build quality into planning, process, and acceptance |
| Forgetting lessons learned during execution | Lessons are not only closing artifacts | Capture and apply learning throughout the project |
| Confusing acceptance criteria and definition of done | Both relate to completion but at different levels | Acceptance criteria describe product expectations; definition of done defines shared completion quality |
| Picking the fastest option | Fast may increase risk, cost, or quality problems | Evaluate trade-offs and constraints |
| Ignoring procurement boundaries | Vendor work may require contractual handling | Review agreements and involve the right procurement authority |
Agile, predictive, and hybrid comparison
| Question | Predictive emphasis | Agile/adaptive emphasis | Hybrid emphasis |
|---|---|---|---|
| How is scope handled? | Defined and baselined earlier | Evolving backlog and discovery | Some scope fixed, some adaptive |
| How is change handled? | Formal change control for baseline impacts | Reprioritization through backlog and feedback | Both mechanisms may coexist |
| How is progress shown? | Milestones, baseline variance, deliverable completion | Increments, reviews, flow metrics, value delivered | Mixed reporting across workstreams |
| How are risks reduced? | Planning, analysis, reserves, controls | Short feedback cycles, experiments, early increments | Risk-based tailoring |
| How is customer feedback used? | At planned reviews, approvals, validation points | Frequently throughout development | Frequent feedback inside governed boundaries |
| What is the project manager’s challenge? | Control complexity and baseline integrity | Enable team, feedback, and value flow | Integrate different cadences and expectations |
Governance, escalation, and ethics checks
- Can you identify when the project manager should act within authority versus seek sponsor or governance approval?
- Can you explain why hiding unfavorable status is unethical?
- Can you respond to pressure to skip quality, safety, compliance, or required approvals?
- Can you recognize conflict-of-interest situations?
- Can you distinguish transparency from oversharing irrelevant detail?
- Can you prepare an escalation that includes impact, options, recommendation, and decision needed?
- Can you protect the team from inappropriate pressure while still being accountable to stakeholders?
- Can you update stakeholders when forecasts change instead of waiting for the next scheduled report if urgency requires it?
Final-review checklist by topic
Business value and benefits
- I can connect project work to organizational objectives.
- I can identify when a project is delivering outputs but not expected outcomes.
- I can prioritize work based on value, risk, and dependency.
- I can explain why benefits may be realized after project closure.
- I can spot when scope expansion threatens business value.
Stakeholders and communication
- I can identify the most important stakeholder in a scenario.
- I can select the best communication method for urgency, sensitivity, and audience.
- I can manage conflicting expectations using facts and agreed criteria.
- I can respond to resistance without ignoring or overpowering stakeholders.
- I can update the right engagement or communication artifact.
Team and leadership
- I can select coaching, facilitation, training, conflict resolution, or escalation based on context.
- I can identify when the team needs empowerment versus direction.
- I can respond to poor performance fairly and constructively.
- I can support distributed or cross-functional teams.
- I can recognize servant leadership in action.
Planning and baselines
- I can distinguish scope, schedule, and cost baselines.
- I can explain how assumptions and constraints affect planning.
- I can select appropriate estimating techniques.
- I can identify dependency and resource constraints.
- I can explain what changes when a baseline is approved.
Monitoring and control
- I can interpret variance, trends, forecasts, and thresholds.
- I can decide whether corrective action, preventive action, defect repair, or change request is appropriate.
- I can choose which artifact to update after an event.
- I can distinguish issue management from risk management.
- I can communicate performance honestly and actionably.
Quality and delivery
- I can distinguish quality assurance from quality control.
- I can use acceptance criteria to evaluate completion.
- I can identify root cause rather than only symptoms.
- I can explain why prevention is often better than late inspection.
- I can integrate quality expectations into agile, predictive, or hybrid delivery.
Risk and uncertainty
- I can identify threats and opportunities.
- I can choose avoidance, mitigation, transfer, acceptance, escalation, exploitation, enhancement, sharing, or acceptance based on the scenario.
- I can identify triggers, owners, residual risks, and secondary risks.
- I can convert a realized risk into issue management.
- I can explain when contingency or management reserve concepts matter at a practical level.
Procurement and external work
- I can identify when vendor performance affects risk, schedule, quality, or scope.
- I can avoid directing vendor work outside agreed channels.
- I can distinguish acceptance of vendor deliverables from internal quality checking.
- I can recognize when procurement, legal, sponsor, or contract authority should be involved.
- I can close procurement work deliberately.
Final-week checklist
| Timeframe | Focus | Checklist |
|---|---|---|
| Early final week | Close content gaps | Review your weakest topic areas, especially risk/change distinction, stakeholder scenarios, delivery approach selection, and EVM interpretation |
| Midweek | Mixed scenario practice | Practice questions that combine people, process, business value, and delivery approach judgment |
| Midweek | Error log review | Rework missed questions and write why the correct answer is better than the tempting answer |
| 2-3 days out | Formula and artifact refresh | Review EVM, critical path, communication channels, key artifacts, and when each artifact is updated |
| 1-2 days out | Decision pattern review | Practice “what should the project manager do next?” scenarios without over-reading |
| Day before | Light consolidation | Review notes, rest, and avoid trying to learn a large new topic from scratch |
| Exam day | Execution | Read the scenario carefully, classify the problem, eliminate extreme answers, and choose the action that best protects value, ethics, and agreed process |
Practical next step
Choose three weak readiness areas from this checklist and complete targeted practice before moving to broad mixed sets. For each missed item, record:
- The topic area.
- The scenario cue you overlooked.
- The artifact or decision point involved.
- Why the correct action is better than the tempting action.
Then return to mixed PMP practice until you can consistently explain your answer choices, not just recognize familiar wording.