CompTIA Project+ PK0-005 (PK0-005) — Questions 301–375

Decomposing project scope into smaller, manageable components produces the work breakdown structure, a hierarchical deliverable-oriented decomposition of total scope. It forms the foundation for estimating, scheduling and control, directly satisfying the planning activity described in the stem.

In a matrix organisation, functional managers retain line authority over shared staff, so the project manager negotiates resource availability rather than directing it. Authority is therefore limited and shared, matching the stem's description of resources split with functional managers.

Obtaining formal acceptance from the sponsor satisfies the closure requirement to confirm deliverables meet agreed criteria before releasing resources. This sign-off transfers ownership to the business and authorises final payments, distinguishing closure from ongoing monitoring. Without documented sponsor acceptance, the project cannot be formally closed or lessons learned validated.

Progressive elaboration means the project's scope and plans are refined iteratively as information and detail emerge, rather than fixed upfront. PMI recognises this as a defining project characteristic, satisfying the stem's requirement for a genuine PMI attribute, alongside temporary endeavour and unique deliverable.

Total float equals late start minus early start, or late finish minus early finish: 10 minus 5, and 20 minus 15, both giving 5 days. This satisfies the calculation requested for the non-critical path activity.

SPI is calculated as EV ÷ PV, giving 0.8, which is below 1.0 and therefore signals the project is behind schedule, directly satisfying the stem's stated concern. The AC figure is irrelevant here, since SPI measures schedule efficiency only, not cost performance.

Cost-benefit analysis quantifies expected financial return by comparing projected benefits against implementation and operating costs, producing a comparable value for each candidate project. This directly satisfies the stem's criterion of a selection method that considers financial return.

The scope statement documents the project's deliverables, measurable product and project objectives, the boundaries of the work (what is in and out of scope), and the acceptance criteria the customer will apply. That matches every element the PM must record before breaking work into a schedule, making it the correct next artifact to produce for the portal replacement.

An announced external event that may delay the critical path is an identified risk with a known trigger window, so it belongs in the risk register with probability, impact, and a response plan. The PM can plan mitigation such as resequencing work, renting temporary power, or negotiating an alternate window. Updating the risk register keeps the analysis visible and drives proactive response rather than reactive firefighting.

A VPN with two-factor authentication encrypts the vendor's session and verifies identity before any internal resource is reachable, satisfying the need to permit installation access without exposing the network. Two-factor authentication specifically mitigates credential compromise, which a plain VPN tunnel alone would not address.

The project charter is the document that formally authorises the project's existence and grants the project manager authority to apply organisational resources to its activities. It names the project manager, states objectives and defines constraints, satisfying the requirement for formal authorisation and resource authority.

The risk register records identified risks, their probability, impact, and planned responses. It is compiled during planning as threats and opportunities are assessed, satisfying the stem's requirement for a planning-phase document that supports ongoing monitoring and response throughout execution.

Iterative approaches deliberately repeat cycles of build and feedback so that requirements are discovered and refined rather than fixed upfront. The autonomous vehicle scenario, with unproven technology and a customer wanting frequent demonstrations, aligns precisely: each prototype teaches the team something and shapes the next cycle, reducing uncertainty progressively.

The stakeholder register is a project document that identifies all stakeholders, including their roles, contact information, and other relevant details. It is used to plan stakeholder engagement and manage communications. In this scenario, the project manager needs a centralized list of stakeholders, making the stakeholder register the appropriate choice.

Planning poker has each team member privately select a card representing their story point estimate, then discuss discrepancies until convergence. This iterative reveal-and-discuss cycle produces a shared consensus estimate, directly satisfying the stem's stated purpose rather than merely averaging individual guesses.

An RFP formally solicits vendor proposals by stating requirements, evaluation criteria and submission terms, letting the buyer compare competing bids. It fits the stem's procurement step of inviting proposals, unlike an RFI, which only gathers capability information before requirements are fixed.

SaaS delivers a complete application managed by the vendor, eliminating upfront hardware and software licensing costs. The sales team can access the CRM via a browser, and the vendor handles maintenance, updates, and infrastructure. This aligns with the sponsor's goal to avoid capital expenditures and reduces total cost of ownership, making it the most suitable cloud service model for this scenario.

The risk management plan documents methodology, roles, budget, timing, and risk categories, establishing how identification, analysis, response planning, and monitoring will be performed throughout the project. This governance framework is its primary purpose, not the actual handling of individual risks.

Multiplying the 20% probability by the 10% cost impact gives an expected monetary value of 2% of project cost, directly satisfying the stem's requirement to quantify the risk's EMV during planning. This probability-weighted figure, not the full 10% exposure, is the correct contingency input.

The WBS decomposes the total project scope into progressively smaller, manageable work packages, giving a hierarchical view of every deliverable and its associated work. This directly satisfies the need to break scope down into work packages for planning and control.

CPI is EV ÷ AC, giving 80,000 ÷ 90,000 = 0.89, so every dollar spent delivers 89 cents of value. SPI is EV ÷ PV, giving 80,000 ÷ 100,000 = 0.80, confirming the project is behind schedule. Both indices satisfy the stem's requirement to measure cost efficiency and schedule progress.

The change control board is the authority that reviews and approves or rejects change requests. Since the impact is assessed, the request must be formally submitted for a decision before any baseline or plan updates occur.

Once the charter is approved, the project manager integrates all subsidiary baselines and plans into the project management plan, which directs execution and control. This satisfies the NEXT-step requirement because planning follows authorisation, before work is performed or baselines are formally approved.

The project sponsor authorises the project and supplies resources and funding, directly satisfying the stem's requirement to secure approval and champion the initiative. Unlike the project manager, who executes within delegated authority, the sponsor owns the business case and holds budgetary control, making them the role accountable for greenlighting and resourcing the mobile application development.

Assuming future work proceeds at the planned rate, the estimate to complete uses the remaining budget: BAC minus EV, giving $10,000 − $4,000 = $6,000. This satisfies the stem's constraint that work continues at the planned rate, rather than the current cost performance, which would instead require dividing by the cost performance index.

Risk identification and creation of the risk management plan occur during planning, where the project manager defines how risks will be identified, analysed, and responded to before execution begins. This satisfies the stem's requirement for the phase producing the risk management plan.

The scope statement is the document that formally records deliverables, acceptance criteria, exclusions, assumptions and constraints, giving the project manager an approved baseline against which scope changes are assessed. It satisfies the stem's requirement for a single artefact defining all five elements.

The final project report summarises scope, schedule, cost and outcome performance, providing the sponsor with documented evidence for formal sign-off. It satisfies the stem's closure requirement, unlike the charter or business case, which belong to earlier phases.

A burndown chart plots remaining work against time across the sprint, so flat or rising lines immediately expose work not decreasing as expected. It satisfies the stem's need to visualise the remaining-work trend over the sprint duration.

Logging the issue alone leaves it unmanaged. Assigning an owner and target resolution date converts the entry into an actionable item, ensuring accountability and a deadline for the one-day delay already incurred, which is the immediate next step in issue-log handling.

Closing requires the sponsor to formally accept the delivered product, confirming it meets requirements before the project can be authorised for closure. This sign-off satisfies the stem's closing-phase constraint, since acceptance occurs after verification and precedes final handover and resource release.

Regular email updates suit low-power, high-interest stakeholders because they need frequent, digestible progress information without demanding intensive engagement. Email delivers scheduled, asynchronous communication that keeps this group informed and satisfied, matching their high interest while respecting their limited influence over project decisions. More interactive methods would over-serve stakeholders who cannot affect outcomes.

The traditional triple constraint comprises scope, time and cost. Time is one of those three axes, so it satisfies the stem's requirement to identify a triple-constraint component, distinct from quality, which sits outside the classic trio.

A policy granting access to any user removes identity-based restriction entirely, exposing the stored data to anonymous or unintended principals. This is the most significant risk because it nullifies authentication and authorisation controls, unlike narrower misconfigurations that still limit who can reach the resource.

Microsoft Project recalculates dependent task dates only when scheduling is triggered after actual finish dates are recorded. Verifying links and entering actuals, then recalculating, satisfies the stem's stale finish-to-start dependency, since Task 4 cannot shift until Task 3's completion is registered and the schedule recomputed.

The 100% rule requires that a WBS capture all project scope: every deliverable and work package appears, and child-level effort sums exactly to the parent's total. This prevents omitted or duplicated work, satisfying the stem's requirement that lower-level totals equal higher-level totals.

Hybrid suits a fixed deadline with evolving requirements by fixing the schedule and budget baseline predictively while iterating requirements delivery. This satisfies both stem constraints: the deadline is protected through predictive planning, and requirement volatility is absorbed by iterative elaboration rather than upfront specification.

Hybrid delivery forces iterative scope evolution against a fixed waterfall baseline, so change requests must be assessed without eroding approved baselines. This directly addresses the stem's core tension: reconciling adaptive execution with formal baseline control, which is the defining governance challenge of hybrid projects.

Redundant network paths eliminate single points of failure and enable traffic to route around outages, sustaining availability while keeping latency low for critical applications. This directly satisfies both stated requirements, unlike additional compute or storage capacity, which addresses neither.

A published regulation that invalidates a design assumption creates a change that must be evaluated for scope, schedule, cost, and compliance impact. Raising a change request and routing it through integrated change control preserves traceability, produces a documented decision, and ensures baselines are only updated after approval. This satisfies the project manager's goal of accuracy plus auditability.

CV subtracts actual cost from earned value; a negative result means costs exceed the value earned, so the project is over budget. It gives the over-budget condition as an absolute currency amount, complementing CPI's ratio-based view of the same cost performance.

The twelve-week permit lead time is a mandatory external dependency and a schedule constraint. The project manager must record it, adjust the network logic so site preparation starts after permit issuance, and then assess the resulting impact on the critical path and project finish date before deciding whether further action is needed.

Uniqueness is a defining project characteristic: every project creates a distinct product, service, or result, differentiating it from routine operations. This progressive elaboration of a novel deliverable satisfies the stem's requirement for a key project characteristic.

The project charter authorises the project and documents its high-level requirements, objectives and success criteria, so it directly satisfies the need to define these before initiation. Business cases and benefits management plans may reference benefits, but the charter is the formal artefact that records measurable success criteria at authorisation.

Documenting the change request and recording it in the change log constitutes the documentation and logging step of integrated change control, where requests are formally captured before review, approval, and subsequent implementation within the project.

Monte Carlo simulation runs repeated random sampling across probability distributions for cost and schedule variables, producing a range of possible outcomes with confidence levels. This iterative numerical modelling satisfies the quantitative risk analysis requirement to assess combined risk exposure.

Historical data and lessons learned supply actual durations from comparable past projects, replacing optimistic assumptions with evidence-based estimates. This directly addresses the root cause identified in the stem — initial estimates being too optimistic — by grounding future estimates in demonstrated team performance.

A private meeting is the appropriate first step in progressive discipline and performance management, allowing the PM to understand root causes, clarify expectations and agree corrective actions without public embarrassment, thereby addressing the shortfall while preserving the team member's motivation.

Monte Carlo simulation repeatedly samples probability distributions for cost and duration to model thousands of possible outcomes, producing a distribution of completion dates. This satisfies the requirement for quantitative schedule-probability analysis, unlike deterministic or qualitative techniques.

Correct. After charter approval, the project manager develops the comprehensive project management plan.

Interactive communication involves real-time, multidirectional exchange of information between two or more people. Daily stand-up meetings are interactive because team members actively share updates, ask questions, and collaborate in real time. This method is most effective for ensuring shared understanding and immediate feedback among participants.

Fast-tracking runs normally sequential activities in parallel, compressing the schedule but removing the buffer between dependent tasks. That overlap means a delay or defect in one stream propagates into the other, raising the likelihood of rework during the executing phase.

R2 has the highest risk score of 0.30.

Opportunities are external favourable conditions the project could exploit, such as emerging market demand or new technology. They sit in the external half of SWOT, paired with threats, and are distinct from the internal strengths and weaknesses.

A formal change control process with mandatory approval gates creates the governance mechanism that stops unapproved features entering scope. It satisfies the stem's constraint by routing every stakeholder request through documented impact assessment, so additions are only accepted once the sponsor authorises the corresponding schedule and budget revisions.

Recording and impact-assessing the request completes the preliminary evaluation; the change control board is the authority that approves, rejects or defers scope changes affecting the triple constraint. Submitting the request to that board is the next step before any baseline modification.

A load balancer distributes incoming traffic across multiple servers, which improves availability and prevents any single server from becoming a bottleneck. In a private cloud ERP deployment, a load balancer helps maintain service if one server fails, directly supporting the high availability requirement. It does not provide data redundancy or site recovery on its own, but it is a key component for resilient application delivery.

Acceptance acknowledges the risk and its potential consequences without changing the plan, reserving contingency for it. Documenting the vendor delay risk and monitoring it closely, with no proactive action, matches this response exactly, unlike mitigate, transfer or avoid.

Overlapping sequential activities, known as fast tracking, compresses duration by starting the successor before its predecessor finishes. Because work proceeds on incomplete inputs, rework and coordination risk rise, so the approach typically increases risk — the specific consequence the option asserts.

The project charter is the document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity. In a predictive life cycle, the charter is created during Initiating and serves as the foundation for planning. This matches the sponsor's request exactly.

Norming is the stage where conflict resolution begins and shared norms are established, satisfying the stem's requirement. Members shift from competing to cooperating, agreeing on working methods and values. This contrasts with storming, where conflict peaks, and performing, where productivity depends on those norms already being settled.

Cost Variance (CV) measures cost efficiency by subtracting actual cost from earned value (CV = EV − AC). A positive CV indicates the project is under budget; a negative CV signals overspending. This directly satisfies the stem's requirement to assess cost efficiency, unlike schedule-based metrics such as SV or SPI.

The project charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. It is issued by the sponsor or another authority outside the project and typically records the high-level scope, objectives, and identified stakeholders. Because leadership has already assigned a sponsor and the request is for formal authorization and resource authority, this is the document the project manager must produce.

Archiving project documents is a Closing-phase activity because it preserves the project's records for audit, compliance and future reference once deliverables are accepted. This satisfies the stem's requirement for typical Closing activities, as records are consolidated and handed over after the product is transitioned, not during Initiating, Planning or Executing.

Shipping encrypted physical media to the cloud provider bypasses the insufficient internet bandwidth entirely, since the bulk seed copy travels offline. Only incremental changes afterwards traverse the network, making the initial transfer feasible within the project timeline.

Probability supplies the likelihood dimension of the risk score, typically rated on a defined scale. Multiplied by impact, it produces the numeric exposure value recorded in the register, so without it the score cannot be calculated for the construction project.

A divestiture that eliminates the business need for part of the scope and moves the deadline is a significant change to the project's baseline. The disciplined first response is to document and submit a change request describing the scope reduction and schedule compression, obtain approval, and only then update the affected baselines and subsidiary plans. This preserves traceability between the changed business need and the revised project documents.

Acceptance criteria define the measurable conditions a deliverable must satisfy to be accepted, directly satisfying the scope statement's requirement to specify verifiable completion standards. Unlike objectives or assumptions, they bind sign-off to testable outcomes, preventing scope creep during validation. This makes them a recognised key component alongside deliverables and exclusions.

The project scope statement details the project deliverables, acceptance criteria, and exclusions, which are essential for creating a precise procurement SOW. It ensures the vendor's work aligns with the project's boundaries and quality expectations. By referencing it, the project manager can clearly define what the vendor must produce and how it will be accepted.

Keeps stakeholders informed.

The critical path method (CPM) is used to determine the longest path through a network diagram, which represents the shortest possible project duration. It helps identify critical activities that cannot be delayed without delaying the project. In this scenario, the project manager needs to find the longest path, so CPM is the correct technique. CPM also calculates float for non-critical activities.

The project charter formally authorises the project and grants the project manager authority over resources. Without it, the manager lacks legitimate mandate, so obtaining approval for a project charter satisfies the stem's constraint of a project already underway without formal authorisation.

A fishbone diagram organises potential causes of the schedule slippage into categories such as people, process and environment, exposing the underlying root cause rather than symptoms. It directly addresses the stem's need to identify why team members are diverted onto non-essential tasks.