CompTIA Project+ (PK0-005) Study Guide: Format, Domains, Cost, and How to Pass

CompTIA Project+ (exam code PK0-005) is an entry-level project management certification built for IT professionals who run projects as part of their job rather than as their whole career. The exam gives you 90 minutes to answer a maximum of 90 questions — multiple-choice plus performance-based questions (PBQs) — and you pass with a scaled score of 710 on a 100–900 scale. The voucher costs $399 after CompTIA’s May 2026 price change, and you can sit the exam at a Pearson VUE test center or online through OnVUE. This guide walks through who the certification is for, exactly what’s on it, how each domain breaks down, and a four-week plan to get you to a passing score.

What Project+ is and who it’s for

Project+ occupies a specific niche in the certification landscape. The Project Management Professional (PMP) demands years of documented project-leadership experience before you can even register. Project+ has no prerequisites at all. It’s aimed at the sysadmin who gets handed a server migration, the help desk lead coordinating a rollout, the business analyst who keeps ending up as the de facto project coordinator — people who need credible project management vocabulary and method without committing to project management as a full-time profession.

The PK0-005 version of the exam launched in November 2022, and it modernized the objectives considerably: Agile and hybrid delivery get real coverage alongside traditional Waterfall, and a full domain is devoted to IT fundamentals and governance topics like cloud computing, enterprise software categories, data security, and ESG (environmental, social, and governance) considerations. That last domain is what makes Project+ distinctly a CompTIA certification — it assumes your projects live in IT environments and tests whether you understand the technology you’re coordinating.

A useful side note for planning your certification path: Project+ does not expire. Unlike Security+ or Network+, it sits outside CompTIA’s continuing education program, so there are no renewal fees or CE units to track. You pass once and hold it for good.

Who should probably not start here: if you already lead large programs full-time and your employer recognizes the PMP or PRINCE2, those credentials carry more weight in dedicated project management roles. Project+ is the right call when you want a respected baseline quickly, when you lack the logged hours the PMP requires, or when your work blends technical execution with coordination duties.

Exam format at a glance

Detail	PK0-005
Question count	Maximum of 90
Question types	Multiple-choice and performance-based questions (PBQs)
Time limit	90 minutes
Passing score	710 on a scale of 100–900
Voucher price	$399 (raised in the May 2026 CompTIA price change)
Delivery	Pearson VUE test center or online via OnVUE
Launched	November 2022
Prerequisites	None

Two format notes worth internalizing before test day. First, the math on timing: up to 90 questions in 90 minutes is a minute per question on average, but PBQs — interactive items where you might order life cycle phases, match chart types to purposes, or sort risks into a matrix — take several minutes each. Budget for that by moving briskly through the multiple-choice items you know cold. Second, the scoring is scaled, not a raw percentage. Don’t try to compute “how many can I miss” — aim to walk in consistently scoring well on full-length practice runs and let the scale take care of itself.

The four domains

PK0-005 draws its questions from four domains with fixed weightings:

Domain	Weight
Project Management Concepts	33%
Project Life Cycle Phases	30%
Tools and Documentation	19%
Basics of IT and Governance	18%

The first two domains together are almost two-thirds of the exam, so that’s where the bulk of your study time belongs. But the last two are where IT professionals often lose easy points — governance and documentation questions feel unfamiliar precisely because they’re the least glamorous part of the job. Here’s what each domain actually covers.

Domain 1: Project Management Concepts (33%)

This is the vocabulary-and-mechanics domain — the largest on the exam. It tests whether you know what a project is (temporary, unique, producing a defined deliverable, as opposed to ongoing operations), who does what on one, and how the core management disciplines work: schedule, cost, resources, quality, risk, communication, and procurement.

Expect heavy coverage of roles and responsibilities. You need to distinguish the project manager from the sponsor, the product owner from the Scrum master, the stakeholder from the team member — and scenario questions will describe someone’s behavior and ask who they are. Communication methods get similar treatment: when a status meeting beats an email, how communication needs change with distributed teams, and how often different audiences need updates.

Risk management is a pillar of this domain, and it rewards process knowledge. You should be able to walk the sequence from identifying risks, through analysis, to planning responses — and know the artifacts at each step. Start with the risk register, the living document where every identified risk gets an owner, a score, and a response, then study qualitative risk analysis to understand how probability-impact scoring turns a raw list of worries into a ranked priority order. Know the classic response strategies for threats (avoid, transfer, mitigate, accept) and their mirror images for opportunities (exploit, share, enhance, accept).

Procurement rounds out the domain: solicitation documents like the RFI (request for information), RFP (request for proposal), and RFQ (request for quote), contract types, and how to score competing bids. Vendor evaluation criteria covers the weighted-comparison approach the exam favors — judging vendors on technical capability, relevant experience, certifications, and cost rather than price alone.

Finally, this domain carries the Agile material: Scrum events and artifacts, Kanban boards and work-in-progress limits, and — critically — when an adaptive approach fits better than a predictive one. Expect scenarios that describe a project’s characteristics (stable requirements vs. evolving ones, regulatory constraints, customer availability) and ask which delivery approach suits it.

Domain 2: Project Life Cycle Phases (30%)

Where Domain 1 tests concepts in isolation, Domain 2 tests sequence: what happens in each phase of a project, in what order, producing which artifacts. CompTIA’s framing runs from discovery and concept preparation through initiation, planning, execution, and closing, and many questions boil down to “given this activity, which phase are you in?” or “what should happen next?”

The front end of the life cycle is justification and setup. Before a project exists, someone has to prove it’s worth doing — that’s the project business case, which lays out the problem, options, costs, benefits, and recommendation that a sponsor approves before anything is chartered. Once the project is real, one of the earliest and most consequential activities is stakeholder identification — figuring out every person and group affected by the work, because a stakeholder discovered late is a change request waiting to happen. What you learn about them gets recorded in the stakeholder register, tracking each stakeholder’s interest, influence, and engagement needs.

Planning is the deepest part of the domain: building a work breakdown structure, developing the schedule, creating a backlog on adaptive projects, planning quality assurance, and assessing risk. Requirements prioritization lives here too — the Kano model is the framework you need for classifying features as baseline expectations, performance attributes, or delighters, and it’s a reliable exam topic.

Execution and closing supply the rest. Know the testing progression on IT projects — unit, integration, system, and finally user acceptance testing, where actual business users validate the deliverable against real-world needs before go-live. For closing, know the checklist: final deliverable acceptance, contract closure, releasing resources, archiving documentation, and capturing lessons learned.

Domain 3: Tools and Documentation (19%)

This domain tests whether you can pick the right instrument for the job. It splits into two halves: charts and analysis tools, and project documents and software.

The chart material is very learnable and very testable. You should recognize on sight — and know the use case for — the Gantt chart (schedule bars over time), the burndown chart (remaining work in a sprint or release), the Pareto chart (sorted bars isolating the vital few causes), histograms, run charts, scatter diagrams, fishbone/Ishikawa diagrams for root-cause analysis, and the RACI matrix (responsible, accountable, consulted, informed) for clarifying who does what. PBQs love this material: matching chart types to described scenarios is a natural drag-and-drop item.

The documentation half covers the paper trail of a project: meeting agendas and minutes, action item logs, status reports, dashboards, issue logs, and change logs. Expect questions about which document serves which audience — an executive dashboard versus a team-level task board — and about the discipline of keeping records current. The domain also touches project management software categories (scheduling tools, ticketing systems, collaboration platforms, version control) at the level of knowing what each is for, not how to operate any specific product.

Domain 4: Basics of IT and Governance (18%)

The smallest domain, but the one that distinguishes Project+ from generic project management certs — and the one where non-infrastructure people need the most deliberate study. It expects a working, project-manager-level understanding of the technology environments where IT projects live.

Cloud and infrastructure concepts anchor it. You need the deployment models cold: public, private, community, and especially the difference between hybrid cloud and multicloud, plus the service models (SaaS, PaaS, IaaS) and why scalability drives cloud adoption on projects. Closely related is virtualization versus containers — the exam wants you to know which technology fits server consolidation versus portable, lightweight workloads. Resilience concepts appear too: eliminating single points of failure through load balancing and redundancy is a recurring scenario. And you need enough networking to hold your own in a kickoff meeting — LAN vs WAN, firewalls, and latency covers exactly that layer.

Enterprise software categories are their own objective. Scenarios describe a business need and ask which system class meets it: CRM vs ERP — plus HRIS, supply chain, and financial systems — for operational platforms, and the broader enterprise software landscape of content management, document management, business intelligence, and ticketing systems. Integration questions follow naturally: middleware and APIs explain how a project connects a legacy system to a new application without replacing either.

Governance and security close the domain from the manager’s chair, not the engineer’s. Physical, operational, and data security covers the controls a PM must account for in planning — facility access, background checks, data classification, and handling requirements. And the PK0-005 objectives added ESG in project management: environmental, social, and governance factors as vendor-selection and RFP criteria, and the obligation to report ESG impacts honestly.

How the PK0-005 exam tests this

Across all four domains, PK0-005 questions follow a few recognizable patterns. Learning to spot the pattern is worth almost as much as knowing the content:

• The next-step scenario. A vignette ends mid-process — a risk was just identified, UAT just failed, a stakeholder just surfaced — and asks what the project manager should do next. The wrong answers are usually legitimate actions performed out of order. Anchor yourself in the life cycle sequence and the process flows.
• The best-fit-artifact scenario. A described need (track who’s accountable, show remaining sprint work, justify starting the project) must be matched to the one document or chart built for it. These are giveaway points if you’ve drilled the Domain 3 material.
• The role-discrimination scenario. Someone in the vignette approves funding, or removes impediments, or prioritizes the backlog — and you name the role. Sponsor, Scrum master, and product owner confusions are the favorite traps.
• The terminology-swap scenario. Two adjacent concepts — risk vs. issue, hybrid cloud vs. multicloud, RFI vs. RFP — appear in a scenario engineered so only one fits. Study these pairs as pairs; that’s how the exam frames them.

Registering for the exam

Registration runs through CompTIA and Pearson VUE. The path: buy a voucher ($399) from CompTIA’s store, create or sign into a Pearson VUE account, and schedule your sitting. You choose the delivery mode at scheduling time — an in-person Pearson VUE test center, or online proctoring through OnVUE from your home or office.

If you choose OnVUE, prepare your environment before exam day: you’ll need a reliable webcam and internet connection, a room where you can be alone with a cleared desk, and a government-issued ID for the check-in photo process. Run the OnVUE system test on the actual computer you’ll use, well in advance. A test center removes all of those variables in exchange for the commute, and it’s the safer pick if your home setup has unavoidable interruptions.

Vouchers have expiration dates, so don’t buy one until you’re within a few months of being ready. If you need to reschedule, Pearson VUE allows it without penalty up to a cutoff (typically 24 hours before the appointment) — check the current policy when you book.

A four-week study plan

This plan assumes roughly 8–10 hours per week and some working familiarity with IT. Adjust the runway, not the sequence, if you need more time.

Week 1 — Project Management Concepts. Take a short diagnostic practice set first to find your baseline; don’t skip this, because it tells you where the next three weeks should flex. Then work through Domain 1: project characteristics, roles, communication, quality, and the full risk and procurement flows. Drill the threat-response strategies and the RFI/RFP/RFQ distinctions until they’re reflexive. Finish the week with a domain-focused practice quiz and review every explanation — including for questions you got right.

Week 2 — Project Life Cycle Phases. Learn the phases as a story, not a list: why the business case precedes the charter, why stakeholder identification happens early, what planning produces, how execution is tracked, what closing requires. Build a one-page timeline of phases and their artifacts from memory, then check it. Cover both predictive and Agile life cycles, and note where they differ. End the week with mixed Domain 1 + 2 practice, since these two domains interleave constantly in real questions.

Week 3 — Tools, Documentation, and IT Basics. Two lighter domains, one week. For Domain 3, make a chart-recognition drill: name each chart type, its axes, and the question it answers. For Domain 4, focus wherever your background is thinnest — infrastructure people should study the governance, ESG, and enterprise software material; business-side people should study cloud models, networking basics, and resilience concepts. Take a full-length timed practice exam at the end of the week.

Week 4 — Integration and weak-point repair. Spend the first half of the week re-drilling every objective you missed on the Week 3 full-length test, using targeted practice by domain. Take a second full-length timed exam mid-week under real conditions — 90 minutes, no notes, no pausing. If you’re scoring comfortably above passing-level consistency, spend the final days on light review and rest. If not, push the exam date; a voucher reschedule is cheaper than a retake.

Throughout all four weeks, favor active practice over passive reading. Answering questions and studying the explanations you got wrong builds the discrimination skills PK0-005 actually tests; rereading notes does not.

Exam-day tips

• Triage the PBQs. If a performance-based question looks time-hungry, flag it, skip it, and return after the multiple-choice items. PBQs and MCQs both feed your score — don’t let one interactive item eat ten questions’ worth of clock.
• Read the last sentence of long scenarios first. The question stem tells you what actually matters in the vignette; then you can read the scenario knowing what to extract.
• Watch for qualifiers. Words like FIRST, NEXT, BEST, and MOST likely change the correct answer. Several options may be true; only one satisfies the qualifier.
• Answer everything. There’s no penalty for guessing. Flag uncertain items, pick your best answer anyway, and revisit if time allows.
• Trust the process order. When torn between two plausible actions, ask which comes first in the life cycle or process flow. PK0-005 rewards sequence discipline more than any other instinct.
• Arrive calm. For test centers, arrive early with your ID. For OnVUE, complete check-in the moment your window opens — the photo and room-scan process takes longer than people expect.

Quick reference

• PK0-005: maximum of 90 questions (multiple-choice + PBQs), 90 minutes, passing score 710 on a 100–900 scale.
• Voucher: $399 (after the May 2026 price change), exam delivered at a Pearson VUE test center or online via OnVUE. Launched November 2022. No prerequisites.
• Domain weights: Project Management Concepts 33%, Project Life Cycle Phases 30%, Tools and Documentation 19%, Basics of IT and Governance 18%.
• Project+ does not expire — no continuing education requirements.
• Prioritize Domains 1 and 2 (63% combined), but don’t concede the IT and documentation domains — they hold the most recoverable points.
• Study sequence-first: phases, process flows, and “what happens next” reasoning dominate the scenario questions.
• Four weeks at 8–10 hours per week is a realistic runway with IT background; let full-length timed practice scores tell you when you’re ready.