CCNA Pkp Project Lifecycle Questions

Crashing saves 3 days for $3,000, giving $1,000 per day. This directly satisfies the stem's request for the crash cost per day, derived by dividing the additional cost by the days compressed on the critical path activity.

The issue log records active problems, their owners and resolution status, so reviewing it exposes communication breakdowns already logged as issues and shows which stakeholder updates have stalled. It directly satisfies the stem's constraint that stakeholders are not receiving timely updates, letting the project manager trace unresolved communication items and assign corrective action.

Analogous estimation uses historical data from a comparable past project, adjusted for size and complexity, to derive the current estimate. The reliance on a similar prior project rather than decomposed work packages identifies this technique.

Logging the newly identified risk in the risk register satisfies the stem's requirement to record it during execution. The register is the single repository capturing each risk's description, probability, impact, owner, and response, so assessment outputs and tracking updates are appended there as the risk lifecycle progresses.

The stakeholder register is produced during initiating, alongside the project charter, as the output that identifies everyone with an interest in the project. It satisfies the stem's requirement for an initiating-phase document because stakeholder identification happens before planning begins.

SPI > 1 indicates ahead of schedule.

A feasibility study evaluates technical, economic, legal, and scheduling factors to establish whether a project can realistically deliver its objectives within existing constraints. During the initiating phase, this assessment determines viability before resources are committed, directly satisfying the stem's requirement to identify the primary purpose.

The project charter formally authorizes the existence of the project and gives the project manager authority to apply organizational resources to project activities. CompTIA Project+ places charter creation in the Initiating phase. Because the sponsor requires a document that both authorizes the project and names the project manager before releasing funding, the charter is exactly the artifact needed to satisfy that condition.

Obtaining final acceptance of deliverables is a key activity in the Close Project or Phase process. It confirms that the project's products, services, or results meet the agreed requirements and that the customer or sponsor formally accepts them. This acceptance is necessary before the project can be considered complete and before final payments and resource release occur.

Critical path activities have zero float, so any delay directly extends the project's finish date. This satisfies the stem's requirement for a true statement about critical path behaviour: the path determines the shortest possible duration, and slack-free tasks on it transmit their slippage straight to overall completion.

Analogous estimation uses historical cost data from a comparable past project to derive the new estimate, which directly matches the top-down approach described. It satisfies the stem's constraint of relying on a similar project's actuals rather than decomposing deliverables, making it fast and inexpensive, though less precise than bottom-up methods.

Stakeholders rated high on both power and interest demand the closest engagement, since they can significantly influence the project and care deeply about outcomes. The power/interest grid assigns this quadrant the manage closely strategy, maximising involvement and addressing concerns directly.

The procurement agreement contains inspection, quality, and acceptance criteria that govern whether deliverables conform. Applying those criteria through formal inspection and acceptance verification produces documented evidence of the nonconformance, which is required before a claim can be substantiated. Without this verification step, the buyer cannot demonstrate that the seller failed to meet the contractually stated specifications.

Impact analysis must precede any decision on a change request, examining effects on scope, schedule, cost and risk. It satisfies the stem's constraint of identifying the first step, since the change control board cannot approve or reject without that assessment.

SPI is calculated as earned value divided by planned value. A result of 0.9 means only 90 per cent of the work scheduled has been earned, so the project is progressing slower than planned. Any SPI below 1.0 indicates the project is behind schedule.

High power combined with high interest places this executive in the quadrant demanding the closest engagement, so the project manager must manage closely. This satisfies the grid's requirement for regular, detailed communication and active involvement, ensuring their significant authority and stake are addressed throughout the project.

Two paths exist: A then C totals 5+4=9 days, while B alone totals 3 days. The critical path is the longest, so 9 days governs the project duration. This satisfies the stem's requirement to identify the critical path duration from the given dependencies.

High interest with low power maps to the "keep informed" quadrant of the power/interest grid, satisfying the stakeholder's need for regular project updates without granting decision-making influence. Engagement focuses on communication rather than consultation, ensuring the stakeholder stays aware while the project manager avoids unnecessary approval cycles with someone who cannot affect outcomes.

A fixed-price contract locks the seller into an agreed sum regardless of actual costs, so any overrun is absorbed by the seller. This places maximum cost risk on the seller, unlike cost-reimbursable or time-and-materials arrangements.

Decomposition subdivides project deliverables into progressively smaller, manageable work packages, satisfying the WBS constraint of hierarchical breakdown. It is the specific technique that transforms top-level deliverables into assignable, estimable components at the lowest WBS level.

Analogous estimation derives cost from the actual cost of a comparable historical project, then scales it for differences in size and complexity. This top-down, experience-based approach matches the scenario, unlike parametric or bottom-up methods that build estimates from component detail.

High-power, low-interest stakeholders can block or derail the project, so they must be kept satisfied through regular, concise updates that address their concerns without overloading them. This prevents disengagement from turning into active opposition when decisions require their approval.

Project closure requires consolidating and storing all artefacts — plans, contracts, reports and lessons learned — so they remain available for audit and future projects. Archiving project documents preserves this organisational knowledge and formally releases the records once the deliverable has been accepted.

Cost Performance Index equals EV divided by AC, giving 50,000/55,000, which is below 1.0. A CPI under 1.0 means each unit of work costs more than planned, so the project is over budget, satisfying the over-budget condition in the stem.

A valid WBS decomposes deliverables into work packages that are small enough for accurate estimating, scheduling, and control. If a work package is too broad, estimates become unreliable and tracking progress is difficult. This characteristic supports the planning goal of creating a manageable, measurable scope baseline that the team can execute and monitor effectively.

A procurement audit reviews the procurement process to identify successes and failures, and closing the contract ensures all terms are met and no further obligations exist. This is essential when an external vendor is involved. It protects the organization legally and financially, and it captures lessons learned for future procurements. It is a key activity in the Closing phase.

Using EAC = BAC ÷ CPI, with CPI = EV ÷ AC = 100,000 ÷ 120,000 ≈ 0.833, gives 200,000 ÷ 0.833 ≈ $240,000. This satisfies the stem's constraint that remaining work continues at the current cost efficiency, rather than assuming the original budget or schedule-based performance.

Norming is the Tuckman stage where interpersonal conflict subsides and the team coalesces around shared norms and working relationships. Members resolve earlier disagreements and build cohesion here, matching the stem's description of resolving differences and developing closer relationships.

The Initiating phase produces the project charter, formally authorising the project and the project manager, and it is where stakeholders are first identified and recorded in the stakeholder register. Both deliverables named in the stem belong to this phase, preceding planning, executing, monitoring and controlling, and closing.

CPI above 1.0 means earned value exceeds actual cost, so the project is under budget. SPI below 1.0 means earned value lags planned value, so it is behind schedule. Both indices together confirm cost efficiency with schedule slippage.

The issue log is used to document and track issues that arise during the project. It includes details such as the issue description, impact, and assigned owner. In this scenario, the technical limitation is an issue that needs to be evaluated. The project manager should review the issue log to see if this issue has been logged, assess its impact, and determine next steps. It is the primary document for managing issues during execution.

A phase gate is a decision point where governance reviews deliverables against exit criteria and issues a go, no-go, or redirect decision. Presenting evidence and obtaining that decision is the defining purpose of the gate and controls whether the project proceeds, changes direction, or stops.

The project manager's first step is to assess the impact of the vendor delay on the project schedule and then evaluate possible corrective actions. This analysis determines whether the delay can be absorbed, whether fast tracking or crashing is possible, or whether escalation is needed. Taking action without understanding the impact could lead to unnecessary changes or costs.

Forming is marked by politeness and dependence, as members orient themselves to the task and each other without yet challenging ideas. The stem's hesitation to share ideas and superficial courtesy match this initial stage, before storming's conflict or norming's cohesion emerges.

Multiplying the $50,000 loss by the 20% probability yields an EMV of $10,000, which quantifies the risk's average financial exposure for the project budget. This satisfies the stem's requirement to calculate expected monetary value, giving the project manager a defensible figure for contingency reserves and risk prioritisation.

Finish-to-Start defines the successor's start as gated by the predecessor's completion, exactly matching the stem's condition that B begins only after A finishes. The other dependency types (SS, FF, SF) permit overlap or reversed sequencing.

High power combined with high interest identifies stakeholders who can both influence project outcomes and care deeply about results, so they demand the most active engagement. Low-power or low-interest quadrants need only periodic monitoring or minimal communication.

Formal acceptance confirms the customer or sponsor agrees the deliverables meet requirements, authorising closure. Without it the project cannot be signed off or the product transitioned, so obtaining it is a mandatory closure activity alongside handover and lessons learned.

High-power, low-interest stakeholders can influence outcomes but do not engage actively, so the keep-satisfied strategy delivers concise, positive updates that prevent surprises without overloading them. Monitor is for low power, manage closely for high interest, keep informed for low power and interest.

A clear risk description states the uncertain event, its cause and potential effect, so the risk can be understood and assessed. It is fundamental register content, providing the basis for subsequent probability, impact and response planning entries.

Analogous estimation derives duration or cost from the actual figures of a comparable historical project, then scales them for size and complexity differences. Here the manager uses a similar past project's real cost, adjusted for scope variance, satisfying the stem's requirement for a top-down, experience-based estimate rather than bottom-up or parametric calculation.

Activity E can begin as soon as Activity C starts, not after it finishes. That relationship, where the successor's start depends on the predecessor's start, is a Start-to-Start dependency, so SS correctly describes the C-to-E link.

A CPI of 0.85 indicates that for every dollar spent, only 85 cents of value is earned, meaning the project is over budget. An SPI of 1.10 means the project is ahead of schedule, as more work is being accomplished than planned. Together, these metrics show cost inefficiency but schedule efficiency.

Charter approval occurs during Initiating, where the sponsor formally authorises the project and grants the project manager resource allocation authority. This satisfies the stem's requirement for the process group in which the charter gains approval, distinguishing it from Planning, where the project management plan and subsidiary baselines are developed instead.

The project charter is produced during Initiating, where the project is formally authorised and the project manager is assigned. It precedes planning, so it cannot belong to later phases such as Executing, Monitoring and Controlling, or Closing.

Start-to-start (SS) dependency defines exactly this relationship: the successor's start is gated by the predecessor's start, not its completion. It satisfies the stem's constraint that the successor cannot begin until the predecessor has begun, distinguishing it from finish-to-start, where the predecessor must finish first.

With EV ($50,000) below PV ($60,000), the project is behind schedule, and AC ($55,000) exceeding EV means it is over budget. Both variances are negative, so this statement correctly reflects the earned value metrics given.

CPI is earned value divided by actual cost: 50,000 divided by 55,000 equals approximately 0.91. A value below 1.0 indicates the project is over budget for the work completed, since each dollar spent delivered only about 91 cents of earned value.

The path A-B-C-D is the longest: A (3) + B (5) + C (4) + D (2) = 14 days. However, since A and B start concurrently, the path through B and C begins after B completes. Wait—actually the critical path is the longest path: A(3) + B(5) + C(4) + D(2) = 14 days. But A and B are concurrent, so the path through A and E is 3+6=9. The path through A, then C, D would be 3+4+2=9, but C depends on B as well, so C cannot start until both A and B finish. Therefore B (5) is the constraint. Path: B(5) + C(4) + D(2) = 11 days. But A must also finish before C starts. A finishes at day 3, B finishes at day 5. C starts at day 5 and ends at day 9. D starts at day 9 and ends at day 11. So critical path is 11 days.

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.

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.

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.

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.

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.

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.

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 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.

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.

Correct: mitigation reduces probability or impact.

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.

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.

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.

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.

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.

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.

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.

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.