How to pass PMI Certified Associate in Project Management (CAPM)
19 min read4 domains coveredFree practice, no sign-up
The PMI Certified Associate in Project Management (CAPM) is a knowledge-based entry point into the profession. Unlike the senior PMP, which tests seasoned judgement, the CAPM tests whether you know the vocabulary, the frameworks, and the core techniques of project management well enough to contribute on a team. Most questions are short and definitional or lightly applied: they ask what a term means, which technique fits a situation, what an artifact is for, or how a simple calculation comes out. If you have studied the standard concepts and can tell closely related ideas apart, the exam is very passable.
The 2023 outline is deliberately broad and integrated. It spans four domains: a large foundations domain covering life cycles, terminology, roles, and artifacts; a predictive, plan-based domain covering scope, schedule, cost, and earned value; an agile domain covering the Agile Manifesto, Scrum, and adaptive planning; and a business analysis domain covering needs assessment, requirements, traceability, and solution evaluation. This spread means you cannot pass on predictive knowledge alone; roughly a fifth of the exam is agile and over a quarter is business analysis, so all four areas need real study.
The domains are weighted unevenly, and study effort should follow the weight: Fundamentals is the largest, Business Analysis is the second largest, then Agile, then the Predictive methodologies domain. A handful of topics require arithmetic rather than recall - the critical path, total float, and the earned value variances - and these reward practice because the concepts are precise and the wrong answers are built from predictable mistakes. The highest-value preparation is practising on definitional and lightly applied questions with worked explanations, so you learn the exact distinctions the exam turns on: validation versus verification, a program versus a portfolio, a threat response versus an opportunity response, a business requirement versus a stakeholder requirement.
CAPM rewards precise knowledge of project management terms, frameworks, and techniques across predictive, agile, and business analysis approaches, not the seasoned judgement the PMP demands.
Difficulty
Intermediate
Best for
Students, recent graduates, and early-career professionals entering project management, plus team members who want a recognised credential proving they know the fundamentals across predictive and agile work.
Prerequisites
Entry-level: PMI requires a secondary diploma plus a modest amount of formal project management education, but no prior project management work experience.
150 (135 scored)
Questions
180 min
Time allowed
$300
Exam cost (USD)
286
Practice questions
How this exam thinks
CAPM rewards precise knowledge over judgement, and that single fact decides how to read most questions. Where the PMP hides one best action among several defensible ones, the CAPM usually has one answer that is simply correct by definition and three that are wrong because they confuse it with a neighbouring concept. Your job is to know each concept sharply enough that the near-miss distractor does not fool you: to know that the critical path is the longest path and not the path with the longest single activity, that validation is confirming you built the right thing while verification is confirming you built it right, that a scrum master serves the team rather than commands it.
Because the distractors are built from common confusions, the exam is really a test of clean distinctions. Study in contrasting pairs rather than isolated facts: project versus operations, program versus portfolio, organisational process assets versus enterprise environmental factors, iterative versus incremental, business versus stakeholder versus solution requirements. When a question offers two options that both sound plausible, the difference between them is almost always the exact distinction the item is testing, so name that distinction before you choose.
A few questions are calculations, and these are the most predictable marks on the exam once you drill them. The critical path, total float, and the earned value variances follow fixed rules, and the wrong answers are made by reversing a sign or misreading a formula, so knowing the method cold both earns the mark and reveals the trap. Finally, treat framework currency as a rule: the 2023 outline integrates predictive, agile, and business analysis, and it uses current definitions from the Agile Manifesto and the Scrum Guide, so ignore retired process-group trivia and answer from the current standards.
What each domain tests and how to study it
The CAPM blueprint is split across 4 domains. Weights are the official share of the exam; see the official exam guide for the authoritative breakdown.
What you must be able to do. Recognise the core vocabulary, life cycles, roles, and planning artifacts of project management, and tell closely related foundational concepts apart: predictive versus adaptive, project versus operations, program versus portfolio, and what each register or baseline is for.
In one sentenceThe shared language of the profession: project life cycles and process groups, core terminology, the responsibilities of the manager, sponsor, team, and stakeholders, and the purpose of foundational artifacts such as the charter, stakeholder register, risk register, and assumption log.
Recall check: answer these from memory first
What distinguishes an iterative life cycle from an incremental one, and which suits evolving requirements?
What does the project charter authorise, and whose approval gives the project manager authority to apply resources?
What is the difference between organisational process assets and enterprise environmental factors?
What it tests. Whether you know the foundations every project professional shares: the difference between predictive, iterative, incremental, adaptive, and hybrid life cycles, and how projects, programs, portfolios, and operations relate. It covers core terminology such as deliverable, milestone, baseline, constraint, and assumption, the roles and responsibilities of the project manager, sponsor, team, and stakeholders, servant leadership and emotional intelligence fundamentals, and the purpose of the charter, stakeholder register, risk register, and assumption log.
How to study it. This is the largest domain, so give it the most time, and study it as a set of clean contrasts. Build a table of the life cycle types and what distinguishes each, and another for project versus program versus portfolio versus operations. Learn what each foundational artifact captures and when it is created, especially that the charter authorises the project and grants the manager authority once the sponsor approves it. Fix the difference between organisational process assets (internal, reusable) and enterprise environmental factors (conditions the project operates within), because that pairing is a frequent trap.
Easy to confuse
Program versus portfolio. A program is a group of related projects managed together to gain benefits not available from managing them separately, so the projects share an objective. A portfolio is a collection of projects, programs, and operations grouped to meet strategic goals, and its components need not be related. The trap is treating any large collection of work as a program when unrelated grouping makes it a portfolio.
Organisational process assets versus enterprise environmental factors. Organisational process assets are the internal templates, processes, and historical information the organisation provides for reuse. Enterprise environmental factors are conditions, internal or external, that the project operates within but does not control, such as regulations, market conditions, or the organisation's culture. The distractor swaps a reusable asset for a governing condition.
Iterative versus incremental development. Iterative development repeats work to refine a single product through successive versions until it is right. Incremental development delivers the product in finished pieces that each add usable functionality. The classic trap describes delivering functional slices and calls it iterative, or describes refining a whole through rework and calls it incremental.
Worked example from the CAPM bank
lock_openFree sampleProject Management Fundamentals and Core Conceptseasy
The Harbourline mobile banking programme has stable, well-understood requirements, a fixed regulatory deadline, and a client who wants the full scope defined and signed off before any build starts. The sponsor asks which development approach best fits these conditions. Which approach should the project manager recommend?
AA predictive approach, planning scope, schedule, and cost in detail before execution beginscheck_circle Correct
BAn adaptive approach, so the team can reprioritise the backlog every iteration as feedback arrives
CAn incremental approach, so a usable subset of features is released at the end of each short cycle
DA hybrid approach, combining predictive planning with adaptive delivery for the same requirements
A predictive life cycle suits work whose scope and requirements are well understood and fixed before execution begins. A predictive approach front-loads detailed planning of scope, schedule, and cost because the requirements are known and stable, which lets the team commit to a plan and a fixed deadline with confidence.
Why A is correct: Predictive life cycles fit stable, clearly defined requirements planned in full before work starts, which matches the fixed scope, signed-off requirements, and fixed deadline described here.
Why B is wrong: Adaptive approaches suit volatile requirements and frequent change, but this programme has stable, well-understood scope defined up front, so the flexibility adds overhead without benefit.
Why C is wrong: Incremental delivery is tempting because of the fixed deadline, but it is chosen to get working functionality into users' hands early, not because requirements are fully known and fixed at the outset.
Why D is wrong: Hybrid is useful when parts of the work are uncertain and parts are stable, but nothing here is described as uncertain, so blending approaches introduces complexity the situation does not call for.
What you must be able to do. Apply the plan-based techniques of scope, schedule, cost, quality, risk, and procurement, and compute and interpret the schedule-driving and value measures: the critical path and total float, the earned value variances, and how contract types allocate cost risk.
In one sentenceThe mechanics of plan-driven delivery: collecting requirements and building a work breakdown structure, finding the critical path and total float, establishing cost and quality baselines, planning risk responses and procurement, and reading earned value to judge schedule and cost performance.
Recall check: answer these from memory first
How do you find the critical path in a network, and how much float do its activities have?
Write the formulas for schedule variance and cost variance, and say what a negative value of each means.
Under a firm fixed-price contract, who carries the risk of a cost overrun, and how does that differ under cost-reimbursable?
What it tests. Whether you can apply the plan-based project techniques correctly. It covers scope management and decomposing work into a work breakdown structure whose lowest level is the work package, the critical path method for finding the longest path and the total float on non-critical activities, cost and quality baselines, risk identification and the response strategies for threats and opportunities, the main procurement contract types and how they allocate cost risk, and earned value basics such as schedule variance and cost variance to judge whether a project is ahead or behind and over or under budget.
How to study it. Split this domain into concepts and calculations and drill the calculations until they are automatic. For the critical path, practise building a small network, finding the longest path, and computing total float, holding firmly to the rule that critical-path activities have zero float. For earned value, memorise that schedule variance is earned value minus planned value and cost variance is earned value minus actual cost, and that a negative result means behind or over. Learn the scope baseline components, the threat and opportunity response strategies as two matched lists, and how fixed-price, cost-reimbursable, and time-and-materials contracts shift cost risk between buyer and seller.
Easy to confuse
Critical path versus the longest-duration activity. The critical path is the longest continuous chain of dependent activities from start to finish, and it sets the shortest possible project duration. It is not the single activity with the longest duration, nor merely the path with the most activities. The trap points you at one long activity or a busy-looking path instead of the longest total path, whose activities have zero float.
Cost variance versus schedule variance. Cost variance is earned value minus actual cost and tells you whether you are over or under budget; schedule variance is earned value minus planned value and tells you whether you are ahead of or behind schedule. Both are negative when the project is in trouble, but they measure different things, and the distractor reports a budget problem using the schedule formula or vice versa.
Fixed-price versus cost-reimbursable contracts. A firm fixed-price contract places the risk of a cost overrun on the seller, who must deliver for the agreed price. A cost-reimbursable contract places that risk on the buyer, who repays the seller's actual costs plus a fee. The trap reverses who absorbs an overrun, which changes the correct procurement choice for a given risk appetite.
A small project network has five activities. Activity A (3 days) and Activity B (6 days) both start the project. Activity C (8 days) follows A. Activity D (4 days) follows B. Activity E (5 days) starts only after both C and D finish, and E ends the project. Which path is the project's critical path?
AA to C to E, with a total duration of 16 dayscheck_circle Correct
BB to D to E, with a total duration of 15 days
CA to C to E, with a total duration of 11 days
DB to D to E, with a total duration of 18 days
The critical path is the longest continuous path through the network, which determines the earliest possible project finish. Adding activity durations along each complete path gives A to C to E at 16 days and B to D to E at 15 days. The longest of these, 16 days, is the critical path because any delay to its activities delays the whole project.
Why A is correct: The critical path is the longest continuous path through the network. A to C to E sums to 3 plus 8 plus 5, which is 16 days, longer than the only other path B to D to E at 15 days, so it sets the earliest project finish and its activities have zero total float.
Why B is wrong: B to D to E is the near-critical path at 15 days and carries only 1 day of total float. It is tempting because it starts with the longest single activity, B at 6 days, but a longer path exists, so it is not critical.
Why C is wrong: This correctly names the longest path but miscalculates its length, most likely by dropping activity E from the sum. The path A to C to E actually totals 16 days, not 11, so the duration stated here is wrong.
Why D is wrong: This selects the near-critical path and also overstates its length, probably by adding an activity that is not on it. B to D to E totals 15 days, and in any case it is not the longest path, so it is not the critical path.
What you must be able to do. Explain the values and principles of the Agile Manifesto and apply the Scrum framework and adaptive planning: the roles, timeboxed events, and artifacts, and techniques such as user stories, story points, velocity, and information radiators.
In one sentenceThe adaptive way of working: the four values and twelve principles of the Agile Manifesto, the Scrum roles, events, and artifacts, and adaptive planning and tracking with user stories, story points, velocity, and burndown charts.
Recall check: answer these from memory first
Who is accountable for ordering the product backlog, and what is the scrum master's relationship to the team?
What are the four values of the Agile Manifesto, stated as this-over-that pairs?
What does velocity let a team forecast, and why is it not a measure of individual productivity?
What it tests. Whether you understand adaptive delivery well enough to work in it. It covers the values and principles of the Agile Manifesto and when an adaptive approach suits high-uncertainty work, the Scrum framework of a product owner who orders the product backlog, a scrum master who serves the team and removes impediments, and developers who build the increment, the timeboxed events of sprint planning, daily scrum, sprint review, and retrospective, and adaptive planning techniques such as writing user stories with acceptance criteria, estimating in story points, forecasting with velocity, and reading burndown charts and Kanban boards.
How to study it. Study Scrum from its own source of truth and hold to current definitions. Learn the three accountabilities, the events and their timeboxes, and the artifacts with their commitments, being careful that the scrum master serves rather than assigns work and that the product owner alone orders the backlog. Memorise the four Agile Manifesto values as this-over-that pairs and the mindset of delivering value early through short feedback loops. For adaptive planning, know that story points are relative estimates rather than hours, that velocity forecasts capacity rather than measures productivity, and that a burndown chart above the ideal line means work is behind.
Easy to confuse
Scrum master as servant leader versus as a boss. The scrum master serves the team by coaching, facilitating events, and removing impediments, and has no authority to assign work or direct individuals. The trap frames the scrum master as a project manager who allocates tasks and holds people to account, which is the opposite of the servant-leadership role the framework defines.
Story points versus hours. Story points are a relative measure of size, effort, and complexity, deliberately abstracted from time so estimates stay stable as the team's pace changes. Hours are an absolute time estimate. The distractor treats a story point as a fixed number of hours, which defeats the purpose of relative estimation and misreads velocity.
Product backlog versus sprint backlog. The product backlog is the single ordered list of everything that might be needed in the product, owned by the product owner. The sprint backlog is the subset the developers select for the current sprint plus their plan to deliver it, owned by the developers. The trap swaps ownership or scope, for example letting the product owner manage the sprint backlog.
The Meridian mobile-banking team has a signed 40-page requirements document, but during the first two-week iteration the client watches the working login flow and asks for three material changes. The team lead argues that the contract fixes the scope and the changes should wait for a formal change request. Which position best reflects the values of the Agile Manifesto?
ADefer the changes to a later release, because the signed requirements document is the team's contract and must govern the current iteration.
BWelcome the client's changes now, because responding to change is valued over following a fixed plan when it delivers a better product.check_circle Correct
CReject the changes outright, because customer collaboration tends to matter most at the start of the project when the scope is first agreed.
DAccept the changes only after the client raises a formal written change request through the document-control process.
The Agile Manifesto values responding to change over following a plan when adaptation yields a better outcome for the customer. Agile treats requirements as emergent; feedback from a working increment is a signal to adapt, and the Manifesto explicitly ranks responding to change above following a fixed plan, which is why welcoming the change is the best position.
Why A is wrong: This treats comprehensive documentation and the plan as fixed authority, which inverts the Manifesto value that prioritises responding to change, so it is wrong.
Why B is correct: The Manifesto value 'responding to change over following a plan' supports adapting to the emerging requirement rather than deferring to the original scope document, so this is correct.
Why C is wrong: It is tempting because early scoping does matter, but the Manifesto values ongoing customer collaboration throughout delivery, not just at kickoff, so this is wrong.
Why D is wrong: A heavyweight change-control gate favours process and documentation over individuals and interactions and responding to change, so although it feels disciplined it conflicts with the values here.
What you must be able to do. Apply business analysis within a project: conduct needs assessment and stakeholder analysis, elicit and classify requirements, maintain traceability, and validate and verify that the solution meets acceptance criteria and delivers the business need.
In one sentenceConnecting the solution to the need: assessing the business need and stakeholders, eliciting and categorising business, stakeholder, solution, and transition requirements, tracing them through a traceability matrix, and validating and verifying that the delivered solution meets its acceptance criteria and business case.
Recall check: answer these from memory first
Classify these into requirement types: a goal to cut call-handling time, a user's need to export a report, a training need at go-live.
What is the difference between validation and verification, and which one asks whether you built the right thing?
What does a requirements traceability matrix link, and how does it support impact analysis when a change is requested?
What it tests. Whether you can perform the business analysis work that keeps a project delivering value. It covers needs assessment to define the business problem and justify a recommended solution, stakeholder analysis, elicitation techniques such as interviews, workshops, document analysis, and observation, and categorising requirements as business, stakeholder, solution, or transition. It covers prioritising requirements against value and constraints, maintaining a requirements traceability matrix for impact analysis, and evaluating a solution against its acceptance criteria while distinguishing validation from verification.
How to study it. Anchor this domain on two things: the requirement-type taxonomy and the validation-versus-verification distinction, both of which the exam tests repeatedly. Learn to classify a stated need as a business, stakeholder, solution (functional or non-functional), or transition requirement, using worked examples until the boundaries are clear. Fix that validation confirms you built the right thing against the need while verification confirms you built it right against the specification. Study what a traceability matrix links and why it powers impact analysis, and know the common elicitation techniques and when each fits.
Easy to confuse
Validation versus verification. Validation asks whether the solution meets the actual business need - did we build the right thing - and is judged against acceptance criteria and the business case. Verification asks whether the solution was built correctly against its specification - did we build it right. The trap swaps the two, offering a specification-conformance answer where the question is about meeting the need, or the reverse.
Business requirement versus stakeholder requirement versus solution requirement. A business requirement is the high-level goal or outcome the organisation seeks; a stakeholder requirement is what a specific group needs from the solution to do their work; a solution requirement is a capability or quality the solution must have. The distractor labels a specific user's need as a business goal, or a system capability as a stakeholder need, blurring the level being tested.
Forward versus backward traceability. Forward traceability links a requirement onward to the design, build, and test that satisfy it, confirming it was delivered. Backward traceability links a requirement back to the business objective that justifies it, confirming nothing extra was built. The trap describes tracing to a business objective and calls it forward, or tracing to a test and calls it backward.
At the Meridian Loyalty project, a sponsor tells the business analyst that the organisation should build a mobile rewards app because a competitor just launched one. Before any solution is chosen, what should the business analyst do first as part of the needs assessment?
ADraft the solution requirements for the mobile app so developers can begin estimating the build effort.
BIdentify and document the underlying business problem or opportunity the organisation is trying to address.check_circle Correct
CSchedule the competitor's app for a feature-by-feature teardown so the new app can match it exactly.
DEstimate the project budget and timeline so the sponsor can approve funding at the next steering meeting.
A needs assessment starts by defining the underlying business need, the problem or opportunity, before any solution is selected. The needs assessment exists to establish why change is warranted. Defining the business problem or opportunity first ensures every later decision, including whether an app is even the right solution, traces back to a real organisational gap rather than to a sponsor's assumption.
Why A is wrong: Writing solution requirements assumes the mobile app is the right answer, which skips the needs assessment and commits to a solution that has not yet been justified by a defined business need.
Why B is correct: A needs assessment begins by defining the business need, the actual problem or opportunity, before any solution is considered, so the response is grounded in a real gap rather than a copied competitor feature.
Why C is wrong: Copying a competitor feature by feature is tempting when a sponsor names a rival, but it substitutes imitation for analysis and never establishes whether the organisation shares the same business need.
Why D is wrong: Budget and timeline estimates matter later in the business case, but producing them before the business need is defined prices a solution that has not been shown to address a genuine problem.
A study plan that works
Map the four domains and set a proportional schedule
Week 1
Start from the four domains and their weights, and plan your time in proportion: the most for Fundamentals, the next most for Business Analysis, then Agile, then the Predictive methodologies domain. Note that the outline is integrated, so budget real time for agile and business analysis rather than treating the exam as a predictive test with extras.
Build the Fundamentals through contrasting pairs
Weeks 2-3
Study life cycles, core terminology, roles, and artifacts as clean contrasts: predictive versus adaptive, project versus operations, program versus portfolio, organisational process assets versus enterprise environmental factors. Learn what each artifact captures and that the charter authorises the project once the sponsor approves it.
Drill the predictive calculations until automatic
Weeks 3-4
Work the critical path method and total float on small networks, holding the zero-float rule, and practise earned value until schedule variance and cost variance and their signs are automatic. Add the scope baseline components, the threat and opportunity response strategies, and how contract types allocate cost risk.
Learn Agile from the current standards
Weeks 4-5
Study the Agile Manifesto values and principles and the Scrum framework from its own definitions: the three accountabilities, the timeboxed events, and the artifacts and their commitments. Fix that the scrum master serves rather than directs, that story points are relative, and that velocity forecasts capacity.
Cover Business Analysis and its key distinctions
Weeks 5-6
Study needs assessment, stakeholder analysis, elicitation techniques, and the requirement-type taxonomy, and drill the validation-versus-verification distinction until it is instant. Learn what a traceability matrix links and how forward and backward traceability differ and support impact analysis.
Practise mixed question sets with worked explanations
Weeks 7-8
Sit timed sets that mix all four domains, including the calculation items. For every question you miss, read the worked explanation and the per-option rationale until you can name the exact distinction the item tested, then log the confusion so you stop repeating it.
Consolidate weak areas and rehearse exam-day pacing
Week 9
Review your logged confusions, redo the domains where your scores lag, and take at least one full-length timed run to confirm your pace across 150 questions in 180 minutes. Aim to finish with time to revisit flagged items rather than racing the clock.
Know when you're ready
You are ready when you can answer unseen definitional and lightly applied questions reliably, not when you have simply read the material once. The signal to trust is a measured score: sit full-length, mixed-domain practice exams under real time pressure and look for a consistent, comfortable margin above a typical pass across several sittings, not a single good run. Because the outline is integrated, check that your scores hold across all four domains rather than being carried by the predictive material most people find familiar.
Just as important is whether you can name the distinction each question turns on. If you are still guessing between two similar-sounding options, you have not yet fixed the concept the item tests. When you can predict the correct answer, explain in a sentence why each distractor is the wrong neighbour - a program mistaken for a portfolio, verification offered where validation was asked, a threat response applied to an opportunity - and when the critical path and earned value calculations come out right every time, the exam holds few surprises.
Ready to put this into practice?
Free CAPM questions with worked explanations. No sign-up.
Read each question for the exact concept it tests. On the CAPM the wrong answers are usually near-miss confusions, so name the distinction before you choose.
For any calculation, apply the method rather than eyeballing it: find the longest path for the critical path, and use earned value minus planned value or actual cost for the variances.
Hold the zero-float rule. Activities on the critical path have zero total float, and the critical path is the longest path, not the longest single activity.
Answer agile questions from current standards. The scrum master serves the team, the product owner orders the product backlog, and story points are relative, not hours.
Keep validation and verification straight: validation is building the right thing against the need, verification is building it right against the specification.
Match the risk response to the risk: threats take avoid, transfer, mitigate, or accept; opportunities take exploit, share, enhance, or accept.
Watch for absolute wording. Options that say always, never, all, or only are often distractors, because real project management answers are rarely absolute.
Flag and move on. With 150 questions in 180 minutes you have time, but protect your pace and return to hard items rather than stalling on one.
Frequently asked questions
How is the CAPM different from the PMP?
The CAPM is a knowledge-based, entry-level credential that tests whether you know project management terminology, frameworks, and techniques. The PMP is a senior, judgement-based exam that tests whether an experienced manager can choose the best action in a messy scenario. The CAPM needs no project management work experience, while the PMP requires documented project leadership experience.
Do I need work experience to sit the CAPM?
No project management work experience is required. PMI asks for a secondary education level qualification and a modest amount of formal project management education. That makes the CAPM well suited to students, recent graduates, and professionals moving into project work who want a recognised credential before they have led projects.
Is the CAPM only about predictive (waterfall) project management?
No. The 2023 outline is integrated across four domains, and only one of them is the predictive, plan-based methodologies domain. Roughly a fifth of the exam is agile and over a quarter is business analysis, alongside the large fundamentals domain, so you must study adaptive delivery and business analysis as seriously as predictive techniques.
How are the four domains weighted?
Fundamentals carries the largest share, Business Analysis is second, then the Agile domain, then the Predictive, plan-based methodologies domain. The exam page shows the current figures, which the exam renders directly, and study time should follow the weights: the most for Fundamentals, a strong block for Business Analysis, and focused coverage of the other two.
Are there calculations on the CAPM?
Yes, a small but predictable set. You should be able to find the critical path and total float in a simple network and compute the earned value variances, schedule variance and cost variance, and interpret their signs. These are among the most reliable marks on the exam once you drill them, because the method is fixed and the wrong answers come from predictable mistakes.
What is the most common way candidates lose marks?
Confusing two closely related concepts. The distractors are built from common confusions - a program mistaken for a portfolio, validation swapped with verification, a threat response applied to an opportunity, a solution requirement labelled a business requirement - so a shaky grasp of the exact distinction is what costs marks. Studying in contrasting pairs is the direct fix.
How long should I study for the CAPM?
Most candidates prepare over roughly two to three months of steady part-time study, following the domain weights. Allow extra time for the areas you know least, which for many is agile or business analysis, and reserve the final weeks for full-length, mixed-domain practice under timed conditions to confirm both your knowledge and your pace.
Are these practice questions reproductions of real exam items?
No. Every question is original, authored from the public examination content outline, with a worked explanation and a rationale on each option so you learn why the correct answer is right and each distractor is the wrong neighbour. They are practice materials and are not affiliated with or endorsed by PMI.
Related certifications
Other Project-management certifications with a study guide.
Examworthy is not affiliated with or endorsed by PMI. This guide is original study material based on the public exam blueprint. We never reproduce live exam items. CAPM and related marks belong to their respective owners.
