CCNA Project Management Fundamentals and Core Concepts Questions

Monitoring and Controlling covers tracking, reviewing and regulating project progress and performance, including performing Integrated Change Control. Document changes and approvals flow through that process group, ensuring only approved revisions are baselined, which satisfies the requirement to control changes to project documents.

Any change affecting cost or schedule must pass through integrated change control. Submitting the request to the CCB lets that body evaluate the 15% cost increase and three-week delay against the sponsor's budget concerns, then approve, reject or defer it formally.

The project manager should first assess how the proposed change affects scope, schedule, cost, quality, and risk. This evaluation provides necessary information for the change control process. Without understanding the impact, the project manager cannot make informed decisions or recommendations to the change control board. This step is part of performing integrated change control, ensuring changes are managed proactively.

An SPI of 0.85 indicates that the project is only achieving 85% of the planned schedule performance, meaning it is behind schedule. A CPI of 1.10 indicates that the project is getting $1.10 of work for every $1 spent, so it is under budget. This combination is correctly interpreted as behind schedule and under budget.

The critical path is the longest path through the project network diagram, and it determines the shortest possible time to complete the project. Any delay in a critical path activity will delay the project. It is calculated using the critical path method, which considers activity durations and dependencies. This is a fundamental concept in schedule management.

Projects are temporary endeavours with defined start and end dates, producing a unique deliverable, whereas operations are ongoing and repetitive, sustaining the business. This directly satisfies the stem's request to distinguish the two: temporality and uniqueness separate projects from continuous operational work.

CPI of 0.8 means every unit of currency returns only 0.8 of planned value, so costs exceed the budget baseline. SPI of 1.2 means earned value outpaces planned value, so work is progressing faster than the schedule baseline. Both indices are measured against the same earned value baseline.

The project charter is the document issued by the sponsor 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 created during the initiation phase and is essential before any project work begins. It also links the project to the strategic objectives of the organization.

The critical path method calculates the longest path through the network and the earliest and latest start and finish dates for activities. Running the forward pass with no resource constraints yields the shortest possible total duration if all activities start as early as possible. This directly answers the sponsor's question about total duration under unconstrained conditions.

The project charter formally authorizes the project's existence and grants the project manager the authority to apply organizational resources to project activities. It is issued by the sponsor or initiating entity and serves as the foundation for detailed planning. Without a charter, the project lacks official sanction and the project manager may lack the power to allocate resources effectively.

Transitioning the completed product to the group that will operate and maintain it is a key closing activity. It ensures the deliverable is not orphaned after the project team disbands and that support responsibilities are formally handed over. This transition, sometimes called turnover, includes communicating relevant documentation and knowledge. It aligns with the sponsor's request because closure is not complete until the product is accepted and successfully transitioned.

Crashing shortens the critical path by adding resources, such as extra staff or overtime, to critical activities. It trades increased cost for reduced duration, directly addressing the behind-schedule constraint where activities sit on the critical path.

Identifying a required vendor for a critical component occurs while developing the project management plan and its subsidiary plans, such as procurement and resource management. This work sits squarely within the Planning process group, satisfying the stem's "during project planning" constraint rather than Executing, Monitoring and Controlling, or Initiating.

The PERT weighted average is (optimistic + 4 × most likely + pessimistic) ÷ 6, giving (4 + 24 + 12) ÷ 6 = 40 ÷ 6 ≈ 6.67 days. Weighting the most likely estimate fourfold accounts for expected variability in the activity's duration.

In a matrix organisation, functional managers retain line authority over the people in their departments, so they typically control who is assigned to project work and how that work is prioritised against departmental duties. The project manager coordinates the work but usually negotiates rather than directs resource allocation.

Time is one of the three classic project constraints, bounding the schedule within which deliverables must be completed. Alongside cost and scope, it forms the triple constraint that project managers continuously balance, since compressing the timeline directly affects both the resources required and the scope achievable.

The project life cycle spans initiation to closure, and its defining characteristics derive from projects being temporary, with definite start and end, and unique, producing a distinct deliverable. This constraint distinguishes project work from ongoing operational activities that repeat indefinitely.

In a projectized structure, team members report directly to the project manager, who controls resources and priorities. This grants the project manager a high level of authority, distinguishing it from functional or matrix structures where power is shared with functional managers.

Because functional managers control resource allocation and workload in a functional organization, the project manager must negotiate with the appropriate functional manager to obtain the extra hours. This respects the reporting structure and uses the influence and coordination skills expected of a project manager with limited authority. Securing the manager's agreement also makes the commitment more durable than an informal request to the designer.

The project charter is the document that formally authorises the project's existence and grants the project manager authority to commit organisational resources. Business cases and plans lack that sanctioning power, so the charter uniquely satisfies the stem's requirement for formal authorisation and resource authority.

Identifying stakeholders during initiation captures who is affected by or can influence the project, along with their expectations, interests and power. This understanding shapes engagement planning and communication, satisfying the purpose of early identification before requirements and scope are finalised.

In a matrix structure, staff report to both a functional manager and a project manager, so securing personnel requires negotiation rather than direct assignment. This dual-reporting authority split is the defining constraint that shapes resource allocation and creates competing priorities for the project manager.

The organisational policy makes the signed charter a mandatory precondition, so the team's authorisation to begin is gated on both signatures. Until the sponsor and functional manager sign, no project work can legitimately commence, regardless of the team's readiness or availability.

Following integrated change control assesses the requested feature's impact across cost, schedule, scope and quality before any rework begins, satisfying the need to minimise disruption to completed deliverables and their inter-dependencies. It routes the request through the change control board for documented approval or rejection, preventing unapproved scope creep during execution.

Re-estimating against the reduced capacity quantifies the schedule impact before any stakeholder communication, satisfying Alex's need to determine the delivery-date effect. Losing two developers lowers velocity, so revised estimates convert that lost throughput into a concrete forecast the product owner requires.

Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. Projects are temporary and produce unique deliverables. Operations management, in contrast, is concerned with the ongoing production of goods or services. This distinction is fundamental and is explicitly defined in the PMBOK Guide.

The risk report is a documented output of Identify Risks, presenting overall risk exposure, prioritised individual risks and sources of uncertainty. It satisfies the process output requirement because it consolidates risk data for subsequent analysis and planning.

In agile, changes are welcomed and managed through the product backlog. The product owner is responsible for prioritizing backlog items, and the team pulls work based on capacity. Adding the feature to the backlog allows it to be considered alongside other work, and the product owner can reprioritize based on value. This approach respects agile principles and the product owner's role.

Operations are ongoing, repetitive activities delivering the same product or service continuously, such as helpdesk support or manufacturing. This contrasts with projects, which are temporary and unique, satisfying the stem's requirement to distinguish the two.

Acceptance means acknowledging the risk and choosing to take no proactive action, retaining the potential 20% cost increase should it occur. Because the probability is low, the project manager deliberately tolerates the risk without mitigation, transfer or avoidance, matching the stem's stated decision.

In a weak matrix, the project manager lacks formal authority over functional staff, so legitimate, reward and coercive power are unavailable. Expert power derives from technical knowledge and credibility, which earns voluntary cooperation from team members who respect the manager's competence.

Progressive elaboration means project details are developed and refined iteratively as understanding grows, rather than fully defined at initiation. This distinguishes projects from routine operations, which follow stable, repeatable processes, and satisfies the characteristic of incremental planning under uncertainty.

Objective success criteria must be measurable and verifiable against defined standards. Linking acceptance to specific compliance test results and target dates allows independent verification after closure rather than relying on subjective impressions. This approach ties the project's outcome to documented evidence, such as audit findings or test reports, which is exactly what an independent reviewer would examine to confirm the upgrade achieved its intended regulatory purpose.

Cost variance equals earned value minus actual cost: $25,000 − $40,000 = −$15,000. The negative result signals the project is over budget by $15,000 at month 2. Planned value is irrelevant to this calculation, so the $30,000 figure is excluded.

Sequence Activities sits in the Planning process group, where dependencies between activities are identified and documented using techniques such as precedence diagramming. This satisfies the stem's requirement by naming a process performed during planning rather than initiation, execution, monitoring or closing.

The concrete fails the contractual strength grade, so Maria must halt affected work and require conforming material. Supplier claims about generic industry standards do not override the project specifications. Stopping work prevents rework and satisfies the fixed budget and schedule constraints.

Scope defines the boundaries of the project and is a key constraint.

Agile is ideal for projects with uncertain or evolving requirements because it embraces change and delivers value incrementally. Through iterative development and frequent stakeholder feedback, the team can adapt to new insights. This approach aligns with the sponsor's desire for quick value delivery and flexibility, making it the most suitable choice for this research project.

Adding resources to critical path tasks shortens their duration through crashing, directly reducing total project duration. Only critical path activities affect the finish date, so this addresses the schedule variance, whereas adding resources elsewhere would not recover time.

Planning is where the project management plan and its subsidiary plans—including the schedule and resource management plan—are developed. The sponsor's request for detailed scheduling and resource assignment is exactly the work of Planning. This process group establishes scope, time, cost, and resource baselines before execution, so it is the correct group for the described activities.

The stakeholder register is a project document that identifies the people, groups, or organizations that could impact or be impacted by the project. It includes information such as their interests, involvement, dependencies, influence, and potential impact on project success. This is exactly what the sponsor requested, making it the correct choice.

A RACI-format responsibility assignment matrix maps each task to who is Responsible, Accountable, Consulted and Informed, removing ambiguity about ownership. This directly resolves the duplicated work and missed tasks caused by unclear roles and responsibilities across the project team.

In a matrix organisation, the project manager owns the project management plan, integrating scope, schedule, cost and risk baselines. During planning, producing this plan is the primary responsibility, while functional managers handle resource allocation and technical supervision of shared staff.

Evaluating the impact on scope, schedule, and cost is the documented first step before a change request reaches the change control board. The change management plan requires this impact analysis so the board can make an informed approve, reject, or defer decision.

Analysing the critical path determines whether the two-week concrete delay genuinely extends project completion, since only critical activities drive the finish date. With no schedule reserve available, the project manager must then evaluate recovery options such as crashing, fast-tracking or resequencing. This satisfies the stem's constraint by quantifying impact before committing to corrective action.

Change impact analysis evaluates how the requested feature affects scope, schedule, cost, and risk before any decision. It is the prerequisite step that gives the project manager and change control board the information needed to approve, defer, or reject the request, rather than immediately altering the approved baseline.

The project charter formally authorizes the project and gives the project manager authority to apply organizational resources to project activities. It is issued by the sponsor or initiating entity. For the marketing campaign, the charter is the document that officially starts the project and empowers the project manager.

Temporariness and uniqueness are the defining characteristics of a project. The promotional video campaign has a clear beginning and end tied to the holiday launch, and the resulting campaign deliverable is unique rather than repetitive. Because the team is released after the deadline, the effort does not continue indefinitely, which is exactly what distinguishes a project from ongoing operational work.

The project manager must first perform integrated change control by assessing how the added feature affects scope, schedule, cost and resources. Only then can a formal change request be submitted to the change control board for approval or rejection.

The WBS decomposes all project deliverables into work packages, so nothing required by the scope statement is omitted and nothing outside it is included. This complete hierarchical decomposition is what defines and confirms the total scope baseline.

The cost baseline is a time-phased budget that is used to measure, monitor, and control overall cost performance on the project. It is a component of the project management plan and is developed as part of the Cost Management knowledge area.

The Create WBS process involves subdividing project deliverables and project work into smaller, more manageable components called work packages. This decomposition allows for better estimation, scheduling, and control. It is performed during the planning phase and results in a WBS that defines the total scope of the project. The work packages at the lowest level can be estimated and managed effectively.

In a functional organisation the functional manager controls resource allocation, and escalation has already failed. Negotiating partial release or a qualified replacement secures some capacity without further confrontation, protecting the fixed four-week deadline while respecting that manager's authority over operational priorities.

The issue log records problems, their owners, and resolution status, so a deployment error should be documented there first to track and escalate it. This satisfies the stem's requirement to identify which project document is updated first when an error occurs.

Missing test results breach the quality management plan, so the project manager records the nonconformity in the issue log and initiates corrective action to close the documentation gap. This restores compliance with the regulated quality requirements rather than merely reporting or ignoring the defect.

Quantitative risk analysis models uncertainty numerically, typically via Monte Carlo simulation, producing a defensible contingency figure rather than an arbitrary 10%. This satisfies the stem's high-uncertainty constraint by deriving the reserve from the project's actual risk exposure and confidence level.

The project charter authorises the project and names the project manager, but detailed scheduling belongs to later planning artefacts such as the schedule baseline. Defining the detailed project schedule is therefore not a charter purpose, making it the exception sought.

Critical chain project management buffers tasks and removes multitasking, directly reducing unplanned work that delays the critical path. It satisfies the stem's constraint by protecting the schedule through resource-levelled buffers rather than padding individual task estimates.

The stakeholder register is created during Initiating through stakeholder identification and analysis, so it qualifies as an Initiating output. It records each stakeholder's interests, influence and engagement needs, distinguishing it from Planning documents such as the communications management plan.

Reviewing the requirements documentation with the stakeholder clarifies what is actually in scope before any change is considered. This addresses the concern at its source, satisfying the need to understand the stakeholder's specific issue before deciding whether scope adjustment is warranted.

The project charter formally authorizes the existence of the 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 and names the project manager. Because the scenario asks what authorizes the project and empowers the manager before planning, the charter is the document that satisfies both conditions.

BCR measures return per unit invested, so Proposal B's 1.5 delivers greater benefit per pound than A's 1.2, directly satisfying the stated goal of maximising return on investment under limited funds. The longer four-year payback is secondary to that constraint.

A milestone represents a significant point or event, carrying no effort or duration, so it is modelled as a zero-duration task. This distinguishes it from activities, which consume time and resources, and satisfies the definition of a schedule checkpoint.

The risk management plan is the sole output of Plan Risk Management, documenting methodology, roles, budget, timing and risk categories. It directly guides all subsequent risk processes, satisfying the stem's requirement for this process's key deliverable.

The project manager should first document the change request and then submit it to the change control board (CCB) for evaluation. The CCB reviews the impact on scope, schedule, cost, and other constraints and decides whether to approve, reject, or defer the change. This ensures that changes are managed systematically.

A RACI matrix maps each task to who is Responsible, Accountable, Consulted and Informed, directly resolving the ambiguity the team is spending time clarifying. It assigns explicit ownership per deliverable, which is the artefact's core purpose.

A configuration management system is a subset of the project management information system that includes tools and processes to manage and control changes to project documents and deliverables. It provides version control, change tracking, and access to the latest documents. In this scenario, it ensures distributed team members access current documents and that changes are tracked, meeting the project manager's needs.

The project charter is produced during Initiating, the process group that authorises the project and formally names the project manager. It precedes Planning, where the charter's high-level scope is elaborated into baselines and subsidiary plans.

The critical path method is a schedule network analysis technique used to determine the early start and early finish dates, as well as late start and late finish dates, for all activities. It calculates the longest path through the network and identifies the critical path. This technique directly provides the early start and early finish dates required in the scenario.

The project scope statement describes the project scope, major deliverables, assumptions, and constraints. It provides the baseline for evaluating changes. In this scenario, the project manager should consult the project scope statement first to understand what is included and excluded, and to assess the impact of the proposed new feature on the project constraints.

The plan integrates subsidiary plans specifying how work is performed and how performance is tracked and controlled. This execution, monitoring and control definition is a core benefit, giving the project manager an approved, documented approach that satisfies the stem's requirement.

Time and cost limitations are classic project constraints. The six-month deadline and $200,000 budget restrict the team's options and require careful planning to ensure the project stays within these boundaries. Recognizing them as constraints helps the project manager prioritize and make trade-offs, such as adjusting scope if necessary, to meet these fixed limits.

The stakeholder engagement plan is a direct output of Plan Stakeholder Engagement, documenting strategies for involving stakeholders based on their needs, interests and influence. It satisfies the stem's requirement by providing the formal, written approach that guides how the project team will communicate and engage throughout the project lifecycle.

Control Costs is the Monitoring and Controlling process that tracks actual spend against the cost baseline, analyses variances and approves corrective action. It directly addresses the stem's constraint of actual cost consistently exceeding planned cost.