CompTIA PK0-005 Practice Test 2026

Explanation:
The chart reveals a consistent and significant pattern: the planned work (orange line) remains relatively high and stable across all sprints, while the actual work completed (blue line) is consistently and substantially lower. This indicates a persistent planning problem. The team is consistently committing to more work than it can deliver. The most logical and necessary action is for the team to use its historical actual performance (its true velocity) to adjust future sprint commitments, bringing the planned work in line with what is realistically achievable.

Detailed Analysis of Incorrect Options:
B. The team’s velocity is getting better.
This is incorrect. While the actual work completed (blue line) shows some minor fluctuations, there is no clear, sustained upward trend indicating that velocity is improving. It remains consistently below the planned work without closing the gap over time.

C. The team understands its velocity and is planning in an accurate manner.
This is the opposite of what the chart shows. Accurate planning would result in the orange (planned) and blue (actual) lines being very close together. The large, consistent gap demonstrates that the team does not understand its velocity and is planning in an inaccurate, overly optimistic manner.

D. The team is doing more work than planned.
This is factually false based on the chart. The blue line (actual work) is consistently below the orange line (planned work), meaning the team is consistently completing less work than planned.

References:
1.CompTIA Project+ PK0-005 Exam Objectives:
This question tests knowledge from Domain 1.0 "Project Management Concepts," specifically Agile principles and metrics like velocity, and Domain 4.0 "Project Tools and Documentation," relating to using burndown/burnup charts for performance analysis.

2.Agile/Scrum Principles:
A core tenet of Agile is using past performance to inform future planning. The chart is a classic example of a team failing to do this. The recommended action (Answer A) is to conduct a sprint retrospective, analyze the cause of the consistent over-commitment, and use the average of the actual work completed (blue line) as a baseline for committing to work in future sprints.

Explanation:

This question tests knowledge of lessons learned and organizational process assets. The project manager is reviewing a prior project's notes and feedback to understand known issues before working on a project enhancement. This activity focuses on capturing historical issues and storing them in a reusable knowledge base so that future projects (like the enhancement) can benefit from past experiences.

✔️ Correct Option: A. A plan for capturing issues and conflicts in a project's knowledge base
The scenario describes reviewing notes and feedback from a prior project to identify known issues that could affect a new project enhancement. This is exactly the purpose of a lessons-learned or knowledge management plan: to systematically capture issues, conflicts, resolutions, and feedback from completed projects and store them in a centralized, searchable knowledge base. By doing this before starting the enhancement, the team avoids repeating past mistakes and leverages proven solutions. The knowledge base becomes an organizational asset that improves decision-making and risk identification for future projects.

❌ Incorrect options:

❌ B. A plan for avoiding potential issues that may arise during project execution
This describes a risk management plan focused on proactive avoidance strategies for future unknown risks. However, the scenario specifically involves reviewing known issues from a prior completed project, not planning avoidance strategies for unidentified future risks. The emphasis is on capturing historical data, not on forward-looking avoidance tactics.

❌ C. A plan for documenting the outcomes of the project
This describes a close-out or final reporting plan that captures deliverables, performance metrics, and formal acceptance at project completion. While outcomes may include some issues, the scenario focuses on gathering feedback and known issues before starting an enhancement, not documenting final outcomes of a completed project. The intent is reuse, not closure.

❌ D. A plan for addressing and resolving identified issues once the project has been completed
This describes a post-project issue resolution plan, which is illogical because completed projects typically do not resolve new issues after closure. The scenario involves reviewing prior issues to inform a future enhancement, not addressing or resolving those issues after the prior project has already ended. Issues from a completed project are archived, not actively resolved.

🔧 Reference:
→ CompTIA Project+ (PK0-005) Exam Objectives – Section 4.1 (Summarize the importance of project closure and lessons learned) identifies capturing issues, conflicts, and feedback into a knowledge base as a key activity for improving future projects.

Explanation:

The company is selecting a project management consulting firm based on RFP responses. The selection criteria should balance cost, experience, and relevant expertise.

Comparing the firms:
Firm     Project Cost     # of Project Managers     Avg. Experience (years)     Similar Projects
Firm 1     $100,225     7     12     5
Firm 2     $100,325     7     6     4
Firm 3     $100,425     5     11     5
Firm 4     $100,625     7     12     5

Why Firm 1 is the best choice:
- Lowest cost: Firm 1 has the lowest project cost at $100,225, which is $100 less than Firm 2, $200 less than Firm 3, and $400 less than Firm 4.
- Strong experience: Firm 1 has an average experience of 12 years, tied with Firm 4 and significantly higher than Firm 2 (6 years).
- Relevant expertise: Firm 1 has completed 5 projects similar in scope to the RFP, tied with Firms 3 and 4, and better than Firm 2 (4 projects).
- Team size: Firm 1 provides 7 project managers, which is the same as Firms 2 and 4, and more than Firm 3 (5).

Firm 1 offers the lowest cost while maintaining top-tier experience (12 years), strong relevant experience (5 similar projects), and sufficient team size (7 PMs). This combination makes it the best value and most qualified choice.

Why other options are incorrect:
- B. Firm 2: Has lower cost than Firms 3 and 4, but significantly less experience (6 years vs. 12) and fewer similar projects (4 vs. 5) than Firm 1, while costing more.
- C. Firm 3: Has moderate experience (11 years) but higher cost than Firm 1 and only 5 project managers, which is fewer than the other firms.
- D. Firm 4: Has equivalent experience and similar projects to Firm 1, but costs $400 more.

References:
CompTIA Project+ PK0-005 Objective 2.5: Given a scenario, use the appropriate procurement documentation. This objective includes evaluating vendor responses based on cost, experience, and qualifications.

Explanation:
The scenario describes a critical failure immediately following a deployment. The new system is not functioning for its primary purpose (issuing payment orders), rendering it unusable for business operations. In such a severe situation, the fastest and most effective way to restore service and minimize business impact is to revert the system to its last known stable state—the pre-migration version. This action is defined in a Rollback Plan.

Why A is correct: A Rollback Plan is a predefined procedure for reversing a deployment or change in the event of a failure. Its purpose is to restore the previous operational state quickly. Since the migration is complete and has failed, executing the rollback plan is the direct and immediate solution.

Detailed Analysis of Incorrect Options:
B. Release plan:
A Release Plan is a high-level schedule that outlines the features, timelines, and resources for a release. It is a planning document, not an emergency response procedure for a failed deployment. It would have been created before the migration, not implemented after a failure.

C. Deployment plan:
The Deployment Plan is the set of procedures that was just executed to migrate and deploy the new system. Since the deployment itself is the cause of the problem, re-implementing the same plan would not resolve the issue and would likely repeat the failure.

D. Contingency plan:
A Contingency Plan is a proactive plan for dealing with a potentialrisk that has been identified. It is a "Plan B" for a specific foreseen event. The failure described is a current, active issue, not a risk. At this point, you are in response mode, not contingency mode. The rollback plan is often a specific type of contingency plan for deployment failures, but in this context, "rollback plan" is the more precise and direct answer for the action to take now.

References:
CompTIA Project+ PK0-005 Exam Objectives:
This question falls under Domain 2.0 "Project Life Cycle Phases," specifically related to the closing and handoff phases, and Domain 3.0 "Change Management," where managing the impact of changes and having backout procedures is critical.

IT Service Management (ITSM) & Change Management:
A fundamental principle in deployment and change management is having a verified and tested rollback plan for any high-risk change. This ensures that if a deployment causes unacceptable disruption, services can be quickly restored, minimizing downtime and financial loss.

Explanation:

This question tests conflict resolution techniques in project management. When stakeholders request changes that conflict with project constraints, the PM must choose a strategy to resolve the dispute. The scenario shows both parties adjusting their positions to reach a workable solution.

✔️ Correct Option:

D. Compromising.
Compromising occurs when each party gives up something to reach an acceptable solution. The end users reduced the scope of their change request, and the PM accepted a simplified version that fits the budget. Both sides made concessions to resolve the conflict quickly.

❌ Incorrect options:

A. Collaborating.
Collaborating seeks a win-win by integrating all concerns into a solution that fully satisfies everyone. Here the users did not get their full request, so it is not a full win-win integration.

B. Smoothing.
Smoothing emphasizes areas of agreement and downplays differences to reduce tension. The PM did not just de-emphasize the conflict; they negotiated a reduced change, which is an actual concession.

C. Avoiding.
Avoiding means withdrawing from or postponing the conflict. The PM engaged directly and negotiated a solution, so the conflict was addressed, not avoided.

🔧 Reference:
→ Conflict Resolution Techniques – CompTIA Project+ PK0-005 identifies Compromising as giving up elements to reach agreement when time or budget is constrained.

Explanation:
The list of contents provided is a classic and comprehensive outline for a Statement of Work (SOW). An SOW is a formal document that describes the entire scope of a project, including its objectives, deliverables, standards, schedule, and all other key requirements. It is the foundational document that defines what needs to be done, and it is precisely the type of document a client would provide to a project manager with the expectation that they will "just execute the plan."

Why D is correct: The listed items are the core components of an SOW:
Purpose, Scope of work, Deliverables, Acceptance criteria: Define the "what" and "how well."
Location of work, Period of performance, Deliverables schedule: Define the "where" and "when."
Applicable standards, Special requirements: Define the "how" and any unique conditions.
Payment schedule: Defines the commercial terms.

Detailed Analysis of Incorrect Options:
A. RFP (Request for Proposal):
An RFP is a document used to solicit proposals from potential vendors. It asks vendors to explain how they would do the work and at what price. The client in this scenario is not asking for a proposal; they are providing a finalized plan for execution, which is the output of a procurement process, not the initial request.

B. WBS (Work Breakdown Structure):
A WBS is a hierarchical decomposition of the total scope of work. It is a project team-facing document that breaks down deliverables into manageable work packages. It would not contain elements like "Payment schedule," "Location of work," or "Period of performance" in such a direct form. The provided document is a higher-level, contractual document from which a WBS would be derived.

C. SLA (Service Level Agreement):
An SLA is an agreement between a service provider and a customer that defines the level of service expected, focusing on measurable metrics like uptime, response time, and resolution time. It does not typically define the initial project's scope, deliverables schedule, or payment terms. An SLA is often used for ongoing operational support after a project is complete, not for defining the project work itself.

References:
CompTIA Project+ PK0-005 Exam Objectives:
This question falls under Domain 2.0 "Project Life Cycle Phases," specifically objective 2.4 "Explain the importance of procurement and vendor selection." A key part of procurement is understanding the different types of project documentation, with the SOW being the primary document that defines project scope and deliverables in a contractual agreement.

Project Management & Contracting:
The Statement of Work is a standard document in project management and contracting. It forms the basis of the agreement between the buyer and the seller, ensuring both parties have a clear and common understanding of the project's objectives and constraints.

Explanation:

For a large, complex project with regulatory and environmental considerations, the first step before developing a detailed project plan is to review the project charter. The charter provides the formal authorization of the project, defines objectives, identifies stakeholders, and sets the high-level scope and constraints. It acts as the foundation for all planning activities. Without reviewing the charter, the project manager risks creating a plan that is misaligned with organizational goals or compliance requirements.

⚠️ Distractor Notes:
A. Review the project charter:
✔ Correct. Ensures alignment with objectives, scope, and authority before planning.

B. Start the process of engaging the stakeholders:
Important, but stakeholder engagement comes after confirming the charter and initial scope.

C. Arrange a kickoff meeting:
The kickoff occurs after planning is complete and the baseline is approved, not before.

D. Evaluate potential risks:
Risk evaluation is part of planning, but it comes after reviewing the charter and defining scope.

📚 Reference:
CompTIA Project+ PK0-005 Exam Objective (Domain 1.3 – Apply project management concepts to initiate a project): The project charter is the first document to review before detailed planning.

PMBOK Guide (Initiating Process Group): The charter authorizes the project and provides the basis for planning.

Explanation:

This question addresses the challenge of "scope creep" and its direct impact on project scheduling. It focuses on the project manager's responsibility to lock down the work requirements to provide an accurate and realistic delivery date.

✅ A. Project scope:
The project scope defines the boundaries of the project—exactly what work is included and, more importantly, what is excluded. When a client continuously adds changes, the scope is in a state of flux, making it impossible to finalize a schedule. By meeting with stakeholders to agree on the project scope, the project manager creates a "baseline." Once the work is clearly defined and capped, the team can calculate the time required to complete those specific tasks and commit to a reliable delivery date.

❌ B. Project communication:
A communication plan identifies who needs information, how often, and through which channels. While important for managing stakeholder expectations, it does not solve the problem of a shifting workload or help in determining the technical completion date of the project.

❌ C. Project budget:
The budget represents the financial resources allocated to the project. While additional changes often increase costs, identifying the budget alone does not help set a delivery date. You can have an unlimited budget and still be unable to provide a timeline if the scope of work keeps expanding.

❌ D. Project objectives:
Project objectives are high-level goals (e.g., "Improve customer satisfaction"). While these guide the project, they are usually too broad to help with detailed scheduling. To set a delivery date, the team needs to know the specific tasks and deliverables (the scope) required to meet those objectives.

🔧 Reference:
→ CompTIA Project+ Scope Management
This official CompTIA resource confirms that defining and controlling the project scope is essential for maintaining the project schedule and preventing uncontrolled changes.

Explanation:

The chart provided is a Pareto chart, which follows the 80/20 rule: focus on the issues that occur most frequently because they have the greatest impact. In this case, the old operating system problem has 78 occurrences, far more than any other issue. Addressing this first will yield the biggest improvement in refurbishing desktops.

⚠️ Distractor Notes:
A. Replace missing peripherals because this process can be easy and less costly:
While it may be simple, it does not address the most frequent or impactful issue.

B. An old operating system issue has the most amount of occurrences:
✔ Correct. Highest frequency, therefore highest priority.

C. Damage to the monitor has the highest percentage:
Incorrect. It has the lowest frequency (only 5 occurrences).

D. Address each issue as discovered to avoid rework:
Inefficient. Pareto analysis prioritizes the most common/high-impact problems first.

📚 Reference:
CompTIA Project+ PK0-005 Exam Objective (Domain 2.2 – Analyze project performance data): Pareto charts are used to identify the most significant issues to prioritize corrective actions.

Explanation:

The Statement of Work is the formal document that defines:
What work is to be completed
Deliverables and requirements
Scope of the project
Responsibilities of the implementation partner

In this scenario, there’s a disagreement about whether all requirements were completed. The SOW is the contractual reference that clearly outlines what the partner was obligated to deliver, so it’s the correct document to resolve the dispute.

Why the other options are incorrect:

B. RFI (Request for Information): Used to gather general information from vendors before a contract is established—not for defining completed work.

C. RFQ (Request for Quotation): Used to obtain pricing information from vendors—again, part of procurement, not execution or validation of work.

D. WBS (Work Breakdown Structure): Breaks down project tasks into smaller components, but it is not a contractual document and does not define vendor obligations.

Exam Tip:
When a question involves contracts, deliverables, or disputes with vendors, think:
👉 “What document legally defines the work?” → SOW