CompTIA PK0-005 exam guide covering scope, scheduling, risk, resources, and project delivery decisions.
This guide targets the current CompTIA Project+ PK0-005 exam. As of April 13, 2026, CompTIA’s public Project+ page still identified PK0-005 as V5 and listed a November 8, 2022 launch date, maximum of 90 questions, multiple-choice and performance-based questions, 90 minutes, a 710 passing score on the 100-900 scale, languages English, Japanese, and Thai, and recommended experience of 6-12 months managing projects in a tech environment. The official CompTIA page also exposes the live four-domain objective map used to organize this guide.
Baseline: The approved version of scope, schedule, or cost used for comparison and control.
Issue log: The record used for problems that have already happened and now need action.
Critical path: The longest path through the schedule, which controls the earliest finish date.
| Item | Current CompTIA signal |
|---|---|
| Version | V5 |
| Exam code | PK0-005 |
| Launch date | November 8, 2022 |
| Question count | Maximum of 90 |
| Exam style | Multiple-choice and performance-based questions |
| Duration | 90 minutes |
| Passing score | 710 on a 100-900 scale |
| Languages | English, Japanese, and Thai |
| Recommended experience | 6-12 months in a tech project environment |
| Guide model | 4 official domain chapters -> 11 objective-group lessons |
Project+ is not a pure vocabulary exam and it is not a deep enterprise-PMO exam. CompTIA is testing whether you can keep a small or medium technical project governed when time pressure, vendor friction, schedule slips, and stakeholder requests start colliding. Strong candidates consistently identify:
That is why the heavier domains are Project Management Concepts and Project Life Cycle Phases. If those are weak, tools questions and IT-governance questions usually feel harder than they really are.
flowchart LR
S["Study Plan"] --> D["4 official domain chapters"]
D --> L["11 objective-group lessons"]
L --> C["Cheat Sheet and Glossary"]
C --> M["Mixed scenario review"]
M --> R["Resources and final scope check"]
Use the guide in this order:
| Domain | Weight | Lesson count | Focus |
|---|---|---|---|
| 1. Project Management Concepts | 33% | 4 | methodologies, change control, risk, issues, scheduling, quality, communication, team performance, and procurement |
| 2. Project Life Cycle Phases | 30% | 3 | discovery, initiation, planning, execution, phase gates, closing, and handoff discipline |
| 3. Tools and Documentation | 19% | 2 | charts, logs, dashboards, collaboration tools, quality visuals, and decision support |
| 4. Basics of IT and Governance | 18% | 2 | ESG, security, compliance, privacy, cloud and infrastructure basics, and controlled IT change |
| Starting point | Protect these chapters first | Why |
|---|---|---|
| project coordinator or business analyst | 1. Project Management Concepts, 2. Project Life Cycle Phases, then 3. Tools and Documentation | you probably know the meeting and status language already but still need cleaner control flow |
| help desk, sysadmin, or support lead | 2. Project Life Cycle Phases, 4. Basics of IT and Governance, then 1. Project Management Concepts | technical readers often understand systems faster than charters, registers, and approval paths |
| newer PM learner starting from scratch | Study Plan and then the four chapters in order | the guide is easiest to absorb if you build phase logic before tool and governance details |
The wrong answer often sounds faster, more helpful, or more decisive than the right answer. Watch for these patterns:
Use the appendix pages as support layers rather than substitutes for the domain lessons: