CompTIA PK0-005 FAQ for exam format, topics, prep strategy, practice, and common candidate traps.
Project+ rewards disciplined project control more than generic management language. The strongest answer is usually the one that keeps authority, documentation, communication, and change governance intact.
CompTIA currently organizes PK0-005 into four domains:
That means the exam is not only about lifecycle steps. It also tests whether you can choose the right document, use a schedule or chart correctly, and apply enough IT and governance awareness to keep a technical project safe.
As of April 13, 2026, CompTIA lists Project+ PK0-005 as:
Not in the same way they are on infrastructure-heavy CompTIA exams. Project+ PBQs are more likely to make you interpret a schedule, classify risk or issue information, route a change properly, or choose the best action from a project-control view. Think practical coordination and governance, not command-line admin work.
You need working context, not deep engineering specialization. CompTIA’s current objectives include security, privacy, cloud models, infrastructure basics, and IT change control, so you should be comfortable reading technical project scenarios. But the exam is still grading project-management judgment first.
The highest-yield set is:
If those blur together, Project+ starts to feel more difficult than it is.
A risk may happen later. An issue has already happened and now needs action. Project+ frequently tests this distinction because it changes which artifact you update and which action is appropriate next.
Yes, but at the fit level. CompTIA wants you to match the delivery style to the work:
The exam is not asking you to join a methodology tribe.
The critical path controls the earliest finish date. Float is schedule flexibility on a task or path. If a task slips but still has float, the best answer is often “monitor and manage” instead of “rebaseline immediately.”
Implementing the change first because it came from an important stakeholder. Project+ strongly favors:
Work the domains in weighted order, then keep a short miss log with rules like:
real problem = issuescope shift = change requestphase confusion = wrong artifactThat kind of log is more useful than rereading generic PM definitions.