Free PK0-005 Practice Test Questions and Answers (2026)

When a deliverable is rejected, the change control process begins by documenting the new requirements. The project manager identifies stakeholders using the RACI matrix to ensure the right people are involved in the impact assessment. Impact assessment (cost, time, risk) must occur before seeking formal approval (sign off) from the Change Control Board (CCB). Once approved, project documents like the Change Log and Schedule are updated to reflect the new baseline. Finally, the technical work is performed (Update and test), verified by the customer (Demonstration), and communicated to the wider organization.

PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition: Section 4.6 "Perform Integrated Change Control," pages 113-120 (Process flow, Change Log updates, and Impact Assessment).

PMI, PMBOK® Guide – Seventh Edition: Section 2.5 "Project Work Performance Domain," pages 77-78 (Change control and document updates).

Project Management Institute: The Standard for Project Management, Section 3.8 "Navigate Complexity," regarding impact assessment and stakeholder engagement via RACI.

IEEE Std 12207-2017: ISO/IEC/IEEE International Standard - Systems and software engineering - Software life cycle processes (Section 6.3.5, Configuration Management and Change Control).

A wiki knowledge base is the most suitable tool for storing lessons learned. It functions as a centralized, collaborative platform where team members can easily create, edit, and link information. This structure allows for the creation of a dynamic, searchable, and accessible repository. Lessons learned can be documented, categorized, and easily retrieved by future project teams, effectively turning past experiences into organizational process assets. This aligns with the core purpose of knowledge management in project environments.

A. Whiteboard: A whiteboard is a tool for temporary brainstorming and visualization during meetings, not for permanent, searchable storage of critical project documentation.

C. Content management system: While a CMS can store documents, a wiki is more specifically designed for collaborative knowledge creation and interlinking, which is ideal for a lessons learned repository.

D. Workflow platform: A workflow platform is designed to manage and automate tasks and processes, not to function as a primary, long-term repository for organizational knowledge.

1. Project Management Institute (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 4.5

"Knowledge Area

" and the discussion on Organizational Process Assets (OPAs). The guide emphasizes that lessons learned repositories are a key OPA

and tools that facilitate their creation and use are essential. A wiki is a prime example of such a tool.

2. Syracuse University

School of Information Studies. (n.d.). IST 641: Project Management. Course materials discuss knowledge management in projects

identifying wikis as a common and effective tool for creating a lessons learned knowledge base due to their collaborative and accessible nature.

3. Meredith

J. R.

Shafer

S. M.

& Mantel Jr.

S. J. (2017). Project Management: A Managerial Approach (10th ed.). Wiley. Chapter 5

"Project Planning

" discusses the importance of the project management information system (PMIS) for storing historical information and lessons learned. The text describes systems with wiki-like functionality as ideal for this purpose.

The business case is the primary document created during the project initiation phase to provide justification for undertaking the project. It articulates the business problem or opportunity, analyzes the costs and benefits, and explains how the project aligns with the organization's strategic goals. This document is then presented to stakeholders and decision-makers to secure formal approval and funding to proceed. The scenario's focus on "business reasons and benefits" for "approval" directly corresponds to the purpose of a business case.

A. Statement of work: This document provides a narrative description of the project's deliverables and the work required to create them. It focuses on the what, not the why.

C. Requirements document: This document specifies what the final product or service must do. It is typically developed during the planning phase, after the project has been approved.

D. Work breakdown structure: This is a planning tool that decomposes the project scope into smaller, manageable work packages. It is created after the project is approved and scope is defined.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 1.2.6.1

Project Business Case. The guide states

"The project business case is a documented economic feasibility study used to establish validity of the benefits of a selected component... and that is used as a basis for the authorization of further project management activities."

2. CompTIA. (2022). The Official CompTIA Project+ Student Guide (Exam PK0-005). Module 1

Topic 1D: Initiating a Project. This official guide specifies that the business case is a key input to the project charter and is used to justify the project's existence and secure approval.

3. Larson

E. W.

& Gray

C. F. (2021). Project Management: The Managerial Process (8th ed.). McGraw-Hill Education. Chapter 2

"Organization Strategy and Project Selection

" discusses the business case as the document that provides the rationale and justification for a project

forming the basis for its selection and approval. (This is a widely used textbook in university project management courses).

Infrastructure as a Service (IaaS) is a cloud computing model where a vendor provides users with virtualized computing resources, such as servers, storage, and networking, over the internet. In this model, the consumer is responsible for managing the operating systems, data, and applications. This gives administrators the most direct control over the OS, including the ability to install, patch, and configure it according to specific project requirements. The cloud provider manages the underlying physical infrastructure, but control of the OS layer resides with the customer.

B. Software as a service: The provider manages the entire stack, including the application and the operating system. The user has no control over the OS.

C. Functions as a service: This is a serverless model where the underlying OS is completely abstracted from the user, who only manages code functions.

D. Platform as a service: The provider manages the platform, including the hardware and the operating system. The user only controls the applications they deploy.

1. Mell

P.

& Grance

T. (2011). The NIST Definition of Cloud Computing (NIST Special Publication 800-145). National Institute of Standards and Technology. Retrieved from https://doi.org/10.6028/NIST.SP.800-145.

Page 2

Section "Infrastructure as a Service (IaaS)": "The capability provided to the consumer is to provision processing

storage

networks

and other fundamental computing resources where the consumer is able to deploy and run arbitrary software

which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems

storage

and deployed applications..."

2. Armbrust

M.

Fox

A.

Griffith

R.

Joseph

A. D.

Katz

R.

Konwinski

A.

... & Zaharia

M. (2009). Above the Clouds: A Berkeley View of Cloud Computing (Technical Report No. UCB/EECS-2009-28). University of California

Berkeley.

Page 3

Section 2.1 "Classes of Utility Computing": This foundational paper distinguishes the service models. It describes IaaS (e.g.

Amazon EC2) as providing virtual machines where users "are responsible for installing and maintaining the operating system and application stack." This contrasts with PaaS and SaaS

where the OS is managed by the provider.

Project portfolio management is the centralized management of one or more portfolios to achieve strategic objectives. A key activity is prioritizing projects to ensure they align with the organization's strategic plan. The strategic plan is fundamentally built upon the company's vision (the desired future state) and its mission statement (the organization's core purpose and focus). Therefore, when a program manager evaluates projects for prioritization, they must measure each project's contribution to fulfilling the mission and achieving the vision. These two elements are the primary drivers of strategic direction.

B. Global environment: This is an external factor that influences the strategic plan's creation, not a core component of the plan itself used for prioritization.

C. Brand value: This is typically a desired outcome or a key performance indicator (KPI) derived from the strategy, not a foundational strategic document.

E. Portfolio budget: This is a resource constraint. Projects are prioritized to fit within the budget, but the budget itself is not the basis for strategic alignment.

F. Local legislation: This represents an external compliance requirement or constraint that projects must adhere to, not a guiding principle of the strategic plan.

1. Project Management Institute. (2017). The Standard for Portfolio Management (4th ed.). Section 3.2

Portfolio Strategic Management

p. 27. The text states

"Portfolio strategic management activities are performed to ensure that the portfolio is aligned with the organization’s strategy... The organizational strategy is developed by senior leadership to articulate the organization’s vision

mission

goals

and objectives."

2. CompTIA. (2022). CompTIA Project+ PK0-005 Exam Objectives. Section 1.1

"Explain the importance of a project." This objective emphasizes the need for projects to have "strategic alignment

" which is directly tied to the organization's overarching vision and mission.

3. Meredith

J. R.

Shafer

S. M.

Mantel Jr.

S. J.

& Sutton

M. M. (2017). Project Management: A Managerial Approach (10th ed.). Chapter 2

"Strategic Management and Project Selection

" p. 42. The chapter explains that project selection models must be aligned with the organization's mission and goals

stating

"To make such a link

the firm’s mission statement is a good starting point."

Meeting minutes are the official record of a meeting's proceedings. Their primary purpose is to document key discussions, decisions made, and action items assigned to team members, including deadlines. By preparing and distributing meeting minutes after each weekly review, the project manager creates a formal communication artifact. This ensures that team members who were unable to attend are kept informed of their responsibilities and the project's current status, directly addressing the need to communicate assignments.

A. Status report: A status report provides a high-level summary of project progress to stakeholders, not the detailed action items or assignments from a specific internal team meeting.

B. Project plan: The project plan is a formal, approved document used to guide project execution and control. It is not used for recording weekly meeting outcomes or individual assignments.

C. Change log: A change log is a specific document used exclusively to track the status of change requests throughout the project lifecycle, not for general meeting assignments.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 10.2.3.1

Project Communications. This section lists meeting minutes as a key component of project communications

which are outputs of the Manage Communications process used to record and distribute information.

2. University of California

Berkeley. (n.d.). Project Management Framework. Project Communication Tools. The framework identifies meeting minutes as a crucial tool for "documenting meeting discussions

decisions

and action items" to be distributed to attendees and key stakeholders.

3. Sanghera

P. (2019). CompTIA Project+ PK0-005 Certification Guide. Pearson IT Certification. Chapter 6

"Project Communication Management

" explicitly states that meeting minutes document decisions and action items and are essential for keeping all team members

including absent ones

informed. (Note: While a commercial publication

it is authored by a recognized authority and directly maps to the official exam objectives

serving as vendor-aligned documentation).

A Gantt chart is a primary project scheduling tool that visually maps tasks against a timeline, showing start and end dates, dependencies, and resource assignments. By reviewing the Gantt chart weekly, the Project Manager (PM) actively communicates the plan and clarifies which tasks are current, upcoming, and critical. This practice directly addresses the team's uncertainty about their daily activities by providing a clear, shared understanding of priorities and deadlines, which is a core responsibility of the PM in executing the project plan.

A. A simple task list lacks the essential context of timelines, durations, and dependencies that a Gantt chart provides for daily planning.

B. The scope of work is a high-level document defining project objectives and deliverables, not the detailed, day-to-day tasks for team members.

D. Managing the team's daily tasks is the responsibility of the PM, not the project sponsor, whose role is more strategic and high-level.

1. CompTIA. (2022). The Official CompTIA Project+ Student Guide (Exam PK0-005). CompTIA Learning and Training. Chapter 6

"Create a Project Schedule

" Section 6-3

discusses bar charts

such as the Gantt chart

as the primary method for displaying the project schedule and communicating task timelines to stakeholders.

2. Heagney

J. (2022). Fundamentals of Project Management (6th ed.). American Management Association. Chapter 10

"Scheduling the Work

" explains that Gantt charts are used to "show the timeline for all the tasks in a project... [and] are the most widely used method for project scheduling" (p. 121). This highlights its role in clarifying work timelines.

3. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Newtown Square

PA: Project Management Institute. Section 2.2.3

"Project Team

" details the project manager's role in "facilitating and leading the project team" to accomplish project objectives

which includes clarifying work assignments. The sponsor's role is defined separately as providing resources and support.

Multiauthoring software, also known as collaborative software, is specifically designed to allow multiple users to create, edit, and manage a shared set of documents. A fundamental feature of these platforms is version control, which automatically tracks changes, logs who made them, and allows for the retrieval of previous versions. This directly addresses the scenario of a project manager diligently maintaining version control for requirements documentation, which is often a collaborative effort involving various stakeholders. These tools provide a centralized and controlled environment for managing document history.

B. Word processor: A standalone word processor lacks robust, built-in version control for collaborative work; managing versions is typically a manual and error-prone process (e.g., saving files with different names).

C. Real-time polling: This is a tool for gathering immediate feedback or votes from a group and is not used for creating or managing the version history of documents.

D. Conferencing platforms: These platforms facilitate virtual meetings and communication. While documents may be shared, the platform itself is not the tool for authoring or versioning them.

1. Schwalbe

K. (2019). Information Technology Project Management (9th ed.). Cengage Learning. In Chapter 10

"Project Communications Management

" the text discusses tools for information distribution

highlighting collaborative tools like SharePoint and Google Docs that provide a "single repository for project information" and include "version control features" (pp. 398-399). This textbook is standard university courseware.

2. Heagney

J. (2016). Fundamentals of Project Management (5th ed.). AMACOM. In Chapter 12

"Project Management Software

" the author discusses Project Management Information Systems (PMIS) which often include document management repositories with features like "check-in/check-out and version control" to manage project artifacts collaboratively (p. 187). This text is frequently used in university-level project management courses.

The Statement of Work (SOW) is a formal, legally binding document that is part of the contract between a buyer and a seller (in this case, the project and the implementation partner). It provides a detailed narrative description of the products, services, or results to be delivered. The SOW explicitly defines the scope of work, deliverables, acceptance criteria, and timelines. In a disagreement over what work was completed, the SOW serves as the authoritative source to clarify the contractual expectations and resolve the dispute.

B. RFI: A Request for Information (RFI) is an early-stage procurement document used to gather general information from potential suppliers; it is not a contract and does not define final requirements.

C. RFQ: A Request for Quotation (RFQ) is used to solicit price quotes from vendors for specific goods or services. While it contains requirements, the SOW is the more comprehensive contractual document detailing the full scope of work.

D. WBS: A Work Breakdown Structure (WBS) is an internal project management tool that decomposes the total project scope into manageable pieces. It is not the contractual agreement with an external partner.

1. CompTIA. (2022). CompTIA Project+ PK0-005 Exam Objectives. Section 4.2

"Given a scenario

use project management documentation." The SOW is listed as a key project document.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 12.1.1.3

Procurement Statement of Work. The guide states

"The statement of work (SOW) is a narrative description of products

services

or results to be delivered by the project... The procurement SOW is developed from the project scope baseline and defines only that portion of the project scope that is to be included within the related contract."

3. University of Maryland

Project Management Center for Excellence. (n.d.). Glossary of Project Management Terms. Defines Statement of Work (SOW) as: "A detailed description of the products or services to be supplied under a contract." This highlights its role in defining contractual obligations.

4. Carnegie Mellon University

Software Engineering Institute. (1995). A Manager's Checklist for Validating Software Cost and Schedule Estimates (CMU/SEI-95-SR-004). Page 10. The document describes the SOW as the instrument that "establishes and defines the project-specific activities

deliverables

and their respective timelines which serve as a basis for a contractual agreement between the buyer and seller."

A project organizational chart is a graphical display of project team members and their reporting relationships. Its primary purpose is to clarify the project's formal structure, showing who reports to whom and the different functional groups involved. By creating and sharing this chart, the project manager can visually communicate each member's position and relationship to others, directly addressing the team's confusion about roles and structure.

A. A project plan is a comprehensive formal document, not a specific chart designed to clarify team member roles visually.

B. A project road map is a high-level strategic overview of project goals and deliverables against a timeline, not team structure.

C. A project milestone chart shows key dates and events in the project schedule, not the roles and responsibilities of team members.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 9.1.2.3

Data Representation. This section explicitly lists "hierarchical charts

" such as a project organization chart

as a tool to show positions and relationships.

2. CompTIA. (2022). CompTIA Project+ PK0-005 Exam Objectives. Domain 2.1

"Given a scenario

manage project resources." This objective covers the need to define and document project roles and responsibilities.

3. University of Washington. (n.d.). Project Management for Construction - Course Materials. "The project organization chart defines the lines of communication and authority... It is essential that each person on the project understands his or her role."