Free CompTIA PK0-005 Practice Questions 2026 - Page 14

Explanation:

When the project manager discovers that required resources are available for fewer hours than planned, this will affect the project schedule. Before making any changes to the project plan, the project manager must first analyze the impact of the issue.

An impact analysis helps determine:
How the schedule will be affected
Whether cost or scope will change
What alternative solutions might exist (e.g., reallocating resources, adjusting timelines)

This analysis provides the information needed to decide the best corrective action and to support any formal change request if necessary.

Why the Other Options Are Incorrect
A. Add a new risk
While the issue might become a risk, adding a risk does not address the immediate scheduling problem.

C. Escalate to the sponsor
Escalation should occur only after the project manager has analyzed the impact and identified possible solutions.

D. Raise a change request
A change request may eventually be needed, but the project manager should first perform an impact analysis to justify any change.

Reference
CompTIA Project+ PK0-005 – Change Management / Schedule Management

Explanation:

The project team gathers weekly to review progress, discuss updates, assign tasks, and address issues—this is a status meeting or stand-up/progress review meeting. When team members are absent, the project manager needs a concise, accurate record of what was discussed, decisions made, and—most importantly—new or updated assignments (action items, responsibilities, due dates) so those individuals can stay informed and continue contributing without falling behind.

Meeting minutes are the document specifically prepared for this purpose:
They capture key points from the meeting in a structured, readable format.
They include a section for action items (who is doing what, by when), which directly addresses assignments.
They are distributed shortly after the meeting (often within 24–48 hours) to all participants and absentees.

This ensures transparency, accountability, and continuity—especially in distributed or large teams where not everyone can attend every session.

Why the Other Options Are Incorrect
A. Status Report
A status report summarizes overall project health (progress against schedule, budget, risks, issues, milestones) and is typically prepared by the project manager for stakeholders or sponsors. It is not focused on capturing detailed meeting discussions or individual assignments from a specific team meeting.

B. Project Plan
The project plan defines scope, tasks, timeline, and resources. It is not updated weekly with meeting-specific assignments or progress notes. It does not serve as a record of weekly discussions.

C. Change Log
The change log tracks approved or requested changes to scope, schedule, cost, etc. It is unrelated to routine weekly progress reviews or team assignments unless a change was specifically discussed and approved in the meeting.

Explanation:

In this scenario, user acceptance testing failed, yet the vendor project manager is insisting on invoice approval. The program manager must first refer to the contractual agreement (Statement of Work, SOW) to determine whether payment is justified.

A. Escalate to Sponsor
Escalation is premature; the program manager should first address the issue directly with the vendor.

B. Compromise
Compromising without reviewing the SOW risks approving payment for incomplete or failed deliverables.

C. Approve Invoice
Incorrect — approving payment despite failed testing undermines accountability and project success.

D. Review SOW with Vendor Executives
Correct — this ensures both parties align on contractual obligations before deciding on payment.

Thus, the best step is to schedule a call with the vendor project manager and vendor executive to review the SOW, ensuring deliverables meet acceptance criteria before approving invoices.

Reference
CompTIA Project+ PK0-005 Exam Objectives: Domain 2.0 – Project Life Cycle, specifically 2.3: Explain the importance of vendor and contract management.
PMI PMBOK Guide: Procurement Management — emphasizes verifying deliverables against the contract before authorizing payment.

Explanation:

Personally Identifiable Information (PII) is any data that can be used to identify a specific individual, either directly or when combined with other available information.

Why B is Correct
A Home address is a primary direct identifier. It pinpoints an individual's physical location and is universally classified as PII that requires protection to prevent privacy breaches or identity theft.

Why E is Correct
Date of birth is considered a sensitive indirect identifier. While many people share the same birth date, it is a key piece of data used in identity triangulation. When combined with other common data (like ZIP code or gender), it can uniquely identify an individual with high accuracy.

Why A, C, and D are Incorrect
Job titles, work phone numbers, and time zones are generally considered business or public data rather than private PII. Because multiple people often share the same title or office phone extension, these are not typically used as unique identifiers for individuals in a private context.

Why F is Incorrect
Blood type is highly sensitive Protected Health Information (PHI) but is usually categorized under medical records rather than standard PII for general identification in project management contexts.

Exam Reference
Domain: Project Documentation and Controls (Domain 2.0)
Topic: Data Security and Privacy Compliance (PII/PHI)

Explanation

In the CompTIA Project+ PK0-005 framework, the closing phase is about administrative finalization, transitioning the product, and releasing the team. Here is the breakdown for the three correct activities.

Correct Answers
B. Recognizing project team efforts and rewarding team members
D. Revoking resource credentials from the system
F. Informing the functional manager about the release of resources

Choice B (Recognizing/Rewarding)
A formal part of the closing process is the recognition or celebration of the team's work. This helps with morale and ensures a positive transition for team members as they move to their next assignments.

Choice D (Revoking Credentials)
During administrative closure, security is a priority. This involves ensuring that project-specific access to systems, buildings, or sensitive data is removed once the work is complete.

Choice F (Informing Functional Managers)
In a matrix organization, project team members are borrowed from functional departments. Formally notifying their functional manager that the project is over allows those managers to reassign the staff to other tasks.

Incorrect Answers
A. Requesting project charter sign-off
This occurs during the Initiation phase. The charter starts the project, not ends it.

C. Working with the financial team to obtain ROI
ROI is a business realization activity that often happens months or years after project closure. The PM closes the project budget but usually does not verify long-term ROI.

E. Updating the risk register with new findings
While the risk register may be archived, updating it with new findings is part of Monitoring and Controlling during the project lifecycle.

G. Monitoring project team performance
This is an Execution and Monitoring & Controlling activity. During closure, active performance is no longer monitored; final evaluations and lessons learned are conducted instead.

OReference
CompTIA Project+ PK0-005 Domain 4.0: Project Closure
Section 4.1: "Summarize the importance of formal closing" (Includes: Lessons learned, Release of resources, Archiving of documents, and Administrative closure).
Source: CompTIA Project+ (PK0-005) Exam Objectives; PMBOK® Guide – Seventh Edition.

Explanation:

The scenario describes the team defining guidance, direction, and an approach for monitoring established procedures for developed products. This aligns with quality assurance (QA).

Project Quality Assurance focuses on:
Ensuring processes and procedures are followed
Monitoring how products are developed and produced
Ensuring the quality standards and procedures are applied during the project

QA is process-oriented, meaning it verifies that the correct procedures are used to produce quality deliverables.

Why the Other Options Are Incorrect

A. Project transition
This plan deals with handing over the project deliverables to operations or support teams, not monitoring procedures during development.

B. Project management
The project management plan is the overall master plan for the project and is broader than the specific focus on monitoring procedures.

C. Project communications
A communications plan defines how information is shared among stakeholders, not how procedures for product development are monitored.

Reference
CompTIA Project+ PK0-005 – Quality Management

Key distinction
Quality Assurance (QA) → Focuses on process monitoring and adherence to procedures
Quality Control (QC) → Focuses on testing and inspecting the final deliverables.

Explanation:

An Ishikawa diagram (also known as a Fishbone or Cause-and-Effect diagram) is specifically designed to identify the potential factors causing an effect—in this case, "poor quality of project documentation." By gathering team members to provide insights and discuss various perspectives, the project manager is facilitating a brainstorming session to categorize potential causes (such as People, Process, Environment, or Tools) to find the root of the problem.

Incorrect Answers

A. Executing the approved contingency plan
Why it's incorrect: A contingency plan is a pre-defined set of actions taken when a specific risk event occurs. While poor documentation is an issue, the team is currently in the "discovery" phase (understanding why it happened) rather than executing a pre-planned response to a triggered risk.

C. Using a Pareto chart to prioritize the different causes
Why it's incorrect: A Pareto chart is a histogram used to rank causes from most frequent to least frequent (the 80/20 rule). While it helps with prioritization, the question describes a team brainstorming insights and perspectives, which is the step taken to identify causes before they can be quantified or ranked in a chart.

D. Engaging the senior management team in regard to the issue
Why it's incorrect: While senior management may eventually need to be informed, the immediate task described is a technical team meeting to analyze the internal quality issue. Jumping to senior management before performing a root cause analysis is generally considered premature in the CompTIA project management framework.

References
CompTIA Project+ (PK0-005) Exam Objectives: Domain 1.6 – "Given a scenario, use appropriate phase-related reports/tools" (Fishbone/Ishikawa diagrams).

PMBOK Guide (6th/7th Edition): Chapter on Project Quality Management, specifically the "Manage Quality" section which details data representation techniques like Cause-and-Effect diagrams used for identifying root causes of quality defects.

Explanation:

The scenario describes a major malfunction during code implementation that caused an inoperative product condition, forcing the team to work late to restore operations. The question asks what the project manager should have generated FIRST to alleviate the impact of this issue prior to deployment. This points to proactive risk planning.

Why D is correct
A contingency plan is a pre-defined set of actions to be taken if an identified risk occurs. If the project manager had anticipated the possibility of a deployment failure (a common risk), a contingency plan (such as a rollback procedure or a rapid response team) would have been in place. This would have allowed the team to respond quickly and methodically, potentially reducing the downtime and the need to work until midnight. The contingency plan is the proactive tool to alleviate impact.

Why A is incorrect
A risk budget (or contingency reserve) is money set aside to address identified risks. While a budget might cover overtime costs, it does not provide a plan for how to restore operations. The question asks for something to alleviate the impact, which requires a plan of action, not just money.

Why B is incorrect
Risk impact is the assessment of the potential consequences of a risk. It is an analysis, not a tool to alleviate impact. The PM would have performed a risk impact analysis during planning, but that analysis alone does not alleviate anything; it just quantifies the potential damage.

Why C is incorrect
A change request is a formal proposal to modify project baselines. It is not a tool to alleviate the impact of an unforeseen issue during deployment. A change request might be submitted after the incident to adjust the plan, but it is not a proactive mitigation tool.

References
CompTIA Project+ PK0-005 Objective 2.3: Given a scenario, perform the activities required to complete a risk assessment. This objective covers developing risk responses, including contingency plans for identified risks.

Explanation:

The scenario states that before a configuration can be made to the system in development (i.e., the configuration activity cannot start until something else is complete), a specific document must be written. This document describes how the new system will interact with other systems in the organization (often called an interface control document, system integration specification, or architecture/interaction design document in project contexts).

This is a classic example of a predecessor-successor relationship where:
The predecessor task (writing/completing the document) must finish first.
Only after it finishes can the successor task (configuring the system) start.

This matches the finish-to-start (FS) dependency — the most common type in project scheduling (e.g., in Gantt charts, network diagrams, or critical path method). You cannot begin configuring the system until you know exactly how it must interact with existing systems (to avoid conflicts, ensure compatibility, comply with standards, etc.).

Why the other options are incorrect

A. Start-to-start (SS)
Both tasks can begin at the same time (or the successor starts after the predecessor has started). Here, configuration cannot start until the document is fully written — not just started — so SS does not fit.

B. Start-to-finish (SF)
The successor's finish is dependent on the predecessor's start (very rare; used in scenarios like "the night shift must finish when the day shift starts"). This does not describe the document needing to be completed first.

C. Finish-to-finish (FF)
Both tasks must finish around the same time (e.g., testing finishes when development finishes). The scenario does not require simultaneous completion; it requires the document to be done before configuration even begins.

Reference
This question tests schedule management and dependency types in CompTIA Project+ (PK0-005), specifically Exam Objective 2.4 (Given a scenario, apply schedule development and management activities and techniques — including successor/predecessor relationships: Start-to-start, Start-to-finish, Finish-to-finish, Finish-to-start). It reflects standard PMBOK/CompTIA guidance on logical dependencies (mandatory/internal in this case, as the interaction document is required for safe/accurate configuration).

Explanation:

The question asks which cloud model provides compute, storage, and networking resources on demand. That’s the definition of Infrastructure as a Service (IaaS).

Software as a Service (A):
Provides ready-to-use applications over the internet (e.g., Gmail, Salesforce). It doesn’t give direct access to infrastructure resources.

Infrastructure as a Service (B):
Offers virtualized computing resources like servers, storage, and networking. Users can build and manage their own systems on top of this infrastructure. Correct answer.

Data as a Service (C):
Focuses on delivering data on demand, not infrastructure.

Platform as a Service (D):
Provides a platform for developers to build and deploy applications (e.g., Google App Engine, Heroku). It abstracts away infrastructure but doesn’t give raw compute/storage/networking directly.

Reference:
This aligns with CompTIA Project+ PK0-005 Exam Objective 1.4 (Cloud and Virtualization Concepts). In cloud computing models:

IaaS = Infrastructure resources
PaaS = Development platform
SaaS = End-user applications