PK0-005 CompTIA Project+ Certification (2026) Free Practice Exam Questions (2026 Updated)

Infrastructure as a service (IaaS) offers administrators more direct control over operating systems than other cloud service models. IaaS is a type of cloud computing service that provides virtualized computing resources such as servers, storage, network, and operating systems over the internet. IaaS allows users to rent or lease infrastructure resources on demand and pay only for what they use. IaaS gives users more flexibility and control over their infrastructure resources and enables them to configure, manage, and customize their operating systems according to their needs and preferences3

When reviewing objectives—especially in a new industry—the PM should start with company vision, mission, and values because they provide the highest-level alignment for why the organization is pursuing the work and how success should support strategic direction. In Project+ terms, objectives should tie back to business goals and the organization’s strategic intent; starting with vision/mission helps ensure the project’s objectives are meaningful, prioritized correctly, and framed in language leadership supports.

After that alignment is established, the PM can translate objectives into industry-specific constraints and success measures—where regulations/standards (A) become critical, especially in regulated industries. “Relevance to the global environment” (B) and “impact to the corporate brand” (D) are important considerations, but they are typically evaluated after the PM anchors the objectives to the organization’s strategic identity and purpose.

So the best first review item is company vision, mission, and values, which sets the “north star” for objectives; then the PM can validate feasibility and compliance via regulations, market/environment considerations, and brand implications.

When a project manager achieves a compromise, it often means that stakeholders may not be entirely satisfied with the outcome. However, compromise is sometimes necessary to balance differing needs, consistent with CompTIA Project+ principles on stakeholder management and negotiation.

The project manager should develop a rollback plan next after determining the appropriate maintenance window in the operational infrastructure change process. A rollback plan is a contingency plan that describes how to revert to the previous state of the system or infrastructure in case of a failure or disruption during the change implementation. A rollback plan can help to minimize the impact and risk of the change and ensure business continuity and stability.

A burndown chart is a visual representation of the remaining work versus the time required to complete it1. It is commonly used by agile teams to track the progress of each iteration or sprint and to forecast the project completion date2. A burndown chart shows the ideal work remaining line and the actual work remaining line, which can help the team identify any deviations or impediments and adjust accordingly1. A burndown chart is different from a Pareto chart, which shows the frequency of different causes of problems; a milestone chart, which shows the key events and deliverables of a project; and a Gantt chart, which shows the dependencies and durations of tasks in a project3. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects Part 2, page 173; Burndown Chart: What Is It & How to Use One for Agile - ProjectManager, Introduction and Components of a Burndown Chart sections; Burndown Chart: What it is, How to Use it, Example [2023] • Asana, Introduction and What is a burndown chart? sections.

A Finish-to-Start dependency implies that a subsequent activity cannot start until a previous one finishes. In this scenario, the manufacturing process (subsequent activity) cannot begin until the critical raw materials (previous activity) have been delivered. This type of dependency is the most common in project schedules and is likely being affected by the global shipping slowdown, causing delays in the start of the project's production run.

This answer is based on the best practice of defining access requirements in project management, which is to identify the roles, responsibilities, and permissions of the project team members and other stakeholders who need to access the project information, resources, and deliverables12. The first step in this process is to assess the resource pool, which is the availability and capability of the human resources that can be assigned to the project34. By assessing the resource pool, the project manager can determine the skills, experience, and security clearance of the potential project team members, as well as their reporting relationships, communication preferences, and expectations56. This information can help the project manager to define the access requirements for each role and stakeholder group, and to assign the appropriate level of access to the project data, documents, tools, and systems78. References = CompTIA Project+ Certification Study Guide9, CompTIA Project+ Certification Exam Objectives10, What is Requirements Management?, How to Write Project Requirements, A Guide to Functional Requirements, Project Requirements Management: A Quick Guide, Creating clear project requirements, How to Define Project Roles and Responsibilities

Time zones are the most important factor to consider when setting up a troubleshooting session for team members who are located in different regions of the world. The project manager should ensure that the session is scheduled at a convenient and reasonable time for all participants, and avoid scheduling conflicts or communication delays. Time zones can also affect the availability and responsiveness of stakeholders, vendors, and customers1.

The waterfall methodology is a project management framework that follows a linear and sequential process, where each stage of the project must be completed before moving on to the next one. The stages of the waterfall model are initiation, planning, execution, and closure, as described in the question12.

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.

Pll stands for personally identifiable information, which is any data that can be used to identify a specific individual. Examples of Pll include name, address, phone number, email address, social security number, passport number, driver’s license number, etc. IP address and email address are both Pll because they can be used to trace the identity and location of a person. Medical record and test result values, name and year of birth, and x-ray and blood type are not Pll by themselves, but they can become Pll if they are combined with other data that can link them to a specific individual. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Security, page 331. CompTIA Project+ Certification Exam Objectives, Domain 4: Project Security, Objective 4.1: Given a scenario, apply security best practices to a project, Sub-objective: Identify and classify Pll.

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.

An issue log is a document that records and tracks any issues that arise during a project and how they are resolved1. It is different from a risk register, which records and tracks potential risks that may or may not occur during a project2. When a risk becomes an issue, it means that it has occurred and has a negative impact on the project. Therefore, the project manager should update the issue log next to document the compliance issue, its cause, its impact, its priority, its owner, and its resolution status3. Updating the issue log will help the project manager communicate the issue to the stakeholders, monitor the progress of the mitigation plan, and prevent similar issues from happening again4. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 11: Executing Projects Part 2, page 331; Project Risk Mitigation Guide + Starter Kit | Smartsheet, Risk Register section; How to Make a Risk Management Plan (Template Included) - ProjectManager, Risk Register section; Issue Log - Project Management Knowledge, Introduction section; Issue Log Template: Free Download | ProjectManager, Introduction and How to Use an Issue Log sections.

RACI is a tool that best illustrates how team members with different roles should interact on the team. RACI is an acronym that stands for responsible, accountable, consulted, and informed. RACI is a type of responsibility assignment matrix (RAM) that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project. RACI can help to improve communication, collaboration, and accountability among team members and avoid confusion, duplication, or conflicts3

A rollback plan is a part of the project management plan that defines how to revert the system to its previous state or baseline if the change or migration fails or causes unacceptable impacts1. A rollback plan is different from a contingency plan, which is a plan to deal with a specific risk event that may or may not occur2. A release plan and a deployment plan are not relevant to the scenario, as they are used to plan and execute the delivery and installation of the system, not to undo them. Therefore, the correct answer is A. Rollback plan.

Scrum requires the most availability from the business team among the given options. Scrum is a popular agile framework that organizes work into short iterations called sprints, usually lasting one to four weeks. Scrum emphasizes collaboration between teams, customers, and stakeholders and encourages open communication and transparency throughout the project lifecycle. Scrum requires frequent involvement and feedback from the business team through activities such as product backlog refinement, sprint planning, sprint review, sprint retrospective, and daily scrum meetings.