CompTIA Project+ PK0-005 (PK0-005) — Questions 226–300

Activity C depends on both A and B, so its earliest start is the longer of the two parallel paths: A finishes at day 5, B at day 3. Adding C's 4 days gives 9 days, the critical path duration. The A-C sequence governs, not B-C.

A scalable deployment architecture with centralized management allows the monitoring solution to add new data centers without redesigning the entire system. Centralized management simplifies configuration, updates, and reporting across sites. This directly supports the requirement to scale as new data centers are added while maintaining consistent monitoring policies and reducing operational overhead.

A stakeholder with high power and low interest falls into the keep satisfied quadrant; the goal is to deliver enough relevant information to prevent surprises or opposition without demanding heavy involvement. Because this department head controls funding, ignoring them risks late resistance, while overloading them with detail may be counterproductive, so targeted, concise engagement is appropriate.

A load balancer distributes incoming traffic across multiple servers, eliminating single points of failure and enabling horizontal scaling as demand grows. This directly satisfies the stem's high availability requirement by rerouting around failed nodes, and its scalability requirement by adding backend instances without service disruption.

Any addition beyond the scope baseline must pass through integrated change control. Submitting a change request to the change control board satisfies the stem's requirement by ensuring the new feature is formally evaluated for impact on scope, schedule, cost and risk before any work begins.

Planning consumes the most effort initially because competing departmental priorities and a tight deadline demand scope definition, resource negotiation, schedule compression and risk identification before execution can begin. These activities all sit within the Planning process group.

Assessing the change's effect on scope, schedule and cost gives the CCB and sponsor the data needed to approve, reject or defer it. Without this impact analysis, no informed decision on the change request is possible, so it must precede submission or any baseline edit.

EMV quantifies risk exposure by multiplying monetary impact by probability: $50,000 × 0.20 = $10,000. This figure lets the project manager weigh the risk against mitigation costs, satisfying the stem's requirement for a single expected monetary value.

The burndown chart tracks remaining work, so adding stories mid-sprint raises the remaining total even while the team completes points. Completed work of 30 story points alongside an upward trend therefore indicates scope was injected into the sprint.

Anonymous questionnaires let experts contribute without the pressure of seniority or groupthink, and the facilitator iteratively circulates responses until consensus emerges. This matches the Delphi technique's defining mechanism, satisfying the stem's requirement for a structured, anonymity-preserving route to expert agreement on risk identification.

A CPI of 0.8 means every unit of planned spend delivers only 0.8 of earned value, so the project is over budget. An SPI of 1.2 means earned value exceeds planned value, so work is ahead of schedule.

Reprioritising the backlog at the sprint review lets the product owner act on stakeholder feedback and emerging business needs, so the highest-value work is pulled into the next sprint first. This directly satisfies the stem's flexibility constraint, ensuring effort targets maximum customer value rather than a fixed upfront plan.

The EAC of $250,000 is derived from the formula EAC = BAC / CPI, which applies when the cost performance index (CPI) is expected to remain constant for the remainder of the project. Given BAC = $200,000 and CPI = EV/AC = $80,000/$100,000 = 0.8, the calculation yields $200,000 / 0.8 = $250,000. This satisfies the constraint that the same CPI persists, reflecting no change in cost efficiency.

Even when a project is terminated early, the Close Project or Phase process must still be executed. This includes obtaining final acceptance of any completed deliverables, archiving project documents, documenting the reasons for termination, and releasing team members and other resources. Skipping closure activities leaves the project open and prevents organizational learning.

A regulatory compliance checklist enumerates the specific data-security standards, controls and evidence the project must satisfy, giving the team an auditable reference. It directly addresses the compliance constraint by mapping required safeguards to deliverables rather than relying on general security guidance.

A hybrid life cycle combines predictive and adaptive phases within one project, matching the stem's split: predictive requirements gathering and design, then iterative sprints for development. It satisfies the constraint that both approaches coexist sequentially, rather than the whole project following a single methodology.

Gold plating is adding unrequested features beyond scope to improve a deliverable, consuming budget and time without customer approval. This precisely matches the stem's description of extra unrequested work, unlike scope creep which stems from stakeholder requests.

In a strong matrix organization, functional managers control the people and the project manager must negotiate for their time. Presenting the approved project charter, which documents the project manager's authority, alongside the non-negotiable regulatory deadline gives the functional manager a clear basis to prioritize the assignment. This is the recognized path to securing scarce specialized resources in a matrix environment.

Power over Ethernet lets the switches supply power to access points, IP cameras and VoIP handsets over the same copper cabling. Where such devices are deployed, omitting PoE support would require separate power injectors or additional electrical work.

Agile matches the stem's evolving requirements through iterative, time-boxed sprints and a prioritised backlog that accommodates change. Daily stand-ups provide continuous coordination, unlike waterfall's sequential phases or PRINCE2's stage-gate governance. This satisfies the constraint that requirements evolve throughout the project rather than being fixed upfront.

After the charter is approved, the project enters the Planning process group, where the project management plan is created. This plan integrates scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management plans. It provides the baseline and guidance needed before execution begins. Developing the plan is the logical next step to translate the charter's high-level authorization into actionable details.

During storming, disagreements surface as members push competing approaches and question one another's proposals, so challenging each other's ideas is the characteristic behaviour. This precedes norming, where the team settles on shared working agreements and roles.

NPV discounts all future cash inflows and outflows to present value, then subtracts the initial investment. A positive NPV signals the project adds financial value, making it a standard discounted cash-flow method for comparing and selecting candidate projects during project selection.

A milestone list identifies significant checkpoints, and mandatory milestones are those required by contract or regulation. Flagging the regulatory date lets the team track progress against discrete, zero-duration checkpoints rather than only the final deliverable, so slippage is visible as soon as an intermediate milestone is missed, well before the closing status report is produced.

Cost-reimbursable contracts pay the vendor all allowable incurred costs plus a fixed fee, matching the stem exactly. The fee is fixed while costs vary, distinguishing it from fixed-price, which sets one total price regardless of actual costs.

The project charter formally authorizes the project and identifies the initial stakeholders, including the project sponsor, key team members, and other parties with a vested interest. It provides the project manager with the authority to begin work and is a primary input to stakeholder identification. This makes it the correct source for the initial stakeholder list.

Communicating project status to stakeholders is a core project manager duty, satisfying the stem's requirement for primary responsibilities. The project manager owns performance reporting, translating schedule, budget and risk data into stakeholder-appropriate updates. This differs from the sponsor, who authorises and funds, and the PMO, which defines standards. Regular status communication sustains alignment and informed decision-making.

Initiation is the first phase where the project is defined and authorized.

The project charter formally authorises the project and names the project manager. It contains the business case, high-level scope and budget constraints, exactly the elements described, distinguishing it from subsidiary documents such as the scope statement.

A phone call delivers immediate, direct notification to senior management, letting them question the project manager and authorise action during an active outage. Written updates are too slow for this urgency, so verbal briefing satisfies the stem's need for rapid escalation of a critical incident.

The issue log is the project artefact specifically designed to record, assign and track issues through to resolution, capturing owner, status and due dates. It directly satisfies the stem's requirement to record and monitor issues, unlike a risk register, which addresses uncertain future events rather than problems already occurring.

Logging the violation in the issue log preserves the audit trail, and the change request routes the security-policy question through formal change control, letting the sponsor weigh risk against schedule without the vendor's unauthorised tool silently bypassing governance.

A Gantt chart plots tasks against a calendar timeline, with bars showing duration and linking arrows that expose finish-to-start dependencies. This directly satisfies the stem's requirement to schedule work and display task dependencies, making it a standard project scheduling tool.

Integration with the project management tool centralises risk data and automated reminders drive the consistent updates the spreadsheet failed to achieve, while built-in scoring replaces manual tracking. This directly addresses the stem's constraints of poor team engagement and absent risk scoring.

The change control board is the formal stakeholder group that reviews analysed change requests and authorises, defers or rejects them, satisfying the stem's requirement for a body deciding approval after schedule, cost and quality impact analysis. Its authority is distinct from the requester and the performing team.

Fast-tracking overlaps activities to shorten duration, while crashing adds resources to critical-path tasks; both aim to compress the schedule to meet a deadline. This shared purpose is the accurate commonality, distinguishing them from techniques that alter scope instead.

The cost baseline is the time-phased budget that the sponsor approved, so it supplies planned cost per period. Actual costs come from project accounting records, and comparing the two yields cost variance and the CPI. It therefore satisfies the stem's requirement for planned versus actual cost performance data.

Scope creep is managed through integrated change control, so the project manager must first assess how the extra features affect scope, schedule, cost and risk, then route a formal change request to the change control board for approval or rejection before any work proceeds.

Routing CR-01 through the change control board satisfies the governance constraint in the stem: any request altering approved scope, schedule or budget needs formal evaluation before implementation. The board assesses impact, risk and resource implications, then authorises, defers or rejects, keeping the change request log's status accurate.

Points plotting beyond the upper control limit signal that the process is influenced by an assignable, non-random source rather than normal common cause variation. This satisfies the stem's observation of out-of-limit data, indicating special cause variation requiring investigation.

It has the highest risk score and requires active monitoring.

Updating the lessons learned repository is an essential part of the Closing phase. It documents what went well, what could be improved, and recommendations for future projects. This knowledge transfer is a key output of the Close Project or Phase process. The project manager should complete this before final project closure, regardless of other completion criteria. It ensures organizational learning and continuous improvement.

The project charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. In this ERP infrastructure refresh, the sponsor signs the charter to legitimize the effort. Without it, the project manager lacks formal power to commit budget, people, or vendor contracts, and the project would lack an approved start.

The risk management plan sits within the project management plan's subsidiary documents, defining how risks are identified, assessed and responded to across the project lifecycle. It satisfies the stem's requirement for a formal planning artefact that governs a knowledge area.

A project wiki provides asynchronous, persistent documentation accessible across all three time zones, directly satisfying the requirement that information be stored for future reference. Unlike synchronous meetings or chat, it eliminates scheduling conflicts and creates a searchable knowledge base, improving collaboration for a distributed team.

The kickoff meeting communicates the approved project management plan, roles, responsibilities, and ground rules to the team and stakeholders, signaling the start of execution. It aligns everyone on objectives and expectations before work begins. In CompTIA Project+ sequencing, the kickoff occurs after plan approval and before or as execution starts, making it one of the activities that formally launches the Executing phase.

The critical path method calculates the longest sequence of dependent activities through the network diagram, directly satisfying the stem's aim of identifying that longest path. Float calculations then reveal which tasks can slip without delaying the project end date, unlike resource levelling or crashing, which adjust rather than identify the path.

The Delphi technique gathers expert judgements through successive anonymous questionnaires, iterating until consensus emerges. Anonymity removes dominant personalities and groupthink, directly satisfying the stem's requirement to avoid bias during risk identification. Unlike brainstorming or nominal group technique, experts never meet face to face, so influence between participants is eliminated.

When scope, time, and cost are all fixed and infeasible together, the project manager cannot unilaterally break a constraint. Escalating to the sponsor, who controls budget and can authorize trade-offs, is the appropriate action to obtain a decision on which constraint to adjust or what additional resources to provide.

Even when a project is terminated early, the Close Project or Phase process must still be performed. This includes documenting the reason for termination, capturing lessons learned, and formally closing out the project. It ensures organizational knowledge is retained and all administrative closure activities are completed regardless of whether deliverables were finished.

Cost performance index is EV divided by AC, so 120,000 / 150,000 = 0.8. The estimate to complete is (BAC - EV) / CPI, giving 80,000 / 0.8 = $100,000, assuming the same cost efficiency continues.

Finish-to-Start (FS) directly encodes the stem's constraint: B's start is gated by A's completion. It is the default precedence relationship in project scheduling, so any successor activity waits on its predecessor's finish. Other dependency types (SS, FF, SF) permit overlap or different anchor points, none of which satisfy "cannot start until complete".

A Pareto chart is a histogram ordered by frequency that helps identify the most significant factors contributing to a problem. In quality control, it is used to prioritize defects by frequency or impact, often following the 80/20 rule. In this scenario, it helps the project manager focus on the few defect types that cause the majority of issues, enabling efficient root cause analysis and corrective action.

The chain A then B then C gives a single critical path of 5+7+4 days, so no slack exists anywhere along it. Activity B sits on that critical path, meaning any delay slips the project; its total float is therefore zero days.

An incremental life cycle delivers the solution in successive functional increments, so a working subset of high-priority network upgrades can be released early while later increments follow as funding permits. This matches the sponsor's intent to realize value within four months and to gate remaining work on budget availability. Each increment adds usable functionality to the same solution rather than producing separate unrelated products.

Releasing project resources satisfies the closure constraint by formally disbanding the team once deliverables are accepted. This frees personnel for other assignments and closes cost accounts, preventing further charges against the project budget. Unlike ongoing execution activities, resource release confirms the project has ended and no remaining work requires staffing.

A CPI of 0.8 means every £1 spent delivers only £0.80 of earned value, so the project is over budget. An SPI of 1.1 means earned value exceeds planned value, so work is ahead of schedule. This option satisfies both constraints simultaneously.

With a negative NPV and an IRR of 4% below the company's 6% required rate of return, the project destroys value on both discounted measures. The payback period is irrelevant when the hurdle rate is unmet, so rejecting it satisfies the stated financial criteria.

Cost is one of the triple constraints, alongside scope and time, limiting what a project can deliver. Budget availability directly restricts options throughout planning and execution, satisfying the stem's requirement for a genuine project constraint.

Incorrect MX records mean sending mail servers cannot locate the new service, so delivery fails regardless of server health. Updating the DNS records to point at the cloud service and allowing propagation restores routing, which is the prerequisite for any further delivery testing.

Fast-tracking overlaps sequential activities to shorten duration without adding cost, directly addressing the sponsor's acceleration request. It suits tasks that can run in parallel, though it raises rework risk. Crashing, the alternative, adds resources and cost instead. Both are recognised schedule compression techniques, satisfying the stem's requirement for two options.

Correct: mitigation reduces probability or impact.

Customer collaboration over contract negotiation satisfies the agile principle of prioritising working relationships with stakeholders above rigid contractual terms. In iterative development, requirements evolve each sprint, so continuous customer feedback shapes the backlog rather than fixed scope agreed upfront. This directly supports the stem's iterative delivery and daily stand-up cadence.

A consistent naming and versioning convention ensures team members can identify the latest approved document and trace revisions. This directly supports the goal of controlled changes and easy retrieval, and it is a foundational practice for any shared project repository where multiple contributors update artifacts over time.

SWOT analysis examines internal strengths and weaknesses alongside external opportunities and threats, exposing risks arising from organisational and environmental factors. It meets the stem's identification requirement by uncovering candidate risks for the register, distinct from qualitative or quantitative analysis, which prioritise and evaluate known risks.

The scope statement provides the detailed description of the project's deliverables, boundaries and acceptance criteria, directly satisfying the planning-phase requirement to define scope in detail. Unlike the charter, which authorises the project at a high level, it documents what is in and excluded from scope, giving the baseline for subsequent change control.

A team charter captures the operating agreement for the group: how members communicate, make decisions, resolve disagreements, and behave toward one another. On a multi-department team with a history of friction, making these expectations explicit and agreed-upon up front reduces ambiguity that fuels conflict. It also clarifies the project manager's authority relative to functional managers, which is essential in a shared-resource environment.

This is a valid risk because it is an uncertain event that could negatively impact the project schedule. Global supply chain issues are external and can cause delays. Documenting it in the risk register allows the project manager to analyze its probability and impact, and plan responses such as ordering hardware early or identifying alternative suppliers. It is a high-level risk appropriate for the Planning phase.

The project sponsor owns the business case and executive authority, so they secure and assign resources and escalate or clear obstacles exceeding the project manager's authority. This matches the stem's requirement for someone providing resources and removing obstacles beyond the PM's control.

Obtaining formal acceptance is the closing activity where the sponsor or customer signs off on the deliverables, confirming they meet requirements. This documented approval is what formally closes the project and satisfies the acceptance criterion in the stem.

The work breakdown structure decomposes project scope into work packages, the lowest deliverable level, from which tasks are assigned. It provides the hierarchical detail needed to allocate responsibilities, satisfying the stem's requirement for a work-package breakdown.

The project charter formally authorizes the existence of the project and gives the project manager the authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity and names the project manager. This matches the sponsor's request for the document that authorizes the project and assigns authority.

The project charter should contain clear success criteria and a high-level budget to authorize and bound the project. When these are vague, the project manager should work with the sponsor to refine and update the charter before detailed planning, ensuring the project has measurable objectives and an approved funding envelope. This prevents planning on unstable assumptions and aligns all stakeholders on what success looks like.

The stakeholder register is created during initiation as stakeholders are identified and their interests, influence and engagement requirements documented. It satisfies the initiation-phase output requirement, providing the baseline record that later feeds stakeholder engagement planning in the executing processes.

Fast-tracking overlaps sequential phases to compress the schedule without altering scope, directly addressing the behind-schedule constraint. Unlike crashing, which adds resources and cost, it accepts increased risk of rework by starting the next phase before the previous one finishes.