CCNA Business Environment — Strategy and Value Questions

Matchingmedium

Match each project document to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Authorizes the project and assigns the project manager

Defines how the project is executed, monitored, and controlled

Hierarchical decomposition of total project work

List of identified risks, their analysis, and response plans

Records knowledge gained during the project

Why these pairings

The correct matches are: Project Charter (business case and authorisation), Scope Statement (detailed scope and acceptance criteria), WBS (work decomposition), and Risk Register (risk tracking). Common confusions involve swapping the project charter with the scope statement or risk register.

Practice this question →

MCQmedium

You are the project manager for a multinational corporation that is launching a new software product. The organization's strategic goal is to increase market share in emerging markets by 15% within the next two years. The project has completed the planning phase, and you are about to start execution. During a stakeholder meeting, the product owner insists on adding a feature that is popular in developed markets but has not been validated for emerging markets. The product owner argues that this feature will differentiate the product, but the development team estimates it will add three months to the schedule and increase costs by 20%. The sponsor is concerned about the budget and timeline. You have reviewed the business case, which does not mention this feature. What should you do?

A.Escalate the issue to the project sponsor and ask for a decision.

B.Accept the feature because the product owner is responsible for the product vision.

C.Add the feature to the backlog and proceed as requested to satisfy the product owner.

D.Conduct a cost-benefit analysis and assess alignment with the strategic goal. If it does not align, recommend against it and proceed with the original scope. If it aligns, submit a change request.

AnswerD

This approach ensures the feature is evaluated for value and follows proper change management.

Why this answer

It follows the PMI framework for managing scope changes: first, evaluate the proposed feature against the business case and strategic goal (increasing market share in emerging markets by 15% within two years). A cost-benefit analysis will determine if the feature delivers value in the target market; if not, the recommendation is to proceed with the original scope. If it does align, a formal change request is required to adjust the baseline schedule and budget, ensuring the sponsor and other stakeholders can make an informed decision.

Exam trap

The trap here is that candidates may assume the product owner's authority is absolute (leading to Option B) or that escalation is the only path (Option A), without recognizing the project manager's duty to first analyze the change's strategic fit and then follow the formal change control process.

How to eliminate wrong answers

Option A is wrong because escalating directly to the sponsor without first analyzing the feature's alignment with the strategic goal abdicates the project manager's responsibility to provide data-driven recommendations. Option B is wrong because the product owner is responsible for the product vision, but that does not override the need for scope validation against the business case and strategic objectives, especially when the feature adds significant cost and schedule impact. Option C is wrong because adding the feature to the backlog and proceeding without a formal change request violates the project's change control process and ignores the sponsor's concerns about budget and timeline, leading to uncontrolled scope creep.

Practice this question →

MCQmedium

A company is implementing a new customer relationship management (CRM) system. The project manager wants to ensure that the project delivers value aligned with the organization's strategic goals. Which document should the project manager reference to confirm the alignment?

A.Project management plan

B.Scope statement

C.Business case

D.Project charter

AnswerC

The business case is the foundational document that provides the necessary information from a business standpoint to determine if a project is worth the required investment. It comprehensively outlines the strategic objectives, the problem or opportunity being addressed, a detailed financial analysis, and the overall justification for the project. Crucially, it demonstrates how the project aligns with and contributes to the organization's strategic goals and objectives, making it the primary tool for strategic justification.

Why this answer

The business case documents the justification for the project, including alignment with organizational strategy, expected benefits, and ROI. For a CRM implementation, the business case would confirm that the system supports strategic goals like improving customer retention or sales efficiency, making it the correct reference for value alignment.

Exam trap

The trap here is that candidates often confuse the project charter (which authorizes the project) with the business case (which justifies it), leading them to select the charter when the question specifically asks about confirming strategic alignment and value delivery.

How to eliminate wrong answers

Option A is wrong because the project management plan describes how the project will be executed, monitored, and controlled, but it does not justify why the project aligns with strategic goals. Option B is wrong because the scope statement defines what is included and excluded in the project deliverables, not the strategic rationale or value proposition. Option D is wrong because the project charter authorizes the project and assigns the project manager, but it typically references the business case for strategic alignment rather than providing that justification itself.

Practice this question →

Multi-Selecthard

Which THREE of the following are key considerations when evaluating the strategic value of a proposed project during portfolio selection? (Choose three.)

Select 3 answers

A.Strategic alignment

B.Return on investment (ROI)

C.Organizational culture

D.Resource availability

E.Risk exposure

AnswersA, B, E

Strategic alignment is a paramount criterion for project selection, ensuring that the proposed project directly contributes to the organization's overarching strategic goals, vision, and mission. Projects lacking clear alignment with strategic imperatives are unlikely to receive funding or executive sponsorship, as they would divert valuable resources from core business priorities. This evaluation ensures the project's outputs and outcomes will advance the organization towards its desired future state.

Why this answer

Strategic alignment (A) is a key consideration because it ensures the proposed project directly supports the organization's overarching goals and competitive strategy, which is the primary filter in portfolio selection. Without alignment, even a profitable project can divert resources from more critical strategic initiatives, leading to suboptimal portfolio value.

Exam trap

The trap here is that candidates often confuse operational feasibility factors (like culture or resource availability) with strategic value criteria, which are specifically about alignment, financial return, and risk-adjusted contribution to organizational goals.

Practice this question →

Drag & Dropmedium

Sequence the steps for performing a qualitative risk analysis.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Qualitative analysis involves identifying risks, assessing probability and impact, prioritizing, categorizing, and updating the register.

Practice this question →

Drag & Dropmedium

Order the steps for performing project quality assurance.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Quality assurance: identify standards, plan, audit, improve, and document lessons.

Practice this question →

MCQeasy

A project manager is reviewing lessons learned from a completed project. The project delivered on time and on budget but did not achieve the expected market share increase. Which document would most likely explain this discrepancy?

A.Benefits realization plan

B.Work breakdown structure

C.Project charter

D.Risk register

AnswerA

The Benefits Realization Plan is a crucial document that outlines how and when the project's intended benefits will be measured, monitored, and sustained after project completion. It defines the metrics, timing, and responsibilities for achieving these benefits, making it the primary tool for evaluating the actual achievement of value against initial expectations during a lessons learned review.

Why this answer

The benefits realization plan defines how and when the project's expected benefits (such as market share increase) will be achieved and measured. Since the project delivered on time and on budget but missed the market share target, the benefits realization plan would contain the specific metrics, assumptions, and measurement methods that explain why the expected business value was not realized despite successful delivery.

Exam trap

PMI often tests the misconception that the project charter or risk register captures all business outcomes, but the benefits realization plan is the specific document that tracks and explains the achievement (or lack thereof) of expected business value after project completion.

How to eliminate wrong answers

Option B is wrong because the work breakdown structure (WBS) decomposes project deliverables and work packages, not business outcomes or benefit measurements; it cannot explain a discrepancy in market share. Option C is wrong because the project charter authorizes the project and states high-level business needs, but it does not contain detailed benefit measurement criteria or post-implementation tracking. Option D is wrong because the risk register documents identified risks and responses, not the planned benefit realization or the gap between expected and actual business value.

Practice this question →

MCQmedium

An organization is transitioning from a traditional waterfall approach to agile. The project manager is tasked with leading a pilot agile project. During sprint planning, the product owner prioritizes features based on stakeholder feedback. However, the team is concerned that the prioritized features do not align with the organization's strategic goals. What should the project manager do?

A.Request a change to the project charter

B.Facilitate a meeting with the product owner and key stakeholders to realign priorities

C.Tell the team to trust the product owner's decisions

D.Escalate the issue to the project sponsor

AnswerB

This is the most effective approach because it directly addresses the perceived misalignment by engaging the primary decision-maker (Product Owner) and those affected by the strategic goals (key stakeholders). Facilitating a collaborative discussion allows for transparent review of the backlog against strategic objectives, fostering shared understanding and enabling informed adjustments to prioritization. This ensures the team's efforts are focused on delivering maximum value aligned with organizational strategy.

Why this answer

The project manager's role in an agile transition includes ensuring alignment between the sprint backlog and the organization's strategic goals. By facilitating a meeting with the product owner and key stakeholders, the PM enables a collaborative re-prioritization that respects both stakeholder feedback and strategic objectives, which is a core agile principle of continuous stakeholder engagement.

Exam trap

The trap here is that candidates may assume the product owner has absolute authority over priorities (Option C) or that any misalignment requires immediate escalation (Option D), when in fact the PM's role is to facilitate alignment through collaboration, not to override or bypass the product owner's decisions.

How to eliminate wrong answers

Option A is wrong because requesting a change to the project charter is premature and overly formal; the issue is about sprint-level priority alignment, not a fundamental change in project scope or objectives. Option C is wrong because telling the team to trust the product owner's decisions ignores the valid concern about strategic misalignment, which could lead to delivering features that do not support business goals. Option D is wrong because escalating to the project sponsor bypasses the collaborative resolution process that agile emphasizes, and the PM should first attempt to resolve the conflict at the team and stakeholder level.

Practice this question →

MCQhard

A project manager is leading a digital transformation initiative. Midway through the project, a new regulation is introduced that affects the product's compliance requirements. The project sponsor is concerned about potential scope creep and delays. What should the project manager do first?

A.Escalate the issue to the project sponsor for direction

B.Update the risk register with the new regulation as a threat

C.Submit a change request to modify the project scope

D.Conduct an impact analysis of the regulation on the project

AnswerD

Conducting an impact analysis of the new regulation on the project is the most appropriate and foundational first step. This involves systematically evaluating how the regulation might affect the project's scope, schedule, budget, resources, quality requirements, and existing risks. This comprehensive understanding provides the necessary data to make informed decisions, develop appropriate response strategies, and then proceed with subsequent actions like updating registers, submitting change requests, or escalating with well-defined recommendations.

Why this answer

D is correct because the first step when a new regulation emerges is to analyze its impact on the project's scope, schedule, cost, and compliance. Without an impact analysis, the project manager cannot determine whether a change request, risk update, or escalation is appropriate. This aligns with the PMBOK Guide's 'Perform Integrated Change Control' process, which requires assessing the effects of any proposed change before taking further action.

Exam trap

The trap here is that candidates often jump to updating the risk register or submitting a change request without first performing the mandatory impact analysis, confusing a reactive step with the correct proactive analysis required by the PMBOK Guide's change control process.

How to eliminate wrong answers

Option A is wrong because escalating to the sponsor without first understanding the regulation's impact bypasses the project manager's responsibility to analyze and recommend. Option B is wrong because updating the risk register as a threat is premature; the regulation may present an opportunity (e.g., competitive advantage) or require a change, not just a risk response. Option C is wrong because submitting a change request without an impact analysis violates the change control process; the impact must be assessed to inform the change request's justification and details.

Practice this question →

Multi-Selectmedium

Which TWO of the following are typically included in a business case? (Choose two.)

Select 2 answers

A.Risk register

B.Cost-benefit analysis

C.Alignment to strategic objectives

D.Detailed project schedule

E.Communication plan

AnswersB, C

Cost-benefit analysis is a key component of a business case.

Why this answer

The business case is a foundational document used to justify the initiation of a project or investment. It must demonstrate that the project is worthwhile, which is why a cost-benefit analysis (Option B) is a core component, quantifying the financial viability. Additionally, the business case must show how the project aligns with the organization's strategic objectives (Option C) to ensure it supports the broader business goals and receives executive sponsorship.

Exam trap

The trap here is that candidates often confuse the business case with the project charter or other planning documents, mistakenly thinking that detailed execution artifacts like the risk register or schedule are included in the business case, when in fact the business case is a high-level justification document created before the project is formally authorized.

Practice this question →