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

WBS is a planning output that decomposes scope.

CPI above 1.0 means earned value exceeds actual cost, so the project is under budget. SPI below 1.0 means earned value trails planned value, so it is behind schedule. The indices measure cost and schedule efficiency on independent axes.

Quality is not one of the triple constraint's three axes — scope, time and cost — so it fails the stem's "NOT a typical constraint" test. Quality is instead an outcome affected by those three; changes to any of them typically alter it, but it is not itself a fixed constraint.

Storming is the stage where team members challenge the project manager's authority and conflict emerges over roles and direction. This directly matches the stem's reported conflicts and authority questioning, distinguishing it from forming (polite orientation), norming (cohesion established) and performing (focus on delivery).

Perform Integrated Change Control provides a formal review and approval gate, so every client request is evaluated for impact before implementation. It satisfies the stem's constraint that changes be properly assessed and authorised, unlike direct execution or informal tracking. This process owns the change control board and updates baselines once approved.

High power combined with high interest places the stakeholder in the grid's manage-closely quadrant, requiring active, regular engagement. Their ability to influence the project and their investment in outcomes mean their concerns must be addressed continuously to avoid disruption.

The project charter formally authorises the project's existence and grants the project manager authority to apply organisational resources to project activities. It is the document issued by the sponsor that satisfies the stem's requirement for formal authorisation and resource authority.

The change log records each change request, its assessment, approval or rejection decision and current status. It satisfies the stem's requirement to track scope changes and their approval status, unlike the scope statement or issue log.

Decomposition is the technique that splits WBS deliverables into progressively smaller, manageable work packages, satisfying the stem's requirement to break deliverables down during planning. It defines the lowest-level components that can be estimated, scheduled and assigned, which is precisely what the project manager needs before basing cost and duration estimates on them.

Monte Carlo simulation runs thousands of iterations, sampling probability distributions for cost and schedule variables, to produce a distribution of possible completion dates. This directly satisfies the stem's requirement for simulation-based quantitative risk analysis determining the probability of finishing on a specific date.

Expected monetary value multiplies probability by impact: 0.30 × $50,000 = $15,000. This quantifies the risk's average financial exposure, letting the project manager weigh it against contingency reserves or response costs during quantitative risk analysis.

The project charter formally authorizes the project and documents its purpose, high-level requirements, and key stakeholders. It is the appropriate document to provide to the sponsor at this stage, as it establishes the project's foundation and gives the project manager authority to proceed.

The sprint backlog is the agile artifact holding the product backlog items selected for the current sprint, plus the team's plan for delivering them. It satisfies the stem's need to manage work at the iteration level, unlike traditional schedules or work breakdown structures.

Analogous estimation uses historical cost data from comparable completed projects to derive the new estimate. With three similar past software projects available, this top-down technique is quick and appropriate, especially when detailed information is limited during early estimating.

Multiplying probability by impact gives the expected monetary value: 0.3 × $50,000 = $15,000. This quantifies the risk's average financial exposure, satisfying the register's requirement to express each risk in monetary terms for comparison and contingency budgeting.

A Kanban board visualises workflow by splitting work items into columns representing process stages, exactly matching the 'To Do', 'In Progress', and 'Done' layout described. It tracks user stories, epics, and bugs as cards moving between those columns, satisfying the stem's sprint-tracking and column-view constraints.

Stakeholder communication needs must be identified first because they determine who receives information, what content, which channel and frequency. Every later element of the communication plan — the matrix, methods and schedule — derives from this analysis, so establishing needs before selecting tools satisfies the plan's foundational dependency.

Because the scope cannot be reduced and the regulatory mandate is external, the only viable path is to formally process the modification through integrated change control. The change request captures the cost increase and schedule extension, allows impact analysis, and gives the CCB or sponsor the authority to approve a new baseline. Without this, the PM would be managing against an obsolete plan.

The complaints indicate that the communication plan was built without considering stakeholder influence, interest, or cultural context. Performing a stakeholder analysis allows the project manager to segment stakeholders by power and interest, understand language and cultural preferences, and select appropriate channels, formats, and frequency for each group. Tailoring the plan to these findings directly addresses why some stakeholders feel uninformed and improves engagement across regions.

A formal change request routes the new features through integrated change control, satisfying the stem's constraint that scope changes during execution must be assessed before work begins. It documents impact on scope, schedule and cost, letting the change control board approve or reject, rather than the project manager informally accepting out-of-scope work.

An issue owner assigns clear accountability for driving each logged issue to resolution. This satisfies the stem's requirement for a typical issue log field, ensuring someone is responsible for escalation, updates and closure rather than the issue being left unmanaged.

The project charter formally authorises the project's existence and explicitly identifies the assigned project manager, conferring authority to proceed. It satisfies both constraints in the stem, whereas subsidiary documents such as the project management plan assume authorisation already exists.

In a matrix organisation, functional managers control resources and performance reviews, so the project manager lacks direct line authority. This limited authority is the primary challenge when directing team members who report elsewhere, despite the project's high priority.

An SPI of 1.2 exceeds 1.0, meaning earned value outpaces planned value, so the project is ahead of schedule. This satisfies the schedule constraint directly, independent of the CPI of 0.8, which indicates cost overrun. SPI measures schedule efficiency only, so the ahead-of-schedule conclusion holds.

The sponsor sits above the project manager in the governance hierarchy, so issues the project manager cannot resolve within delegated authority are escalated to the sponsor, who arbitrates and removes organisational blockers, complementing the sponsor's resourcing and championing duties.

Status report template provides consistent updates.

Next steps are a standard status report section.

An instant messaging and persistent chat platform supports real-time collaboration by allowing quick questions, clarifications, and decisions across time zones, with searchable history. It addresses the real-time communication need in the scenario. Combined with a version-controlled repository, it forms a practical toolset for a distributed team's communication plan.

Clear requirements documentation gives the project manager a baseline against which requested additions can be compared, exposing any deviation from the agreed scope. Without this documented reference, changes cannot be identified or challenged, so the constraint of detecting scope creep is satisfied.

Obtaining formal acceptance from the sponsor satisfies the closing requirement to confirm deliverables meet agreed criteria before releasing resources. This sign-off transfers ownership to the business and authorises final payment, providing the documented closure evidence that project closing demands.

Closing is the phase where formal acceptance of deliverables is obtained, alongside finalising contracts and releasing resources. The stem's constraint is formal sign-off, which occurs only after verification confirms the product meets requirements. Acceptance documentation is produced here, transitioning the project from delivery into handover and administrative closure.

Critical path method identifies which task sequences determine the project's finish date, so inserting the vendor delay into the network diagram reveals whether float absorbs it or the end date slips. This directly satisfies the stem's need to analyse schedule impact and communicate revised timelines.

Schedule is one of the triple constraints directly affected by an approved change request, satisfying the stem's fixed-budget, strict-deadline scenario. Any approved variation alters task durations or sequencing, shifting the critical path and completion date.

Activities on the critical path have zero total float, meaning any delay directly extends the project's finish date. This zero-float property is precisely what defines the longest-duration sequence through the network diagram, satisfying the stem's requirement to identify critical path characteristics.

Critical path analysis identifies the longest sequence of dependent activities, whose total duration equals the shortest possible project completion time. Any delay on that path directly delays the finish date, so it is the activity that determines the schedule's end.

A network diagram maps tasks as nodes with arrows showing dependencies, making the longest sequence — the critical path — visible. That directly satisfies the stem's requirement to visualise both task dependencies and the critical path for the construction project.

Using the cost performance index (CPI) to extrapolate future spending satisfies the stem's constraint that the project continues at the same cost efficiency. CPI is EV ÷ AC = 60,000 ÷ 80,000 = 0.75, so EAC = BAC ÷ CPI = 200,000 ÷ 0.75 = $266,667.

A Gantt chart renders activities as horizontal bars positioned along a timeline, with bar length showing duration and links showing dependencies and milestones. This directly satisfies the stem's requirement for a tool depicting bars, dependencies and milestones.

Performing quality assurance belongs to execution because it applies planned quality processes to verify deliverables meet standards, satisfying the stem's execution-phase constraint. Unlike monitoring and controlling, which tracks performance against baselines, quality assurance is proactive process auditing conducted while work is produced, confirming it as a genuine execution activity.

A defined start and end date expresses the temporary nature of a project, which is the characteristic distinguishing it from ongoing operations. This satisfies the stem's definition directly, since uniqueness of the deliverable and temporariness are the two defining attributes.

A risk is a potential future occurrence with probability and impact that may or may not materialise. An issue has already occurred and requires active resolution now. This temporal and certainty distinction drives separate treatment: risks are analysed and responded to proactively, issues are managed in the current log.

Manage Project Issues is the process of identifying, logging, assigning, and driving project issues to resolution, including owners and due dates. The compliance violation is an active problem threatening the project, and the project manager is doing exactly that: documenting it, assigning accountability, and setting a target date for closure.

A formal change control process with change control board review directly addresses the root cause of the previous project's delays: uncontrolled requirement changes. By requiring impact assessment and approval before implementation, scope creep is contained, protecting both the schedule baseline and cost baseline from unauthorised modifications.

The final project report formally records scope, deliverables, variances and acceptance, providing the sponsor's authorisation to close. Finalising it during closure satisfies the requirement to document final performance against baselines and transition the product to operations.

The risk register is the artefact that logs each identified risk alongside its probability, impact and agreed response strategy. It satisfies the stem directly, unlike a risk management plan, which describes approach rather than listing individual risks.

The stakeholder register is the document that records identified stakeholders alongside their interest, influence and impact, which is exactly the analysis artefact described. It satisfies the requirement to capture influence, interest and impact in one place.

Cost variance is earned value minus actual cost: $50,000 minus $70,000 equals -$20,000. The negative figure shows the project has spent more than the value earned to date, directly matching the stem's supplied EV and AC values.

Anonymity lets panellists submit and revise judgements without social pressure or dominance by senior voices, which is the defining mechanism separating Delphi from interacting groups such as brainstorming or nominal group technique. This satisfies the stem's requirement for a genuine Delphi characteristic, since controlled feedback across anonymous rounds converges expert opinion.

A negative variance means the activity is taking longer than planned, so it is behind schedule. On the critical path, any delay directly pushes out the project finish date, since critical path activities have zero float. The -2 days therefore translates into a two-day project delay.

Communication needs establish what information each stakeholder requires, forming the content dimension of the communication plan. Addressing this per stakeholder ensures relevant, timely updates and satisfies the stem's requirement to consider factors tailored to each individual or group.

Cloud-based project management software centralises documents in a shared repository accessible from any location, providing concurrent editing, version history, and task assignment in one platform. This directly satisfies the three-continent constraint requiring real-time collaboration alongside version control and task allocation.

The sponsor secures funding and executive backing, and removes organisational obstacles escalated by the project manager. The stem asks for a primary sponsor responsibility, and providing funding and clearing blockers satisfies this by reflecting the sponsor's authority above the project manager, distinct from day-to-day delivery duties.

Time is one of the three project management triangle constraints, alongside cost and scope. It bounds the schedule within which the deliverable must be produced, so any compression directly trades off against the other two axes.

iSCSI transports SCSI commands over existing Ethernet infrastructure, so it reuses standard switches, cabling and NICs rather than requiring dedicated Fibre Channel HBAs and fabric switches. That reuse is the axis of difference, satisfying the stem's cost constraint when the organisation lacks a Fibre Channel fabric.

The resource management plan defines how project roles are staffed, so the vacant key role must be recorded there first. Updating it establishes the replacement approach before procurement, RACI or schedule documents are revised to reflect the new team member.

Acceptance criteria define the measurable conditions a deliverable must satisfy to be accepted by the sponsor or customer. They form a key component of the scope statement because they bound what counts as complete, alongside deliverables, exclusions and assumptions.

An SPI of 0.9 falls below 1.0, meaning earned value lags planned value — the project has completed less work than scheduled at this point. This directly satisfies the stem's schedule-performance constraint, confirming the project is behind schedule. CPI, by contrast, measures cost efficiency, so it cannot support this conclusion.

The benefit component of a user story states the value or outcome the feature delivers, completing the "so that" clause. It satisfies the stem's requirement to describe the benefit or value provided, as distinct from the role or the desired capability.

A hybrid cloud management platform is designed to provide a unified interface for managing resources across on-premises and cloud environments. It enables centralized provisioning, monitoring, and governance, directly satisfying the requirement for a single pane of glass and simplifying operations for the project team.

Once the change control board approves a scope change, the approved change must be reflected in the project management plan and its scope baseline, since those documents formally define approved scope, schedule and cost against which performance is measured.

In a matrix organisation, resources remain under functional manager control, so the project manager must negotiate directly with that manager to secure the team member. Negotiation addresses the shared-authority constraint rather than escalating or demanding the resource.

Even when a project is terminated early, the project manager must capture lessons learned and archive records. This preserves organizational knowledge, supports audits, and helps future projects avoid similar issues. It is a core closure activity that applies regardless of whether the project delivered all planned scope.

The schedule is the artefact that records activity dates, dependencies and float, so a critical path shift must be reflected there first. Updating it establishes the revised baseline from which other documents, such as the risk register, are then reconciled.

Closure requires all deliverables to be formally accepted, and two remain unaccepted because of minor quality issues. Correcting those defects and securing client sign-off satisfies that acceptance prerequisite, which must precede resource demobilisation and final project closure.

This is the correct first step because it follows the integrated change control process: assess the impact on scope, schedule, cost, quality, and risk, then present options for approval. It preserves the contract baseline and gives the customer the information needed to decide whether to adjust the deadline, budget, or scope.

Planning poker achieves consensus by having each estimator reveal their card simultaneously, exposing divergent assumptions before discussion. This satisfies the stem's requirement directly: the technique's purpose is collective agreement on effort, not individual accuracy or velocity forecasting. Divergence triggers debate, then re-estimation, converging the team on one shared estimate.

Before approving, rejecting or deferring the request, the project manager must assess how it affects scope, schedule, cost, risk and quality. Impact analysis produces the evidence the change control board needs, so it precedes any decision or baseline update.

Because the specialist is scarce and the demand is short but critical, the PM should plan a backup and protect the schedule with reserve. A contingency reserve covers known risks such as the specialist being reassigned. Identifying an alternate reduces the impact if the primary becomes unavailable. Together these actions address both the probability and the impact of the resource risk without inflating the entire plan.

High-power, low-interest stakeholders require sufficient engagement to prevent them from becoming blockers, yet without overwhelming them with operational detail. Periodic high-level updates satisfy this by maintaining awareness and confidence while conserving their attention. This matches the power/interest grid's "keep satisfied" quadrant, which prioritises concise, strategic communication over frequent granular reporting.

Approved scope changes must flow into the scope baseline, which comprises the project scope statement, work breakdown structure, and WBS dictionary. Updating it preserves the authorised scope against which performance is measured, satisfying the stem's requirement to revise the project management plan after change control approval.

Relationship building is essential in a weak matrix where the project manager lacks direct authority. Trust and cooperation increase the likelihood that functional managers will prioritize project work and that team members will follow project direction. This leverages interpersonal skills and informal influence rather than formal power.

Approved changes altering cost and schedule require formal revision of the affected baselines, since baselines are the approved reference points against which performance is measured. Updating the project plan alone leaves cost and schedule baselines stale, so both must be revised to reflect the 10% cost increase and 15% schedule reduction.

CPI is EV divided by AC, giving 50,000/60,000 = 0.83. Any value below 1.0 means earned value trails actual cost, so the project has spent more than the work delivered is worth — over budget.

A work breakdown structure decomposes scope into deliverables, not activities, so each element must represent a tangible output the project produces. This satisfies the best-practice constraint that WBS nodes define what will be delivered, enabling accurate scope, cost and acceptance criteria assignment.

Archiving records and capturing lessons learned preserves organizational process assets so future projects can avoid repeated mistakes and reuse effective practices. This transfer of knowledge is explicitly part of closing, alongside releasing resources and finalizing contracts. It ensures the value of the project extends beyond its own timeline.