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

To account for potential risks, project managers use Expected Monetary Value (EMV) analysis. EMV is calculated by multiplying the probability of a risk event by its potential impact and adding this to the base estimate.

Base estimate: 9 days, $3,000

Risk impact: 5 additional days, $1,000 extra cost

Probability of risk: 20% (0.2)

Calculations:

Time: 9 days + (0.2 * 5 days) = 9 + 1 = 10 days

Cost: $3,000 + (0.2 * $1,000) = $3,000 + $200 = $3,200

However, to ensure sufficient contingency, it ' s prudent to budget for the full potential impact:

Time: 9 days + 5 days = 14 days

Cost: $3,000 + $1,000 = $4,000

But since the risk has only a 20% chance of occurring, the EMV approach provides a balanced estimate:

Time: 9 days + 1 day (20% of 5 days) = 10 days

Cost: $3,000 + $200 (20% of $1,000) = $3,200

Therefore, the most accurate budget considering the risk is 10 days and $3,200.

This aligns with the CompTIA Project+ PK0-005 exam objectives under Domain 1.4: Given a scenario, perform risk management activities, which includes understanding and applying EMV analysis.

A Request for Proposal (RFP) is a document issued by an organization to solicit proposals from potential vendors for a specific solution or service. It outlines the organization ' s requirements and criteria for evaluation, allowing vendors to propose how they would meet those needs. An RFP is appropriate when the company seeks detailed proposals for a solution to its specific needs.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 3.4: Explain important project procurement and vendor selection concepts, understanding the use of RFPs is essential for effective procurement management.

The project sign-off is the formal acceptance of the project deliverables by the client, stakeholder, or customer. It also marks the closure of the project and the release of the final payment. If the project sign-off is not completed, the project may still incur costs and liabilities, which can explain the losses in the financial report. Therefore, the project manager should complete the project sign-off as soon as possible to avoid further losses12.

Archiving project documentation is an important process to ensure that the project information is stored, retrieved, and updated in a consistent and efficient manner1. It also helps to meet legal requirements, enable long-term analysis, and support new projects and team members1. If the documentation was not archived as per the PMO standards, it would be difficult for the current project manager to find the relevant documents and learn from the previous project. This would cause the current project manager to keep asking questions to the previous project manager, who may not have all the answers or may not be available. Therefore, the most likely cause of this situation is that the documentation was not archived as per the PMO standards. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing the Project, page 403; How to Archive a Completed Project: A Guide for PMOs, Introduction and Benefits sections.

A defect log specifically tracks bugs, errors, or defects discovered in the product. It includes descriptions, severity, and resolution. Issue logs capture broader non-technical challenges, while change logs and risk registers serve different purposes.

the brand of a project should deliver the message about its value and goals, and a proper brand helps the project get the necessary support and increases loyalty. The project that promotes new initiatives to expand its benefit to other communities is the one that best represents the project impact to a company’s brand value, as it shows the company’s vision, cause, and reputation.

Infrastructure as a service (IaaS) is a cloud model that provides on-demand access to cloud-hosted physical and virtual servers, storage, and networking resources. IaaS customers can provision, configure, and use these resources as they would use on-premises hardware, but without the hassle of purchasing, installing, managing, and maintaining them. The cloud service provider owns, manages, and maintains the hardware and computing resources in its own data centers, and charges the customers based on their usage. IaaS is suitable for customers who need flexibility, scalability, and control over their IT infrastructure, and who want to avoid the high costs and complexity of owning and operating their own hardware. The other options are not correct because:

Software as a service (SaaS) is a cloud model that provides on-demand access to ready-to-use, cloud-hosted application software. SaaS customers do not need to install, update, or maintain the software, as the cloud service provider handles all the technical aspects. SaaS is suitable for customers who need to access common applications, such as email, office productivity, or customer relationship management, without worrying about the underlying infrastructure or platform.

Data as a service (DaaS) is a cloud model that provides on-demand access to cloud-hosted data sources, such as databases, data warehouses, or data lakes. DaaS customers can query, analyze, and visualize the data, as well as integrate it with other applications or services, using APIs or web interfaces. DaaS is suitable for customers who need to leverage data from various sources, such as social media, IoT devices, or third-party providers, without having to store, manage, or process the data themselves.

Platform as a service (PaaS) is a cloud model that provides on-demand access to a complete, ready-to-use, cloud-hosted platform for developing, running, maintaining, and managing applications. PaaS customers can use the platform’s tools, frameworks, libraries, and services to create and deploy applications, without having to worry about the underlying infrastructure or software. PaaS is suitable for customers who need to develop, test, and deploy applications quickly and efficiently, and who want to take advantage of the cloud’s scalability, reliability, and security features. References = IaaS vs. PaaS vs. SaaS; AWS Fundamentals: Understanding Compute, Storage, Database, Networking & Security; What are the different types of cloud computing?; What is Cloud Storage and How to Use It

When a project manager observes that the project ' s outcomes do not align with expectations, despite the vendor fulfilling all contractual obligations as per the Statement of Work (SOW), the appropriate next step is to perform a gap analysis. This analysis helps identify discrepancies between the current state (what has been delivered) and the desired state (stakeholder expectations).

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Given a scenario, perform risk management activities, performing a gap analysis is a critical activity to assess and address such discrepancies. The gap analysis will provide insights into areas where the project may not be meeting stakeholder expectations, allowing the project manager to develop strategies to bridge these gaps.

The PM is building a Work Breakdown Structure (WBS). A WBS is the structured decomposition of the project’s deliverables and scope into progressively smaller pieces until you reach the lowest practical level of detail (often called work packages), which can then be scheduled, estimated, assigned, and tracked. In the CompTIA Project+ objectives, the WBS is explicitly listed as a planning artifact used to break down the work during initiation/planning activities.

The other options don’t fit the “smallest activity components” description. A milestone chart highlights key checkpoints/dates, not the granular decomposition of work. A task board visualizes workflow status (e.g., to-do/in-progress/done) but doesn’t inherently define the decomposition structure. A detailed project plan is broader and would include schedule, resources, budget, and governance—often informed by the WBS rather than being the decomposition itself.

By creating the smallest components list, the PM is effectively decomposing scope into manageable units, which is precisely the purpose of a WBS in Project+ planning and control.