CompTIA Project+ (PK0-005) Study Guide: All Four Domains, Where the Points Are
Last updated October 24, 2026
Project+ is CompTIA's entry point into project management — a vendor-neutral credential aimed at people who manage smaller or less formal projects, often alongside another primary IT role, and don't yet need (or want) PMP's five-year experience requirement. The current version, PK0-005, is built around four domains and leans more on frameworks, terminology, and governance basics than on heavy calculation. Here's how it's weighted, what each domain actually covers, and where candidates lose points.
How the exam is weighted
CompTIA publishes an official domain breakdown for PK0-005 (Version 5.0), and it should directly drive how you allocate study time:
- 1.0 Project Management Concepts (33%) — the largest domain. Project characteristics, methodologies and frameworks (Agile vs. Waterfall, Scrum, Kanban, XP, SAFe, DevOps/DevSecOps), change control, risk and issue management, quality and performance management, communication management, schedule development, and meeting management.
- 2.0 Project Life Cycle Phases (30%) — the second-largest domain, following a project from discovery and concept preparation through initiation, planning, execution, and closing.
- 3.0 Tools and Documentation (19%) — the tools used throughout the life cycle, reading and interpreting quality and performance charts, and comparing productivity and collaboration tools.
- 4.0 Basics of IT and Governance (18%) — ESG factors, information security concepts, compliance and privacy, operational change control during an IT project, and foundational IT concepts a project manager needs to function on a technical team.
Unlike CISSP's nearly flat weighting, Project+ is top-loaded: the first two domains alone account for nearly two-thirds of the exam. That means methodology and life-cycle-phase questions carry the most weight, and the tools/governance domains, while still worth real points, are the lighter half of the exam.
What each domain actually tests
Project Management Concepts is where the exam tests whether you can tell methodologies apart by their defining trait rather than by name alone — Scrum's short iterative sprints versus Waterfall's sequential phases, Kanban's WIP-limited task board versus a Gantt chart, DevSecOps embedding security throughout the pipeline versus treating it as a final gate. This domain also covers the mechanics of running a project day to day: dependency types (finish-to-start, hard logic vs. soft logic), qualitative versus quantitative risk analysis, and the difference between an issue and a risk.
Project Life Cycle Phases tests whether you know which artifacts and activities belong to which phase — a work breakdown structure and detailed scope statement belong to planning, not initiation; removing system access and closing contracts belong to closing, not execution. The exam frequently presents an activity and asks which phase it belongs in, so phase-to-activity mapping is worth memorizing deliberately rather than picking up by feel.
Tools and Documentation covers reading quality and performance charts at a glance — a histogram shows frequency distribution, a Pareto chart prioritizes the vital few causes behind most effects, a run chart shows trends over time, a scatter diagram shows correlation between two variables — plus comparing communication and collaboration tools (chat vs. email vs. SMS vs. phone) by which one fits a given situation best.
Basics of IT and Governance is the domain most unlike a traditional PM exam: it expects you to know data-classification terms (PII vs. PHI vs. trade secrets), the cloud service models (IaaS, PaaS, SaaS) and what each one hands off to the vendor, and how operational change control works specifically in an IT context. This is the domain that most clearly signals Project+ was built for people managing projects inside IT organizations, not project managers in general.
How long should you study
Project+ doesn't carry a formal experience prerequisite the way PMP does, so study time depends mostly on background. Candidates already working in any IT role who have informally run or coordinated projects typically prepare in three to five weeks, focused on methodology vocabulary and phase-to-activity mapping. Candidates newer to both IT and project work often need six to eight weeks to build comfortable familiarity across all four domains, particularly the governance and cloud-service-model content in Domain 4.
Where candidates lose points
- Mixing up similar-sounding dependency and chart terms. Finish-to-start vs. start-to-finish, hard logic vs. soft logic, and histogram vs. Pareto chart vs. run chart are all easy to blur together under exam pressure — the exam relies on that.
- Treating Domain 4 as an afterthought. At 18%, it's the lightest domain, but PII/PHI classification and the IaaS/PaaS/SaaS distinction show up reliably and are easy points for anyone who reviews them deliberately.
- Misplacing an activity in the wrong life-cycle phase. Knowing what a work breakdown structure is isn't the same as knowing it belongs to planning, not initiation — the exam tests the placement as much as the definition.
- Picking the methodology name instead of the described behavior. Questions often describe a practice (pair programming and test-driven development, say) and ask which methodology it belongs to, rather than naming the methodology and asking for a definition — so memorized definitions alone aren't enough.
Why full-rationale practice questions help
Because so much of PK0-005 is about distinguishing closely related terms and correctly placing an activity or artifact, the value of practice is in seeing why the three wrong options are wrong, not just confirming the right one. Full rationale on every choice — not just the key — is what turns "I recognized the right answer" into "I understand why the other three don't fit," which is what actually holds up across unfamiliar scenario wording on exam day.
CompTIA Project+ (PK0-005 v5) - 600 Questions & Full Rationales — $9.99, instant PDF download with full rationale on every answer.
View the practice questions →If you're building toward a broader project or IT path
Project+ pairs naturally with a vendor-neutral networking foundation, or serves as a stepping stone toward PMP once you've built up real project experience: