CompTIA PK0-005 - CompTIA Project+ Certification (2026)

The program manager should schedule a call with the vendor PM and vendor executive to review the statement of work (SOW), which is a document that defines the scope, deliverables, timeline, quality, and payment terms of the project. The program manager should clarify the expectations and criteria for user acceptance testing (UAT), which is a process of verifying that the system meets the user’s requirements and expectations. The program manager should also discuss the reasons for the UAT failure and the corrective actions needed to resolve the issues. The program manager should not approve the invoice until the UAT is successfully completed, as this would compromise the quality and value of the project. The program manager should also not escalate the issue or work on a compromise without first reviewing the SOW and communicating with the vendor12.

The output of this exercise where the project manager is comparing the cost of the project to the cost savings the project will produce when it is complete will produce the return on investment (ROI). ROI is a financial metric that measures the profitability or efficiency of an investment by comparing its benefits or returns to its costs. ROI can help to evaluate the value or worth of a project and support decision making and prioritization. ROI is calculated by dividing the net benefits (benefits minus costs) by the total costs and multiplying by 100 to get a percentage.

A program is a group of related projects managed in a coordinated way to achieve benefits and control that would not be available if the projects were managed separately. Option C—a consolidation of related projects with a common goal—matches the standard program definition used across project management frameworks and aligns with CompTIA Project+ terminology that distinguishes projects (temporary endeavors producing unique outputs) from programs (coordinated management of multiple related projects).

Option A is incorrect because unrelated projects do not form a program; that is closer to a portfolio (a collection of projects/programs managed to meet strategic objectives, not necessarily related). Option B describes operational tracking, not a program definition. Option D sounds like scope decomposition or workload definition, which is not what a program is.

Programs typically have overarching governance, shared resources, interdependent timelines, and integrated risk/benefit management. The focus is on achieving strategic outcomes/benefits across the combined effort, such as rolling out a suite of capabilities or transforming an end-to-end business process via multiple projects.

DevOps architecture integrates development and operations to enhance the software development lifecycle. It emphasizes continuous integration and delivery, automation, and collaboration, ensuring that factors like reliability, scalability, security, and cost-effectiveness are integral to project goals and objectives. By adopting DevOps practices, organizations can achieve faster deployment times, improved system stability, and efficient resource utilization.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, DevOps is recognized as a methodology that supports these critical factors.

A business case exists to justify why the project should be done—what problem/opportunity it addresses and what benefits/value it provides relative to cost. In CompTIA Project+ objectives, the business case is part of discovery/concept and initiation, linked to business objectives and ROI, and is used to support approval decisions. The first, foundational element of that justification is clearly stating the problem being solved (or the opportunity being captured). ()

Option D best captures that intent: specify what problem is being solved by the project. Once the problem is defined, the business case typically expands to include expected benefits, costs, assumptions, constraints, and high-level risks—but those are supporting elements, not the primary objective.

Option A is more aligned to risk management artifacts (risk register, issue log). Option B (timeline and budget) is more aligned to the project plan and estimating/scheduling. Option C (specific tasks) aligns to a WBS or backlog planning. The sponsor is asking for the “why” and justification for investment before committing effort—so the business case objective is to articulate the problem and the value of solving it. ()

The total amount that should be budgeted for the task is calculated by adding the expected value of the risk to the original estimate. The expected value of the risk is the product of the probability and the impact of the risk. In this case, the expected value of the risk is 0.2 x (5 days and $1,000) = 1 day and $200. Therefore, the total amount that should be budgeted for the task is 9 days and $3,000 + 1 day and $200 = 10 days and $3,2001.

The project manager should have a meeting with the project sponsor and main stakeholders first after discovering that some of the legal requirements have not been addressed during the project concept preparation. The project sponsor and main stakeholders are the key decision-makers and influencers of the project. They have the authority and responsibility to approve or reject any changes to the project scope, budget, or schedule. Having a meeting with them can help to communicate the issue, assess the impact, explore alternatives, and seek guidance on how to proceed with the project34

The project scope is the document that defines and describes the project objectives, deliverables, requirements, boundaries, assumptions, and constraints. It also includes the success criteria that should be fulfilled by the product or service to meet the stakeholder expectations and the business case. The success criteria are the measurable standards that indicate whether the project has achieved its intended results. The other options are not correct because:

A quality plan is the document that defines and describes the quality standards, policies, procedures, tools, and techniques that will be applied to the project to ensure that the deliverables meet the requirements and the success criteria.

Contract obligations are the terms and conditions that bind the parties involved in a contractual agreement, such as the project manager, the customer, the sponsor, and the vendor. Contract obligations specify the roles, responsibilities, deliverables, payments, and penalties of each party.

A work breakdown structure (WBS) is a graphical representation of the project scope that breaks down the deliverables into smaller and manageable components. A WBS shows the hierarchy and relationship of the project elements, but does not include the success criteria. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects, Part 2 (Scope, Quality, and Risk), pages 175-179; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.1: Given a scenario, create a project charter and project management plan.

Informal communication is a type of communication that is casual, spontaneous, and unstructured. It does not follow any predefined rules, protocols, or formats. Examples of informal communication include email, phone calls, conversations in the hallway, and impromptu meetings12. The sponsor is using informal communication to communicate with the team, as these methods are convenient, flexible, and personal. However, informal communication may also have some drawbacks, such as lack of documentation, inconsistency, and potential for misunderstanding3. Therefore, the sponsor should also use formal communication when necessary, such as for official reports, contracts, and presentations4.

A formal contract is a legal document that defines the terms and conditions of the agreement between the project parties, such as the scope, schedule, budget, quality, deliverables, roles and responsibilities, payment methods, and dispute resolution mechanisms. A formal contract is essential for external projects, especially when there is an exchange of money involved, to protect the interests and rights of both parties and to ensure mutual understanding and compliance. A formal contract is different from a business requirement, which is a statement of the needs and expectations of the customer or stakeholder for the project outcome. A formal contract is also different from a client statement of work, which is a document that describes the work to be performed, the deliverables to be provided, and the acceptance criteria to be met by the project vendor or contractor. A formal contract is also different from a project charter, which is a document that authorizes the project and provides the high-level information about the project objectives, scope, stakeholders, and project manager. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Integration Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 4: Project Integration Management2; 11 Essential Documents To Use as a Project Manager3