Pass the CompTIA Project+ PK0-005 Questions and answers with ExamsMirror

The critical path of the project is the longest sequence of tasks that must be completed on time for the project to finish on schedule. It determines the shortest possible duration of the project and shows the tasks that have no slack or float. Any delay in the critical path tasks will affect the project completion date. To find the critical path, we need to calculate the earliest start (ES), earliest finish (EF), latest start (LS), latest finish (LF), and slack (S) for each task. We can use the table and the network diagram given in the question to do this. The formula for calculating the slack is S = LF - EF or S = LS - ES. A task with zero slack is on the critical path. The calculations are as follows:

Task | Duration | ES | EF | LS | LF | S A | 10 | 0 | 10 | 0 | 10 | 0 B | 15 | 10 | 25 | 10 | 25 | 0 C | 10 | 10 | 20 | 15 | 25 | 5 D | 20 | 25 | 45 | 25 | 45 | 0 E | 10 | 25 | 35 | 35 | 45 | 10 F | 15 | 20 | 35 | 30 | 45 | 10 G | 5 | 45 | 50 | 45 | 50 | 0 H | 10 | 35 | 45 | 40 | 50 | 5 I | 20 | 35 | 55 | 30 | 50 | -5 J | 5 | 50 | 55 | 50 | 55 | 0

Based on the table, we can see that the tasks with zero slack are A, B, D, G, and J. Therefore, the critical path is A-B-D-G-J, which has a total duration of 55 days. The other options are not the correct critical paths, as they either include tasks with positive slack (such as C, E, F, and H) or have a longer duration than 55 days (such as A-C-F-I-J).

Because the team needs validation every time a new change is integrated, the priority is repeatability, speed, and consistent coverage—this is where automated testing is most effective. CompTIA Project+ explicitly calls out testing approaches as Automated vs. Manual within operational change-control and release practices, reinforcing that automation is a key control to support frequent integration and deployment.

While regression testing is the type of testing that checks whether new changes broke existing functionality, doing it manually every integration is often slow and expensive. Automation enables the regression suite (and other checks) to run quickly in CI/CD pipelines, improving coverage and reducing per-run effort, which matches the question’s “timely and cost-effective” requirement. CompTIA also lists regression testing among testing cycles, but the scenario’s emphasis is on executing that validation repeatedly with efficiency—best achieved by automation.

Sanity testing is usually a quick, narrow check after a change; it does not provide the broad “good coverage” implied here. Therefore, establishing automated testing is the best answer to ensure consistent, repeatable validation whenever changes are integrated.

A wiki is the best tool to record retrospective results for a distributed/virtual team because it provides a shared, persistent, easily editable knowledge base where outcomes can be documented and revisited. Retrospectives produce actionable items such as what went well, what didn’t, root causes/themes (e.g., production issues), and improvement experiments with owners and due dates. A wiki supports this by enabling structured pages, version history, links to incident records, and ongoing updates—helping the team track whether morale and operational stability improve over time. CompTIA Project+ includes meeting management and documentation practices (agendas, notes, action items) and recognizes collaboration tools used to capture and share project knowledge.

A presentation is typically one-way and not ideal for ongoing collaborative updates. Chat is transient and hard to curate as a long-term record; key decisions and actions get buried. Polling is useful for quick sentiment checks (which can help measure morale), but it doesn’t serve as the primary system to document discussion, decisions, and actions from the retrospective.

Therefore, to record retrospective results clearly and durably for a virtual team, the PM should use a wiki.

This directive acknowledges local emergency policies/constraints. Hurricane season is a predictable period of elevated operational risk for a utility company, where system stability and rapid incident response are critical. By prohibiting operating-system-impacting projects during that season, the organization is recognizing that emergency preparedness and service continuity take priority, and that change activity increases outage risk when the environment is already volatile.

“National environments” (B) would relate to country-level laws, geopolitical factors, or national regulatory contexts; the directive is tied to a seasonal, location-driven emergency risk pattern rather than national policy. “Company brand value” (A) is indirectly affected, but it’s not what the directive is formally acknowledging. “Standard operating procedures” (C) is tempting because a directive could become an SOP, but the reason and driver is the emergency operating context—hurricane season—so the best match is local emergency policies.

From a Project+ perspective, this is an example of an environmental/operational constraint that should be considered in planning (schedule constraints, blackout windows, change freezes) and reflected in the project schedule and risk planning.

An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

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 client provided a statement of work (SOW) to the project manager and suggested that the project manager and team just need to execute the plan. A SOW is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. A SOW typically includes information such as purpose, scope of work, location of work, period of performance, deliverables schedule, applicable standards, acceptance criteria, special requirements, and payment schedule. A SOW can help to establish a common understanding and agreement between the client and the service provider on what needs to be done and how it will be done.

Meeting with the team to emphasize the importance of following change management procedures is the best approach to prevent future unauthorized changes. CompTIA Project+ highlights the importance of adhering to formal change control processes to ensure project alignment and accountability.

Meeting minutes should be prepared to ensure team members who are absent remain informed about assignments. Meeting minutes document what was discussed, decisions made, and assignments given during a meeting, providing a record of the team's progress and ensuring absent members are up-to-date. References: CompTIA Project+ Study Guide Section 4.2.2

The project manager should prepare meeting minutes to ensure team members who are absent remain informed about assignments. Meeting minutes are a written record of what was discussed and decided in a meeting. They usually include information such as attendees, agenda items, action items, decisions made, issues raised, and deadlines assigned. Meeting minutes can help to communicate important information to team members who could not attend the meeting and provide a reference for future follow-up.

A QA plan, or quality assurance plan, is a document that specifies the quality standards, practices, resources, specifications, and activities for a product, service, project, or contract. A QA plan helps to ensure that the products produced during the project meet the highest quality standards and that the project objectives and customer requirements are met. A QA plan also helps to communicate the quality expectations and responsibilities to the team members and other stakeholders, and to monitor and control the quality performance throughout the project. Developing a QA plan is one of the key tasks of the project manager, as it is part of the project scope management and project quality management processes123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 3: Project Scope Management, p. 97; Chapter 5: Project Quality Management, p. 169; 6 Key Steps to Creating A Quality Assurance Plan - The QA Lead; What is Quality Planning? Quality Control Plans | ASQ; What Is A Quality Assurance Plan? - Sofeast