CCNA Project Management Concepts Questions

The sponsor sits above the project manager in authority, so they secure funding, staff and facilities, and escalate issues the team cannot resolve. This directly satisfies the stem's requirement for a key sponsor responsibility: providing resources and clearing obstacles that block delivery.

Closing is the phase where deliverables undergo formal acceptance sign-off and contracted resources are released, satisfying the stem's requirement for both acceptance and resource release. These activities occur after verification in Controlling, confirming the product is complete and the team can be disbanded.

Iterative two-week sprints for software plus sequential hardware procurement combine predictive and adaptive approaches within one fixed budget. That blend of life cycles is precisely what defines a hybrid life cycle, matching the stem's mixed delivery constraint.

A project is a temporary endeavour with a defined start and end, undertaken to create a unique product, service, or result. The stem's one-time mobile application initiative, bounded by fixed budget, schedule, and scope, matches this definition exactly, unlike ongoing operations or programmes.

A hybrid approach combines a predictive, upfront construction plan with iterative design flexibility, satisfying the stem's dual constraint of clear overall planning plus adaptable design. Pure predictive fixes design early; pure agile lacks the upfront construction baseline the project requires.

Lessons learned sessions and document archiving occur during Closing, the final phase of the project life cycle, where deliverables are formally accepted and records are handed over. This satisfies the stem's description of post-completion administrative wrap-up activities.

A project is defined by its temporary nature and constrained by scope, schedule, cost and quality objectives. This distinguishes it from ongoing operations, which are continuous and repetitive rather than bounded by a defined endpoint and deliverables.

A balanced matrix shares authority between the functional manager and the project manager, who holds moderate power over resources. This matches the stem's dual reporting lines and moderate project manager authority, unlike weak or strong matrix variants.

In a functional organization, staff remain under the direct control of their functional managers, who handle performance reviews and daily priorities. The project manager coordinates work but typically has little to no formal authority over team members, relying instead on influence, negotiation, and communication. This matches the scenario exactly, so the project manager must plan to lead through influence rather than positional power.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Predictive (Waterfall) suits stable, well-understood requirements with low expected change because it fixes scope early and progresses through sequential phases. Iterative or agile approaches would add unnecessary overhead when requirements are already clear and unlikely to shift.

Stable, well-understood requirements and a fixed budget suit a predictive (waterfall) approach, where scope is defined upfront and delivered through sequential phases. Its emphasis on early detailed planning and change control directly satisfies the stem's constraint that requirements are unlikely to change.

NPV discounts future cash flows to present value; a positive NPV means the project adds value, while a negative NPV destroys it. Project A's $50,000 exceeds Project B's −$10,000, so selecting A satisfies the NPV-based selection criterion.

The WBS decomposes the total scope into manageable deliverables and work packages, forming the scope baseline. It is produced during planning, after the charter authorises the project, satisfying the stem's requirement for a planning-phase characteristic rather than initiation or execution activity.

Multiplying the $30,000 annual inflow by the 3.791 annuity factor gives a present value of $113,730; deducting the $100,000 initial investment yields $13,730. This satisfies the stem's requirement to discount all five years' cash flows at 10% and subtract the upfront outlay.

In a weak matrix the functional manager controls resource assignment, so the project manager must first negotiate for the specific people and the percentage of their time. Agreeing on allocation and availability up front creates a shared expectation and documents the commitment, which is the standard first step before any escalation becomes necessary.

Gold plating means delivering extra functionality beyond what was agreed. Adding a reporting module that was never specified exceeds the approved scope, consuming budget and schedule without authorisation, which is precisely the definition the question tests.

CPI below 1.0 means costs exceed the earned value, so the project is over budget. SPI above 1.0 means earned value exceeds planned value, so work is ahead of schedule. Both indices together confirm overspending alongside schedule acceleration.

This criterion is measurable because it specifies a quantifiable target (15% increase) and a time frame (six months after go-live). The project charter should include high-level success criteria that can be objectively verified. This option provides a clear metric for evaluating project success, unlike vague qualitative statements. It aligns with the purpose of the charter to define what success looks like for the project.

Predictive suits stable, well-understood requirements where change is unlikely, allowing sequential phases with upfront planning. Collocated, experienced teams reduce the communication overhead that iterative approaches address, so heavyweight change responsiveness adds little value. Fixed scope and low uncertainty let the team plan, execute and control against a defined baseline efficiently.

Three-point estimating uses optimistic, most likely, and pessimistic values to account for uncertainty. When those values are combined as a weighted average, the result is the beta or PERT distribution, which is exactly what the team is computing for each work package. This technique suits the scenario because prior experience makes all three estimates credible.

Predictive methodology fixes scope, schedule and cost baselines early, with requirements fully elicited before build begins. That matches the stated constraint of gathering all requirements up front and locking scope, whereas adaptive approaches deliberately welcome late change.

Executing follows planning because the project management life cycle sequences phases as initiating, planning, executing, monitoring and controlling, then closing. Once baselines for scope, schedule and cost are approved, work begins and deliverables are produced, satisfying the stem's requirement to identify the phase immediately after planning.

A negative NPV means the discounted present value of expected cash inflows is less than the initial investment, so the project destroys value at the required rate of return and should not proceed on financial grounds.

Total float is the amount of time an activity can be delayed without delaying the project finish. A path with three days of float is not critical, so shortening an activity on it by two days consumes no project buffer and leaves the zero-float path, which controls the completion date, unchanged. The project finish is governed by the longest path.

In a weak matrix, functional managers hold primary authority over resources and operational priorities, while the project manager has limited power to negotiate assignments. This structural imbalance explains why operational work consistently overrides project task allocation.

In a weak matrix, functional managers retain primary authority over resources and project decisions, while the project manager acts largely as a coordinator with limited power. This matches the stem's constraints: significant functional control and limited PM authority, distinguishing it from balanced or strong matrices where PM influence increases.

Gold plating occurs when the team adds unrequested features beyond the agreed scope, exactly as described. It satisfies the scenario's constraint of unauthorised extra functionality, consuming budget and time without approval. Unlike scope creep, which is uncontrolled change from stakeholders, gold plating is extra work initiated by the team itself.

The project management plan is the integrated document that describes how the project will be executed, monitored, controlled, and closed, including team structure, communication cadence, and tooling. Because the manager is defining reporting frequency, team organization, and tracking tools as a single approved baseline for execution, this is exactly the artifact being built.

Closing secures formal sign-off of deliverables through the acceptance process, then releases team members, budget and equipment. It satisfies the stem's twin requirements: obtaining formal acceptance and freeing project resources, which occur only after verification confirms the deliverables meet specification.

Closing the procurement requires verifying that deliverables meet contractual terms and obtaining formal acceptance, often through a signed acceptance document. This evidence supports releasing final payment and terminates the vendor's obligations. It directly addresses the sponsor's need for assurance that requirements were met before funds are disbursed.

Project A delivers the greater net present value, $50,000 against $40,000, so it adds more value once future cash flows are discounted to present terms. The stem explicitly asks for selection based on NPV, making payback period irrelevant here despite Project B's faster two-year recovery.

Formal acceptance is a closing activity because it confirms the customer agrees the deliverables meet requirements and marks the point at which the product transitions to the customer. It is documented in the final acceptance record and often triggers final payment. Performing acceptance during execution would leave the project without a defined endpoint and could expose the seller to unresolved scope disputes.

Gold plating is the deliberate addition of features beyond the agreed scope, consuming budget and schedule without customer request or approval. It matches the stem's scenario precisely, differing from scope creep, which is uncontrolled incremental change rather than developer-initiated extras.

A balanced matrix gives the project manager moderate authority while functional managers retain control of resources, matching the shared resource management described. Neither the weak nor strong matrix produces this equal split of power between both managers.

A balanced matrix grants the project manager moderate authority while resource control is shared equally with the functional manager, matching the stem's dual-reporting arrangement. Unlike a strong matrix, where the project manager holds dominant resource control, or a weak matrix, where the functional manager prevails, this structure splits power evenly between both managers.

Discounting each inflow at 10% gives $27,273 + $33,058 + $37,566 = $97,897; subtracting the $100,000 outlay yields -$2,103. The negative NPV means the project returns less than the 10% discount rate, so it destroys value against that hurdle.

A negative NPV means the project's discounted future cash inflows are worth less than the initial investment, destroying value. Rejecting it is the financially sound recommendation, satisfying the stem's constraint that the sponsor act on the -$15,000 figure.

Net Present Value discounts all future cash flows to today's value, directly satisfying the steering committee's requirement to maximise return over time. Unlike payback period, which ignores cash flows beyond the break-even point, NPV captures total long-term profitability across each project's full lifespan, making it the definitive metric for comparing financial viability.

Assigning selected team members to activities and verifying their availability is part of Acquire Resources. Once negotiations succeed, the project manager records the assignment against the schedule and confirms that the individuals can support the planned dates. This finalizes the acquisition step for the scarce skill set and is distinct from the planning activities that precede it.

Controlling quality is a Monitoring and Controlling process that involves monitoring and recording the results of quality activities to assess performance and recommend necessary changes. It ensures that project deliverables meet the required quality standards. This activity is performed throughout the project to identify and correct quality issues, making it a key part of the Monitoring and Controlling process group.

In a functional organisation, authority rests with functional managers and the project manager acts largely as coordinator, holding minimal power over resources and priorities. This structure therefore gives the project manager the least authority of the options.

Formal acceptance of the final deliverable is the trigger that allows the project to move into closing. Until the customer provides documented sign-off, the project cannot be considered complete, and contractual or payment obligations may remain open. The project manager should secure this acceptance first so that subsequent activities such as archiving, releasing resources, and capturing lessons learned reflect a verified, accepted outcome rather than an unconfirmed one.

The project charter formally authorises the project and names the project manager, satisfying the initiation-phase requirement for documented approval. It also records the high-level scope, budget and timeline the sponsor supplied, distinguishing it from the detailed project management plan, which is produced later during planning.

Risk response planning develops options and actions to reduce threats and enhance opportunities. The team has a concrete threat, the API deprecation, and is generating and weighing three distinct strategies: avoiding the dependency through a rewrite, transferring or sharing the problem through vendor negotiation, and mitigating by accelerating the cutover. That selection process is exactly risk response planning.

Hybrid suits this construction project because the scope is well-defined yet minor changes remain welcome. Predictive planning locks the baseline schedule and budget, while agile elements absorb small customer adjustments during execution. Pure waterfall would resist those changes; pure agile would waste effort re-planning stable, well-understood work.

Because the component is already in production and the defect blocks acceptance, the work required to remediate it must be authorized rather than performed informally. Reopening the project, replanning the affected work, and securing change control board or sponsor approval for the revised baseline restores legitimate control over scope, schedule, and cost. This keeps the project's records accurate and ensures the customer's acceptance decision is based on verified results.

In a functional organisation, work is grouped by department and the functional manager controls budgets, assignments and priorities. The project manager coordinates across functions with little or no formal authority, giving the least authority over project resources of any structure.

Uncontrolled changes, such as a stakeholder adding unapproved features, constitute scope creep. Because the request bypasses the formal change control process, the project manager cannot assess its effect on the schedule and budget constraints, which is precisely the risk described in the stem.

Crashing adds resources to critical-path activities, while fast-tracking overlaps sequential activities. Both techniques target the critical path to shorten total duration, so each is a schedule compression method applied when the project is behind schedule.

Payback divides initial investment by annual return: $50,000 ÷ $15,000 = 3.33 years for Project A, versus $80,000 ÷ $22,000 = 3.64 years for Project B. Project A recovers its investment sooner, satisfying the stem's payback criterion.

Ground rules such as meeting etiquette, expected response windows, and channel usage are core team charter content. For a team spread across three time zones, these agreements prevent misunderstandings about availability and set shared expectations for communication. They are established by the team during the forming stage and documented in the charter so behavior is governed by consensus rather than assumption.

Championing the project is a core sponsor responsibility, satisfying the stem's requirement for typical sponsor duties. The sponsor secures executive backing, removes organisational blockers and advocates for resources at senior level, distinct from the project manager's day-to-day delivery duties. This authority-based advocacy is what the scenario's role definition demands.

In a fixed-price contract, the price is set, but changes in scope typically require a contract amendment to adjust the price and terms. The CCB approval is an internal step, but the customer must agree to the change and any associated cost. This option correctly reflects that a contract modification is necessary to formalize the change and ensure the seller is compensated for additional work.

When time and cost are constrained, scope is the variable the project manager can most realistically adjust. Working with the sponsor and stakeholders to descope or defer lower-priority features allows the project to meet the regulatory deadline within the capped budget. This is a recognized trade-off approach in the triple constraint and keeps the project aligned with its most critical business objective rather than attempting an impossible delivery.

A program coordinates related projects to obtain benefits not available from managing them individually. This matches the stem's definition, distinguishing it from a portfolio, which groups projects aligned to strategic objectives rather than interdependent ones.

Gold plating occurs when the team adds functionality beyond the agreed requirements, exactly as described. It satisfies the scenario's constraint of unsanctioned scope addition, consuming budget and time without customer approval. Unlike scope creep, which is stakeholder-driven, gold plating is initiated internally by the project team itself.

Closing processes verify that all required work across all process groups is complete, obtain final acceptance, archive project documents, and capture lessons learned for the organizational process assets. Compiling the final report and archiving records is precisely this activity, and it also releases team members and closes contracts so the organization can measure realized value later.

NPV measures absolute financial value in today's currency, so Proposal A's $50,000 exceeds Proposal B's $30,000. The stem explicitly asks which is more beneficial based on NPV, making the shorter payback period irrelevant to this criterion.

Predictive methodology fixes scope, schedule and cost baselines up front and controls changes through formal approval. With clearly defined requirements and minimal expected change, this sequential approach satisfies the stem's stability constraint better than adaptive alternatives.