CompTIA Project+ PK0-005 (PK0-005) — Questions 151–225

Schedule variance (SV) and cost performance index (CPI) are both standard key performance indicators (KPIs) defined in earned value management (EVM). SV measures the difference between earned value and planned value, indicating whether the project is ahead or behind schedule. CPI measures cost efficiency by comparing earned value to actual cost, directly reflecting project budget performance.

When a change request is approved and the project baseline is updated, the risk register must also be updated because the change may introduce new risks, alter the probability or impact of existing risks, or render some risks obsolete. The risk register is the formal document that captures identified risks, their analysis, and response plans, so any baseline change directly affects the risk profile of the project.

Norming is when the team starts to work together more cohesively and establish norms.

Gold plating is when the project team adds extra features beyond the requirements without authorization, increasing scope without corresponding value.

Product backlog, sprint backlog, and burndown chart are agile artefacts. The RACI matrix is a responsibility assignment tool, and the risk register is a traditional project management document.

The project charter is the document that formally authorizes the project and gives the project manager authority.

Requirements documentation is a key output of the scope planning process because it formally captures the stakeholder needs and expectations that must be met by the project. This documentation serves as the foundation for defining the project scope and is used to validate that deliverables align with business objectives.

The meeting at the end of a project phase is a retrospective, specifically designed to capture what went well and what could be improved. The formal document produced from this meeting is the lessons learned document, which records insights and recommendations for future phases or projects. This aligns with the PMI's definition of lessons learned as a key output of the project's monitoring and controlling processes.

Inputs to develop the project management plan include the project charter and outputs from other planning processes (subsidiary plans and baselines). Work performance data, change requests, and approved changes are inputs to monitoring and controlling processes.

The schedule baseline is a key component of the project management plan because it defines the approved project schedule, including start and end dates for activities, milestones, and dependencies. It serves as the reference point against which actual schedule performance is measured and controlled throughout the project lifecycle.

A flowchart is the correct tool because it is specifically designed to visually represent the sequence of tasks, decision points, and branching logic within a business process. Unlike other charts, flowcharts use standardized symbols (e.g., rectangles for processes, diamonds for decisions) to map out the flow of activities, making them ideal for process mapping and workflow analysis.

The project charter is created during the Initiating phase, which also includes stakeholder identification.

The project manager must submit the change request to the change control board (CCB) for evaluation and approval, as it exceeds typical thresholds. Approving or rejecting without CCB is not allowed; updating the plan occurs only after approval.

CPI > 1 means under budget, SPI < 1 means behind schedule.

The project management plan is the formal, approved document that defines how the project is executed, monitored, and controlled. The schedule baseline (B), cost baseline (D), and scope baseline (E) are three of the key baselines that collectively form the performance measurement baseline (PMB) against which project performance is measured. These baselines are formally approved and can only be changed through a formal change control process.

The project charter is the document that formally authorizes the project and gives the project manager authority.

CPI = EV/AC = 200,000/250,000 = 0.8. A CPI less than 1 indicates the project is over budget.

The stakeholder register is the correct tool for capturing key stakeholders who influence project success because it documents their identification, assessment, and classification. The project manager uses this register during stakeholder analysis to record names, roles, expectations, and influence levels, which is essential for developing the project charter.

The critical path is the longest sequence of dependent tasks in a project schedule, determining the shortest possible project duration. For this project, the critical path is A→C→D, with durations summing to 22 days. Any delay on this path directly extends the project completion date.

Releasing project resources is a key activity in the project closure phase because it formally ends the team members' obligations to the project, allowing them to be reassigned to other initiatives. This step ensures that resource allocation is properly documented and that any contractual or administrative obligations are fulfilled, preventing ongoing costs or conflicts.

Parametric estimating (B) uses historical data and statistical relationships between variables (e.g., cost per square meter, hours per unit) to calculate activity durations. It is a standard technique in project schedule development because it provides objective, data-driven estimates based on measurable parameters.

The team is in the forming stage, characterized by politeness and uncertainty.

EMV = Probability × Impact = 0.20 × $50,000 = $10,000.

An active-active data center arrangement is most appropriate for high availability and disaster recovery because it distributes application traffic across multiple geographically dispersed data centers, all of which are actively serving requests. If one site fails, traffic is seamlessly redirected to the remaining active sites, ensuring near-zero downtime and no data loss. This configuration supports automatic failover and load balancing, which are critical for meeting stringent recovery time objectives (RTO) and recovery point objectives (RPO).

The communication management plan defines how project information will be distributed to stakeholders. Including stakeholder communication requirements ensures that each stakeholder receives the right information in the right format and at the right frequency, directly addressing the need for timely information.

According to the integrated change control process, the first step is to evaluate the impact of the change on the triple constraint (scope, schedule, cost) before presenting it to the change control board.

Finish-to-Start (FS) is the most common dependency, where the successor activity cannot start until the predecessor activity has finished.

The standard project life cycle phases are Initiating, Planning, Executing, Monitoring and Controlling, and Closing.

High power, high interest stakeholders are in the 'Manage Closely' quadrant and need the most attention.

Closure activities include lessons learned, obtaining formal acceptance, and archiving project documents.

The critical path is A-C-D: 2 + 4 + 2 = 8 days, which corresponds to option B. Path A-B-D is 2+3+2=7 days, which is option C. Options A (10) and D (9) are not possible given the durations.

According to the power/interest grid, stakeholders with high power and low interest should be kept satisfied to maintain their support.

The backup software configuration specifies a filesystem label or UUID for the backup volume, but the actual volume has a different label or UUID. This mismatch prevents the backup software from locating the intended target volume, causing the job to fail. This is a common configuration issue that would be evident from examining the configuration files and the volume properties.

The project charter is the formal document that authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is issued by the project sponsor or initiator and formally assigns the project manager, establishing their role and responsibilities from the outset.

Number of sprints = total story points / velocity = 120 / 30 = 4 sprints.

Phase C is correct because in a typical project schedule, the phase with the most total float is the one that can be delayed the longest without affecting the project's overall completion date. Total float is calculated as the difference between the late start and early start (or late finish and early finish) of an activity. Phase C has the highest total float value, indicating it has the greatest scheduling flexibility.

Risk register includes risk description, probability and impact assessment, and response plan.

Analogous estimation uses historical data from similar projects to estimate costs or durations.

Fast-tracking involves overlapping sequential activities, which increases risk.

Start-to-start (SS) means the successor activity can start when the predecessor starts. Activity E starts when Activity C starts, so it's SS.

The Control Costs process is responsible for monitoring cost performance, analyzing variances from the cost baseline, and implementing corrective actions. Since the project manager observes actual costs exceeding planned costs, they must use Control Costs to perform earned value management (EVM) calculations such as cost variance (CV) and cost performance index (CPI) to quantify and analyze the deviation.

The firmware is a prerequisite for the new hardware to function correctly; proceeding without it risks incompatibility, instability, or hardware failure. Updating the firmware immediately and adjusting the schedule is the only viable path that ensures the migration is technically sound. The project schedule is tight, but the firmware update is a necessary step that cannot be skipped or deferred without jeopardizing the migration's success.

The risk is specifically a single point of failure in the fiber path between data centers. Installing a second, diverse fiber path eliminates this single point of failure, ensuring synchronous replication can continue even if one cable is cut. This directly addresses the sponsor's concern about go-live delays due to cable outages, without changing the replication mode or adding unnecessary hardware.

Bottom-up estimating is best suited for estimating the cost of each work package because it involves decomposing the work package into its lowest-level components (activities or tasks) and estimating each one individually. This provides a high level of accuracy by aggregating detailed estimates from the team members who will perform the work, making it ideal for project planning when detailed scope definition is available.

The typical phases are initiating, planning, executing, monitoring and controlling, and closing. 'Testing' is not a phase; it is an activity within executing.

Since planning is complete, but the project hasn't started execution, the project manager should assess the impact and, if necessary, submit a change request to formally add the requirement through the change control process.

Purchasing insurance transfers the financial risk of the supplier's bankruptcy to the insurance company. This is a classic example of the Transfer risk response strategy, where the impact of the risk is shifted to a third party, not eliminated or reduced.

Jira supports product backlog (epics, stories, tasks) and sprint backlog (selected items for current sprint). Velocity is a metric, not an artefact; burndown chart is a visualization; stakeholder register is not typically in Jira.

The project scope statement defines the project's deliverables and the work required to create them, serving as the baseline for verifying that all objectives have been met during project closure. It includes acceptance criteria for each deliverable, which the project manager uses to confirm completion against the agreed-upon scope. This document is the authoritative reference for scope verification, ensuring no scope creep has occurred and all deliverables satisfy stakeholder requirements.

Network latency is a key consideration for SAN performance because SANs rely on low-latency, high-speed block-level storage protocols such as Fibre Channel (FC) or iSCSI. High latency can cause significant delays in I/O operations, directly impacting throughput and application responsiveness, especially in environments with synchronous replication or high transaction rates.

CPI = EV/AC = 90,000/100,000 = 0.9. EAC = BAC/CPI = 200,000/0.9 = $222,222.

A technical constraint is a limitation or condition that is imposed by technology choices or requirements. In this case, the customer mandates a specific software platform, which is a technical constraint.

Negotiating priorities with functional managers, escalating unresolved conflicts, and using resource leveling help resolve resource conflicts in a matrix structure.

The project manager must first submit a formal change request to the change control board (CCB) because adding a new feature after the budget has been approved constitutes a change to the project scope, schedule, and cost. This follows the formal change control process defined in the project management plan, ensuring that all changes are evaluated for impact, approved, and documented before implementation. Without CCB approval, updating the plan or proceeding with the feature would violate the project’s baseline and governance procedures.

Evaluating a change involves analyzing its impact on the triple constraint, determining if it adds value, and assessing risks. Updating baselines and rejecting without analysis come later or are not part of evaluation.

Velocity is the average story points completed per sprint, used for forecasting.

An agile approach with iterative cycles is characteristic of an iterative or adaptive life cycle, where scope is refined through repeated cycles.

A version control system (VCS) like Git enforces code review workflows through pull requests or merge requests, ensuring that changes are reviewed and approved before integration into the main branch. This directly supports the project manager's requirement for a controlled integration process, as VCS tracks every change and requires explicit approval via branch protection rules or merge checks.

It aligns with the project management principle of first attempting to recover the schedule using techniques like crashing (adding resources) or fast-tracking (performing tasks in parallel) before accepting a delay. Since the project has contingency reserves, you can potentially expedite the correct switch delivery or re-sequence tasks to absorb the three-week delay, preserving the original deadline. Ordering the correct switches immediately is necessary, but you must first evaluate if schedule compression can offset the impact, making D the most proactive and effective response.

Risk score is calculated as probability × impact. Here, 0.3 × 4 = 1.2.

Power supply redundancy ensures that if one unit fails, the other can sustain the load without downtime. In a data center upgrade, redundant power supplies (often N+1 or 2N configuration) are critical to maintain uptime for servers and network gear. This directly supports high availability for the project's critical systems.

The project charter is a foundational document that formally authorizes a project, assigns the project manager, and provides a high-level summary of objectives, scope, and key stakeholders. It is one of the three common types of project management documentation, alongside the risk register and scope statement, as defined in the PMBOK Guide and tested in the PK0-005 exam.

The project charter is created and approved in the Initiating process group.

The project charter is created in the initiating phase to authorize the project and define high-level objectives.

The stakeholder management plan defines how stakeholders will be engaged and how decisions will be obtained from them, including the steering committee. By updating this plan, the project manager can establish clear escalation paths, decision-making authority levels, and meeting cadences to ensure timely governance. This directly addresses the lack of timely decisions by formalizing the engagement and decision process.

Closing activities include obtaining formal acceptance, releasing resources, and archiving project documents.

The deployment failure was specifically a database migration issue, as indicated by the exhibit. The project manager should have the DBA manually apply the database migration to ensure the schema changes are correctly and safely executed, addressing the root cause of the failure rather than just rolling back.