Knowledge areas group the process model by subject: integration, scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholders. Learn them as a map of concerns that must stay joined — not as ten silos to recite under exam lights.
Ten areas, one project
Integration is the joining work: charter, plan, directing delivery, managing change, and close. Scope defines what is in and out. Schedule and cost are the time and money baselines. Quality is the standard the output must meet. Resources are people and things. Communications is who knows what, when. Risk is uncertainty. Procurement is work you buy. Stakeholders are the humans who can help or sink the thing.
You do not 'do risk' on Tuesdays and 'do stakeholders' on Wednesdays. A late vendor is procurement, risk, schedule, and a stakeholder conversation. The area names help you notice which concern you ignored. They are not a rota.
Agile language maps onto the same concerns with different artefacts. A product backlog is scope and priority. A sprint review is quality and stakeholder engagement. A retrospective is resource and process improvement. If a question uses Scrum words, answer the concern, not the brand.
Integration is the actual job
Most 'best next action' items are integration in disguise. Someone wants a change: you assess impact across areas, follow the agreed control, and update the plan. Someone wants a shortcut: you protect the baseline or the increment's definition of done. The exam rewards the PM who joins the dots, not the specialist who only sees their favourite area.
Watch for answers that optimise one area and wreck another. Crashing the schedule by exhausting the team is a resource and quality problem. Accepting a cheaper vendor without residual-risk ownership is procurement theatre. The better option usually names the trade-off and the person who must accept it.
Change control sits here. If work is baselined, you do not quietly absorb scope because the sponsor asked nicely in a corridor. If work is agile, you do not ignore a mid-sprint dump either — you take it to the product owner and the backlog. Same integration instinct, different mechanism.
How the exam uses this language
You may see area names, process names, or neither — just a situation. Use the map to ask: which concern is in trouble, and what process would a competent PM use? Then check the domain: is this really a people item dressed in process vocabulary?
Do not invent a requirement to memorise every tool and technique list. Know the purpose of a charter, a baseline, a RAID-style register, a stakeholder analysis, a definition of done, and a benefits measure. Know when earned value informs a conversation and when a burn-down does. Depth on purpose beats a graveyard of acronyms.
When you revise, take one scenario and walk it across areas: what happens to scope, time, cost, risk, and people if this decision lands? That habit is closer to the exam than highlighting a textbook until it glows.
Summary & next steps
Ten knowledge areas are a map of concerns; integration is how they stay one project. Use the map to find the ignored constraint. The exam still speaks this language while scoring domains and judgement.
Next: practice questions — how to read a scenario, and a few worked examples with the reasoning made visible.