CompTIA Project+ PK0-005 (PK0-005) — Questions 526–600

The scope baseline is a component of the project management plan because it formally defines the project's scope, deliverables, and acceptance criteria. It consists of the scope statement, Work Breakdown Structure (WBS), and WBS dictionary, which together establish the foundation for scope control and validation throughout the project.

The Gantt chart is the correct tool because it visually represents a project schedule with horizontal bars plotted against a timeline, where each bar corresponds to a task, and it can display dependencies (via arrows or linking lines) and milestones (as diamond symbols). This aligns directly with the description in the question, making it the standard choice for schedule visualization in project management.

A CPI of 0.8 means the project is earning only $0.80 for every $1.00 spent, indicating cost overrun (over budget). An SPI of 1.1 means the project is earning $1.10 for every $1.00 of planned work, indicating progress ahead of schedule. Therefore, the project is over budget and ahead of schedule, making option B correct.

The closing phase involves formal acceptance of deliverables, lessons learned, releasing resources, and archiving documents.

The critical path is the longest path through the network diagram, determining the minimum project duration. By summing the durations along each path, Path A-B-E-F totals 3+5+2+2=12 days, which is longer than the other paths (A-C-F: 3+4+2=9 days; A-D-F: 3+6+2=11 days). Therefore, the total duration of the critical path is 12 days, making option C correct.

The critical path method (CPM) uses network diagrams to show activity sequences and dependencies.

A Kanban board uses columns to represent workflow stages, helping to visualize work in progress.

The WBS decomposes the total project scope into smaller, more manageable components called work packages. This hierarchical decomposition ensures that all deliverables and work required to complete the project are identified and organized, which is the primary purpose of the WBS in project planning.

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

In a fixed-price contract, the seller bears the risk of cost overruns because the price is set regardless of actual costs.

Formal acceptance of deliverables is a key activity in the Closing phase, where the customer or sponsor formally accepts the final deliverables.

A PERT (Program Evaluation and Review Technique) chart is a project scheduling tool that uses a network diagram to represent tasks and their dependencies, with weighted time estimates (optimistic, pessimistic, most likely) to calculate expected durations. It is commonly used for scheduling complex projects where task time uncertainty is high, enabling critical path analysis.

The correct answer is D because any change that impacts scope, resources, or timeline must go through the formal change control process as defined in the project management plan. This ensures that all changes are evaluated for impact, approved by the change control board (CCB), and properly documented before implementation. Skipping this process introduces uncontrolled scope creep and risks project failure.

In a matrix structure, resources are shared between functional managers and project managers. A balanced matrix gives the project manager moderate authority, while weak matrix gives more authority to the functional manager, and strong matrix gives more to the project manager.

Option D is correct because the project manager should facilitate a collaborative discussion to evaluate the technical merits of each approach, enabling the team to reach consensus. This aligns with conflict resolution best practices in project management, leveraging the team's expertise to find the optimal solution without imposing a decision that could undermine buy-in or quality. By addressing the disagreement directly, the PM prevents schedule delays while maintaining team cohesion and technical integrity.

The change control board (CCB) reviews and approves change requests.

The Work Breakdown Structure (WBS) is a key planning document that decomposes the project scope into manageable work packages. It is created during the planning process group to define and organize the total work required, serving as a foundation for cost estimation, scheduling, and resource allocation.

A CPI of 1.2 means the project is earning $1.20 for every $1.00 spent, indicating it is under budget. An SPI of 0.9 means the project is earning only $0.90 for every $1.00 of planned work, indicating it is behind schedule. Therefore, the project is under budget and behind schedule, making option B correct.

The classic triple constraint includes scope, cost, and schedule. Quality is often added as a fourth constraint.

Storming is characterized by conflict and questioning of authority.

Perform Integrated Change Control (D) is the correct process because it is the formal process within project management that ensures all change requests are reviewed, evaluated for impact on scope, schedule, cost, and quality, and approved or rejected before implementation. This process integrates the change across all knowledge areas and requires documented approval, which directly addresses the project manager's need to evaluate and approve changes before they are implemented.

Stakeholders with high power and high interest should be managed closely as key players.

The change log is the correct document for recording and tracking changes to project scope and their approval status. It serves as a formal, chronological record of all scope change requests, including the date, description, impact analysis, and final disposition (approved, rejected, deferred). This aligns with the PMI's Project Management Body of Knowledge (PMBOK) guidance for the Perform Integrated Change Control process.

In a typical organizational chart for a project, the reporting structure shows that Developer 1 reports directly to Bob, who is the team lead or manager. Bob is therefore directly responsible for assigning tasks, reviewing work, and managing Developer 1's performance. This is based on the hierarchical lines of authority depicted in the exhibit.

Decomposition is the process of breaking down deliverables into smaller work packages within the WBS.

Monte Carlo simulation uses repeated random sampling to model the probability of different outcomes, commonly used for schedule and cost risk analysis.

EMV = Probability × Impact = 0.30 × $50,000 = $15,000.

Agile artifacts include product backlog, sprint backlog, and burndown charts. These are key to transparency and inspection.

Analogous estimation uses historical data from similar projects to estimate costs. It is quick and reliable when past projects are similar. Parametric uses statistical relationships, and bottom-up is detailed and time-consuming.

EMV = Probability * Impact = 0.3 * $50,000 = $15,000.

The first step in communication planning is to identify stakeholder communication needs, including what information they need, when, and how. This ensures that the plan addresses all requirements.

The SOW (Statement of Work) defines the deliverables, specifications, and performance criteria. It is the primary reference to verify compliance. The contract includes legal terms but the SOW details the technical requirements.

Common fields in an issue log include issue ID, description, owner, priority, status, and resolution date.

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

In a matrix organization, team members report to both a project manager and their functional manager. The project manager has high project priority but lacks direct authority over team members, meaning they cannot unilaterally assign work, evaluate performance, or make personnel decisions. This limited authority is the primary challenge because the project manager must rely on negotiation and influence rather than command-and-control to secure resources and commitment.

CPI < 1 means over budget; SPI > 1 means ahead of schedule. EAC > BAC typically when CPI < 1, and TCPI to meet BAC is >1.

The project sponsor provides executive support, secures funding, removes obstacles, and is ultimately accountable for project success. They often help resolve issues escalated by the project manager.

A status report template is a standardized document used to communicate project progress, issues, and next steps to stakeholders. It ensures consistency in reporting and helps stakeholders quickly understand the project's health, making it a core tool for project status reporting and communication.

Option A is correct because 'Next steps and action items' are a standard component of a project status report, as they communicate what will be done after the reporting period to keep stakeholders informed of upcoming work. This aligns with the PMBOK Guide's guidance on status reports, which should include a forward-looking section to maintain project momentum and accountability.

The RACI matrix defines roles as Responsible (doer), Accountable (final decision-maker), Consulted (subject matter experts), and Informed (kept updated). These are the four typical categories. 'Supporting' is not a standard RACI role.

Using a change control process ensures changes are evaluated, and maintaining clear requirements documentation helps prevent unauthorized changes. Gold plating is a cause of scope creep, not a solution. Fast tracking is a schedule compression technique, not scope management.

Closing includes formal acceptance, lessons learned, and archiving documents. Resource leveling occurs during planning/execution; risk identification occurs during planning.

The closing phase includes finalizing all activities, obtaining stakeholder acceptance, and closing the project.

The triple constraint includes scope, cost, and schedule. Quality is also a constraint but often considered as part of the triple constraint triangle.

The critical path is the longest path through the network diagram and determines the shortest project duration. Any delay on this path delays the project.

The critical path is the sequence of tasks that dictates the project's minimum duration.

A network diagram shows activities and their dependencies, and is used to identify the critical path. Gantt charts show timelines but not as clearly for path analysis.

CPI = EV/AC = 60,000/80,000 = 0.75. EAC = BAC/CPI = 200,000/0.75 = $266,667.

A Gantt chart uses horizontal bars to represent tasks over time, with dependencies and milestones typically marked.

A project is temporary, meaning it has a definite beginning and end, and it produces a unique outcome.

Assumptions and constraints are foundational elements that shape project planning and execution. The project charter formally authorizes the project and often captures high-level assumptions and constraints, while the project management plan details how the project will be executed, monitored, and controlled, including a more comprehensive list. Recording them in these documents ensures they are visible to all stakeholders and integrated into the project's baseline.

A risk is an uncertain future event; an issue is a current problem that has occurred.

Option D is correct because implementing a robust change control process with a change control board (CCB) ensures that all requirement changes are formally reviewed, approved, and documented before being incorporated. This directly addresses the risk of frequent, uncontrolled changes that caused schedule delays and cost overruns in the previous project, aligning with the PMBOK Guide's integrated change control process.

The final project report (B) is a key closure document that summarizes project performance, deliverables, and lessons learned, providing a formal record for stakeholders. Lessons learned (C) captures what went well and what could be improved, which is essential for organizational process improvement and future project planning.

The risk register is the central repository for risk information throughout the project.

The stakeholder register is the document that captures all stakeholders along with their influence, interest, and impact on the project. This register serves as the foundational input for stakeholder analysis and engagement planning, directly matching the description in the question.

Task B has a negative schedule variance (SV) because its earned value (EV) is less than its planned value (PV). With PV = 8 (planned effort) and EV = 50% * 8 = 4, the SV is 4 - 8 = -4, indicating the task is behind schedule. The other tasks have EV equal to or greater than PV, resulting in non-negative SV.

Cost variance (CV) is calculated as EV minus AC. With EV = $50,000 and AC = $70,000, CV = $50,000 - $70,000 = -$20,000. A negative CV indicates the project is over budget by $20,000.

The final project report is a key deliverable of the closure phase that summarizes performance and obtains formal acceptance. Lessons learned and closure checklist are also closure documents, but the final report is the primary acceptance document.

Delphi uses anonymous experts and rounds of questionnaires to reach consensus.

The critical path is the longest path through the project network diagram, determining the minimum project duration. By summing the durations of activities along each path (Start→A→C→F→End = 3+4+5=12 days; Start→B→D→F→End = 2+6+5=13 days; Start→B→E→End = 2+7=9 days), the path B→D→F has the longest total duration of 13 days. However, the correct answer is 12 days because the exhibit shows that activity F has a duration of 5 days, and the critical path is Start→A→C→F→End with a total of 12 days, making option D correct.

A negative variance on the critical path indicates the activity is behind schedule. Since the critical path has zero float, any delay directly extends the project's finish date. A variance of -2 days means the activity is 2 days late, which will delay the project by 2 days unless corrective action is taken.

Communication needs and preferred frequency are key inputs to the communication plan.

Cloud-based project management software (e.g., Jira, Asana, Microsoft Project Online) provides real-time collaboration, version control, and task assignment through a centralized web platform. It supports distributed teams by enabling simultaneous document editing, automatic change tracking, and role-based access, which directly meets the requirement for cross-continent coordination.

The sponsor provides resources, champions the project, and resolves issues that are beyond the PM's authority.

iSCSI is generally chosen over Fibre Channel primarily because it leverages existing Ethernet infrastructure, which significantly reduces hardware and operational costs. Fibre Channel requires specialized switches, host bus adapters (HBAs), and cabling, whereas iSCSI can run on standard network interface cards (NICs) and switches, making it a more cost-effective solution for many organizations.