CompTIA Project+ PK0-005 (PK0-005) — Questions 601–675

CPI < 1 indicates over budget; SPI < 1 indicates behind schedule.

The standard format is 'As a [role], I want [feature], so that [benefit]'. The 'so that' clause captures the benefit.

In RACI, 'Responsible' means the person who does the work to complete the task. 'Accountable' is the person who signs off.

After a change is approved by the change control board, the project manager must update the project management plan and the scope baseline to reflect the new scope.

In a matrix organization, the PM must negotiate with the functional manager for resources.

The project schedule is the document that directly reflects the sequence, dependencies, and timing of tasks, including the critical path. When a delay causes the critical path to change, the schedule must be updated first to capture the new start and finish dates, float values, and path dependencies. This ensures the project manager has an accurate baseline for assessing impacts and communicating changes.

A non-critical task has float, but if it is a predecessor to a critical task, its delay can consume float and eventually impact the critical path.

Schedule compression must focus on the critical path to reduce project duration. Tasks with zero float are on the critical path, so crashing them (adding resources or overtime) can directly shorten the schedule. The task with three days of float is not on the critical path, so compressing it would not reduce overall project duration.

Planning poker is a consensus-based estimation technique where team members discuss and vote on story point estimates to reach agreement.

The first step is to perform an impact analysis to assess the effects of the change before submission to the CCB.

A program is a group of related projects managed in a coordinated way to obtain benefits not available from managing them individually.

The correct matches are: Scope Management with its definition about including all work, Time Management with timely completion, and Cost Management with budgeting and cost control. Common confusions include swapping definitions between these knowledge areas, especially because they are closely related.

Stakeholders with high power and low interest should be kept satisfied. They need sufficient information to ensure satisfaction but not overwhelmed with details.

When a change is approved, the project baselines (scope, schedule, cost) and the project management plan are updated. The scope baseline and schedule baseline are part of the plan. The change log is also updated, but it is not part of the project management plan itself.

Approved changes require updating the project management plan and baselines (cost, schedule).

CPI = EV/AC = 50000/60000 = 0.83. A CPI less than 1 indicates the project is over budget. The project is spending more than planned for the work performed.

The WBS should be decomposed to work packages, and each element should represent a deliverable, not an activity.

CPI = EV/AC = $40,000/$45,000 = 0.89.

Predictive/waterfall is suitable for stable requirements and low change, as it follows a sequential plan-driven approach.

A Gantt chart is the correct tool because it visually displays task start and end dates along a timeline, and it can explicitly show dependencies between tasks using arrows or linking lines. This makes it ideal for project scheduling and tracking progress against planned dates.

The stakeholder engagement plan is the correct document because it specifically outlines strategies and actions to manage stakeholder expectations, interests, and influence throughout the project lifecycle. Unlike a communication plan, which focuses on the logistics of information distribution, the engagement plan addresses how to actively involve stakeholders based on their power, interest, and influence levels. This aligns with PMI's guidance in the PMBOK Guide for the Plan Stakeholder Engagement process.

Predictive (waterfall) methodology works best when requirements are clear and stable. It uses sequential phases and fixed scope.

The project manager should first coach the product owner on agile principles, specifically the impact of changing requirements during sprints. In agile, the product owner is responsible for prioritizing the backlog, but changes should not be introduced mid-sprint as they disrupt the team's commitment to sprint goals. By leveraging the good relationship, the project manager can educate the product owner on the importance of sprint stability, which directly addresses the root cause without escalating or overcomplicating the process.

A positive NPV indicates a profitable project; a negative NPV indicates a loss. Select Project A.

In a RACI matrix, 'A' stands for Accountable, meaning the person who is ultimately answerable for the task. There should be only one 'A' per task.

A milestone chart is specifically designed to show key events or milestones, not detailed tasks or dependencies.

After approval, the project manager must implement the change, which includes updating all relevant baselines (scope, schedule, cost) and communicating the change to stakeholders.

Stakeholders with high power but low interest need to be kept satisfied to maintain their support without overwhelming them with information.

After approval, the change must be implemented and project baselines (scope, schedule, cost) updated to reflect the approved change.

The planning phase involves creating detailed plans and defining scope, schedule, cost baselines.

Jira and Trello are both popular Agile project management tools that support Scrum and Kanban methodologies.

The change log is the first document to update because it serves as the official record of all change requests, including their status and approval decisions. Once the CCB approves a change, the project manager must log the approval in the change log before updating other documents like the schedule or scope statement, as those updates depend on the change being formally recorded.

The risk management plan is the correct document to create or update when high uncertainty could affect the schedule because it defines how risks will be identified, analyzed, responded to, and monitored throughout the project. This plan includes the risk register and risk response strategies, which directly address schedule uncertainties by establishing a structured approach to handling potential impacts. In the PK0-005 context, the risk management plan is a key component of the project management plan that proactively manages uncertainty rather than reacting after the fact.

NPV = Present value of inflows - Initial investment. PV of inflows = $30,000 * 3.791 = $113,730. NPV = $113,730 - $100,000 = $13,730.

The estimate at completion (EAC) when cost performance is expected to continue is calculated using the formula EAC = BAC / CPI, where CPI = EV / AC. Here, CPI = $100,000 / $120,000 = 0.8333, so EAC = $200,000 / 0.8333 = $240,000. This formula assumes the same cost efficiency will persist for the remainder of the project.

Activities on the critical path have zero float by definition.

The schedule baseline includes the approved start and end dates, milestones, and activity dependencies. It is not updated with changes until approved.

The scenario describes the project manager updating the issue log and meeting with the team to evaluate alternatives for a delayed deliverable. This is the core of the 'Direct and Manage Project Work' process, which involves executing the project management plan, performing activities to produce deliverables, and managing issues as they arise. The PM is actively directing the work by addressing the issue and exploring options, not yet controlling or changing baselines.

The question explicitly requires the provider to support data sovereignty, which mandates that data must be stored and processed within specific geographic boundaries. The SLA clause on data residency and location clauses (Option D) directly addresses this by defining where data centers are located and whether data can be moved across borders. Without this clause, the provider could store data in jurisdictions violating legal or regulatory requirements, making it the most critical clause to review.

EMV = Probability × Impact = 0.20 × $50,000 = $10,000. EMV is used to quantify risks in monetary terms.

Based on the change request log, CR-001 adds 2 weeks to the schedule, CR-002 is a low-priority enhancement with no schedule impact, CR-003 reduces the schedule by 1 week to offset delays from other changes, and CR-004 is an urgent but high-risk change that could cause additional delays. To maintain the project schedule, the project manager should approve CR-003 because it directly reduces the schedule and helps compensate for delays caused by approved changes.

The business case is a key input to the project charter because it provides the justification for the project, including high-level risks that could affect the project's viability. The project manager uses the business case to identify these risks early, ensuring they are documented in the charter before detailed planning begins.

The Cost Performance Index (CPI) is the correct KPI because it directly measures cost efficiency by comparing the earned value (EV) to the actual cost (AC). A CPI greater than 1 indicates the project is under budget, while a CPI less than 1 indicates over budget. This aligns with the question's focus on how efficiently the budget is being used during the execution phase.

The cost variance (CV) is calculated as earned value (EV) minus actual cost (AC). From the exhibit, EV = $25,000 and AC = $40,000, so CV = $25,000 - $40,000 = -$15,000. A negative CV indicates the project is over budget, meaning costs have exceeded the value of work performed.

The exhibit shows a risk response plan with a configured limit of two active risk responses per category. However, the risk log displays three risks in one category, indicating that the limit is not being enforced correctly. This mismatch between the planned configuration and the actual tracking is the direct issue, making option D correct.

Common risk register fields include risk ID, description, owner, probability, impact, risk score, response strategy, residual risk, and trigger.

The change management plan is the correct document because it specifically defines the process for submitting, reviewing, approving, and tracking change requests. This plan outlines the roles, responsibilities, and procedures for managing changes to project baselines, ensuring that all modifications are controlled and documented.

The stakeholder's perception of business value may differ from the approved scope. The project manager should review the business case with the stakeholder to clarify the agreed-upon objectives, success criteria, and expected value, thereby realigning expectations without scope creep. This approach maintains stakeholder engagement and ensures the project remains within its defined boundaries.

The project manager's role during the initiation phase is to align stakeholders on project objectives. Facilitating a meeting to prioritize requirements and reach consensus directly addresses the disagreement between maximizing functionality and minimizing cost, ensuring the project charter reflects agreed-upon goals before proceeding.

Gold plating is adding extra features beyond requirements. It can be well-intentioned but adds unnecessary scope.

The Gantt chart is the correct tool because it visually displays project tasks, their dependencies, durations, and resource assignments along a timeline. It explicitly shows the critical path (the longest sequence of dependent tasks) and allows the project manager to adjust schedules dynamically when tasks are delayed, making it ideal for schedule management and impact analysis.

CPI < 1 means over budget; SPI > 1 means ahead of schedule.

The project charter is a high-level document that authorizes the project and provides the project manager with the authority to apply organizational resources. The business need (option B) is a core component because it justifies why the project is being undertaken, linking it to organizational strategy. High-level risks (option E) are also included to identify potential uncertainties at the outset, without requiring detailed analysis, which aligns with the charter's purpose of providing a broad overview.

The forcing technique (also known as 'competing') involves the project manager imposing a decision unilaterally without input or discussion from the conflicting parties. This approach is appropriate when a quick resolution is needed to avoid project delays, as the question states. It does not seek consensus or compromise but rather asserts authority to move forward.

Mandatory dependencies, also known as hard logic, are inherent in the nature of the work and cannot be changed. For example, you must build the foundation before erecting walls.

Predictive (waterfall) is best when requirements are stable, the team is experienced, and the work is well understood. Agile is for evolving requirements; hybrid would be overkill; iterative is not as structured as predictive for stable requirements.

Schedule development follows: define activities, sequence, estimate resources, estimate durations, then develop the schedule.

A trigger is an event or condition that indicates that a risk is about to occur or has occurred. It serves as a warning sign that the risk response plan should be activated.

The risk register is the formal project document used to record identified risks, their analysis, planned responses, and status throughout the project lifecycle. In the PK0-005 context, it is the definitive tool for tracking risks from identification through closure, ensuring all risks are managed systematically.

Firewall rules are essential for controlling inbound and outbound traffic to the web server, protecting it from unauthorized access and attacks. A TLS certificate enables HTTPS encryption, ensuring data confidentiality and integrity between clients and the server. Both are critical security measures that should be included in the project plan for a new web server deployment.

The change control board (CCB) has approved the change, making it an authorized modification. The project manager must now update the project management plan and baseline to formally incorporate the approved change, ensuring the schedule and budget reflect the new scope. The sponsor's concern is noted but does not override the CCB's decision; the PM should address the concern through communication and reporting, not by halting the process.

Transfer involves shifting the impact of a risk to a third party, such as through insurance.

Residual risk is the risk remaining after implementing the response. The new probability is 0.2, impact remains $50,000, so residual risk score = 0.2 * 50,000 = 10,000. The initial risk score was 30,000, but the question asks for the residual risk score after the response.

Predictive/waterfall works well when requirements are clear and scope is fixed from the start. Agile is for changing requirements; hybrid is a mix; Kanban is for flow.

Control charts (with UCL/LCL) distinguish between special and common cause variation. Run charts can also show trends but may not have control limits. Cause-and-effect diagrams identify root causes, Pareto charts prioritize, histograms show distribution but not special causes.

The change log is updated to record the approval, implementation details, and closure of the change request, providing an audit trail. The project baseline (e.g., scope, schedule, cost) must be updated to reflect the approved change, ensuring all future work and variance analysis are measured against the revised baseline.

The typical project life cycle phases are initiating, planning, executing, monitoring and controlling, and closing. Executing follows planning.

A negative NPV means the project's costs exceed its benefits, indicating it is not financially viable.

Lessons learned documents are forward-looking artifacts that capture actionable insights to improve future project execution. Recommendations for future projects are a standard component, as they translate past experiences into specific guidance for planning, risk management, and process adjustments in subsequent initiatives.