CompTIA Project+ PK0-005 (PK0-005) — Questions 901–975

The project management plan is a formal, approved document that defines how the project is executed, monitored, and controlled. The Risk Management Plan (D) and Scope Management Plan (E) are two of the subsidiary plans that must be included, as they detail processes for identifying, analyzing, and responding to risks, and for defining, validating, and controlling scope, respectively. These are mandated by the PMBOK Guide and are core components of a comprehensive project management plan.

Schedule variance (SV) = EV - PV = $45,000 - $55,000 = -$10,000 (negative, behind schedule). Cost variance (CV) = EV - AC = $45,000 - $50,000 = -$5,000 (negative, over budget).

The product backlog is the prioritized list of user stories and work items for the product. The sprint backlog is for the current sprint.

A Request for Proposal (RFP) is used to solicit proposals from sellers.

A Kanban board displays workflow stages and limits work in progress.

The project sponsor is the primary source of authority and funding for the project, and they have the broadest organizational visibility and strategic interest. Interviewing the sponsor is the most reliable method to identify key stakeholders because the sponsor can provide insights into influential individuals, departments, and external parties that may not be captured in static documents. This aligns with the PMBOK Guide's emphasis on engaging the sponsor early during project charter development.

Reassigning a developer from a non-critical task (which has float) to the critical path task is the most cost-effective way to recover schedule without additional budget or scope changes.

Finish-to-Start (FS) is the most common dependency where the successor cannot start until the predecessor finishes.

The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is the most appropriate quality tool for identifying the root cause of a delay because it systematically maps potential causes (e.g., resources, processes, environment) to the observed effect (the schedule delay). Unlike other tools that show data distribution or trends, this diagram is designed for root cause analysis by visually brainstorming and categorizing contributing factors.

Risk, Stakeholder, and Integration are three of the ten project management knowledge areas defined in the PMBOK Guide. Risk management involves identifying, analyzing, and responding to project risks; stakeholder management focuses on engaging individuals and groups affected by the project; integration management coordinates all project processes and activities. These are core knowledge areas that the PMBOK Guide explicitly lists, unlike Security or Budgeting, which are not standalone knowledge areas in the PMBOK framework.

The first step in change control is to document the change request and submit it for impact analysis.

Crashing the schedule by adding overtime directly increases the work hours available to complete critical path tasks without requiring additional resources. Since the project has no backup resources and a tight deadline, overtime is the only option that can compress the schedule by applying more effort to the existing team, thereby minimizing the schedule impact from the resignation.

Project closure includes obtaining formal acceptance, archiving documents, and releasing resources. Risk response strategies are part of execution, and creating the WBS is part of planning.

The project charter includes the project purpose, objectives, high-level scope, budget, schedule, assumptions, constraints, and the authority of the project manager.

Avoidance is the only strategy that completely eliminates the threat by changing the project plan to avoid the risk. Transfer shifts liability, mitigate reduces impact/probability, and acceptance acknowledges the risk without action.

The project charter is a document that formally authorizes the project and identifies the project manager. It provides authority to use resources.

Fast tracking involves performing critical path activities in parallel instead of sequentially to compress the schedule. Since the project is behind schedule due to underestimation of task durations, fast tracking can shorten the project timeline without increasing costs, as it does not require additional resources or overtime.

The correct actions are to assess the impact on cost and schedule and submit a change request. Ignoring or rejecting without analysis is not appropriate; adding it anyway is scope creep.

The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is a quality management tool used to identify, explore, and graphically display the potential root causes of a problem or quality defect. It helps project teams systematically analyze the relationship between an effect (the problem) and its possible causes, making it a core tool in quality planning and quality assurance.

The project charter is a high-level document that authorizes the project and provides a summary of its purpose and key elements. A high-level project description and product description are core components of the charter, as they define the project's scope and deliverables without going into execution-level detail.

Agile methodologies are designed for evolving requirements and iterative delivery.

A VPN (Virtual Private Network) is the correct choice because it creates an encrypted tunnel over the public internet between the on-premises infrastructure and the public cloud provider, ensuring secure connectivity. Technologies like IPsec or TLS-based VPNs authenticate both endpoints and encrypt all traffic, preventing eavesdropping and tampering during transit.

R-001 has the highest risk score (0.75), indicating the highest priority. Higher scores require more immediate attention.

A project is a temporary endeavor with a defined beginning and end, undertaken to create a unique product, service, or result.

A portfolio is a collection of projects, programs, and operations managed as a group to achieve strategic objectives.

The project charter is a key output of the initiation process because it formally authorizes the project and provides the project manager with the authority to apply organizational resources to project activities. It documents the business case, high-level scope, objectives, and key stakeholders, serving as the foundational document that transitions the project from concept to execution.

An issue log should include owner (responsible person) and priority (rank of importance).

The project charter is the correct document because it provides a high-level overview of the project, including the business need, key assumptions, constraints, and initial risks. This document formally authorizes the project and is created before detailed planning begins, aligning with the sponsor's request for a summary-level view.

The PERT expected duration formula is (Optimistic + 4 × Most Likely + Pessimistic) / 6. Plugging in the values: (4 + 4×6 + 12) / 6 = (4 + 24 + 12) / 6 = 40 / 6 = 6.67 days. This weighted average accounts for uncertainty by giving more weight to the most likely estimate.

Project closing includes acceptance, releasing resources, closing contracts, lessons learned, and archiving.

The schedule baseline (C) is a key component of the project management plan because it is the approved version of the project schedule that serves as a reference point against which actual progress is measured. It includes start and end dates for activities, milestones, and dependencies, and any changes to it must go through formal change control.

Planning poker is a consensus-based estimation technique where team members use cards with story point values and reveal their estimates simultaneously.

WBS should be deliverable-oriented, decomposed to manageable level, and follow 100% rule.

The project is in the planning phase and the core issue is conflicting priorities among cross-functional team members. Facilitating a team-building session directly addresses misalignment by fostering collaboration and establishing shared goals, which is a proactive leadership technique before formal planning decisions are locked in. This approach aligns with the PMBOK Guide's emphasis on team development and conflict resolution during the early stages of a project.

In the storming stage, team members may have differing opinions, leading to conflicts and power struggles as they assert themselves.

In a projectized structure, the project manager has full authority over the project and dedicated team members.

Fast-tracking involves overlapping sequential activities, which increases risk. Crashing involves adding resources to the critical path, which increases cost. Both are schedule compression techniques, but the description matches fast-tracking.

A positive NPV indicates the project is expected to generate profit, while a negative NPV suggests a loss. Therefore, Project A should be selected.

Since the risk event has occurred and the impact exceeded expectations, the project manager should update the issue log to track the actual problem and initiate any necessary corrective actions. The risk register should be updated to reflect the closure, but the immediate need is to manage the issue.

Brainstorming is a foundational technique for risk identification because it leverages the collective expertise of the project team and stakeholders to surface potential risks in a structured, creative session. It is explicitly listed in the PMBOK Guide as a key data-gathering tool for the Identify Risks process, allowing the team to generate a comprehensive list of risks without initial filtering.

Risk score = probability × impact = 0.4 × 50,000 = $20,000.

Root cause analysis is the first step in addressing performance variances. Once the causes are known, the project manager can develop an appropriate corrective action plan.

Net Present Value (NPV) is the sum of present values of incoming and outgoing cash flows over a period of time.

The Cost Performance Index (CPI) of 0.85 indicates that for every dollar spent, only $0.85 of earned value is received, meaning the project is over budget. The Schedule Performance Index (SPI) of 1.05 indicates that the project is progressing at 105% of the planned rate, meaning it is ahead of schedule. Therefore, the project is over budget and ahead of schedule, making option D correct.

A risk is an uncertain event that may happen in the future, while an issue is a current problem that has already occurred and needs resolution.

Jira (with add-ons) offers Gantt charts and Kanban boards. Monday.com also provides both views. Trello is primarily Kanban, Asana mainly task lists, Smartsheet is spreadsheet-based.

Equipment rental is a direct cost because it is a specific expense that can be directly attributed to the project. It is incurred solely for the project's benefit and can be easily traced to the project's budget without allocation.

CV = EV - AC = $80,000 - $90,000 = -$10,000. Negative CV means over budget.

The change log records all changes and their status, helping manage baseline changes.

The exhibit shows the web server is in a 'LISTENING' state on port 80, with established connections (ESTABLISHED) to client IPs. This indicates the server process is running, the TCP handshake completed successfully, and it is actively handling HTTP requests. Option D is correct because a listening socket with established sessions confirms operational status.

Performance reports and change requests are typical outputs of monitoring and controlling. The project charter is an output of initiating, and the risk register is an output of planning.

Waterfall is sequential, Agile is iterative, and Scrum uses sprints and stand-ups. Common confusions include mixing characteristics with other methodologies like Kanban.

A request for quotation (RFQ) is used to obtain a price for a specific item.

The change log is the official repository for recording all approved change requests, including their details and impacts. Updating it first ensures that the change is formally documented and communicated to stakeholders before any baselines or plans are modified. This aligns with the integrated change control process, where the change log serves as the primary communication tool for change status.

Schedule variance (SV) = EV - PV = $50,000 - $60,000 = -$10,000. A negative SV means the project is behind schedule.

A run of seven or more points on one side of the mean is a rule for identifying special cause variation, even if within control limits.

Integrated change control evaluates change requests against constraints and manages approval.

A program is a group of related projects managed together for benefits, and a portfolio is a collection of projects and programs aligned with strategic objectives.

The Waterfall model (Option C) is correct because it follows a strictly sequential, phase-by-phase progression: requirements, design, development, testing, and deployment, with no overlap or iteration. This linear approach is characteristic of the Waterfall life cycle, where each phase must be completed before the next begins, as described in the PMBOK Guide for predictive life cycles.

The backup server is on the same network segment as production traffic, causing congestion during peak hours. Backup timeouts indicate that the backup traffic is competing with production traffic for bandwidth, leading to packet loss or delays. Isolating backup traffic on a separate VLAN reduces network congestion by logically separating the traffic, ensuring dedicated bandwidth for backups and preventing interference with production operations.

The project charter is created during project initiation to formally authorize the project and provide the project manager with the authority to apply organizational resources. It documents the business case, high-level scope, and key stakeholders, serving as the foundational document for all subsequent planning.

The root cause of the budget overrun and schedule delay is scope creep and unclear requirements, which have demoralized the team and led to inefficient work. By conducting a scope review with the sponsor and stakeholders to prioritize remaining features and freeze requirements, you directly address the source of rework and wasted effort. This action stabilizes the project baseline, allowing the team to focus on delivering the highest-value work within the remaining budget and timeline, and it prevents further uncontrolled changes that would worsen the CPI and SPI.

Schedule compression techniques like crashing (adding resources) or fast-tracking (performing tasks in parallel) are standard methods to shorten a project's duration without changing scope. The project manager should evaluate these to determine if the one-month acceleration is technically feasible given the project's constraints.

CPI > 1 means under budget; SPI < 1 means behind schedule. Over budget would be CPI < 1; ahead of schedule would be SPI > 1.

In project management status reporting, a red indicator typically signifies that the project is off track with critical issues, meaning the project is significantly behind schedule, over budget, or facing major risks that require immediate attention. This aligns with the standard red-yellow-green (RAG) status system used in tools like Microsoft Project or Jira, where red indicates a severe deviation from the baseline plan that cannot be resolved without intervention.

The project management plan is the comprehensive document that includes all subsidiary management plans.

Jira is widely used for agile project management, and Trello supports Kanban boards, a common agile tool. Microsoft Project is more traditional. Smartsheet and Monday.com are not specifically agile-only.

Procurement documents include SOW (Statement of Work) and RFP (Request for Proposal). The project charter and WBS are not procurement-specific; the risk register is a risk document.

The RACI matrix (Responsible, Accountable, Consulted, Informed) is the correct document because it explicitly defines stakeholder roles and responsibilities in a project and is presented as a matrix format. This aligns with the PMBOK Guide and the PK0-005 exam objectives for Tools and Documentation, where the RACI matrix is the standard tool for clarifying participation levels across project tasks.