Scenario practice questions

You are preparing a portfolio performance report for the Portfolio Governance Board. The board has requested a forward-looking view of how changes in strategic priorities might affect the portfolio's value. Which technique should you use to provide this insight?

Trap 1: SWOT analysis of the portfolio's internal and external environment.

SWOT analysis identifies strengths, weaknesses, opportunities, and threats, but it is qualitative and not designed to quantify how changes in strategic priorities affect portfolio value. The board requested a forward-looking, value-oriented view. While SWOT can inform strategy, it does not provide the quantitative scenario modeling needed to understand value impacts. Thus, it is not the best technique for this specific request.

Trap 2: Monte Carlo simulation of component completion dates.

Monte Carlo simulation models schedule uncertainty and can forecast completion probabilities, but it does not directly link strategic priority changes to portfolio value. The board wants to understand how value might change if priorities shift, which requires scenario analysis that incorporates strategic alignment and benefit realization. Monte Carlo is useful for schedule risk but insufficient for strategic value forecasting.

Trap 3: Earned value management (EVM) analysis across all components.

EVM provides historical performance data on cost and schedule, but it is backward-looking and does not forecast the impact of strategic priority changes. The board requested a forward-looking view of value under different strategic scenarios. EVM would not address how shifting priorities might alter portfolio value. Therefore, it is not the appropriate technique for this request, though it remains valuable for performance measurement.

A
SWOT analysis of the portfolio's internal and external environment.
Why it fails: SWOT analysis identifies strengths, weaknesses, opportunities, and threats, but it is qualitative and not designed to quantify how changes in strategic priorities affect portfolio value. The board requested a forward-looking, value-oriented view. While SWOT can inform strategy, it does not provide the quantitative scenario modeling needed to understand value impacts. Thus, it is not the best technique for this specific request.
B
Monte Carlo simulation of component completion dates.
Why it fails: Monte Carlo simulation models schedule uncertainty and can forecast completion probabilities, but it does not directly link strategic priority changes to portfolio value. The board wants to understand how value might change if priorities shift, which requires scenario analysis that incorporates strategic alignment and benefit realization. Monte Carlo is useful for schedule risk but insufficient for strategic value forecasting.
C
Scenario analysis that models portfolio value under different strategic priority shifts.
Scenario analysis allows the portfolio manager to create multiple future states based on different strategic priorities and assess how portfolio value, alignment, and risk would change. This forward-looking technique directly addresses the board's request by quantifying the impact of priority shifts on benefits and investment. It supports informed decision-making and is a key tool in portfolio performance management.
D
Earned value management (EVM) analysis across all components.
Why it fails: EVM provides historical performance data on cost and schedule, but it is backward-looking and does not forecast the impact of strategic priority changes. The board requested a forward-looking view of value under different strategic scenarios. EVM would not address how shifting priorities might alter portfolio value. Therefore, it is not the appropriate technique for this request, though it remains valuable for performance measurement.

Question 2mediummultiple choice

A portfolio manager is designing the governance model for a new portfolio. The organization wants to ensure that component decisions are made at the right level and that strategic alignment is maintained. Which document should the portfolio manager use to define the decision-making roles, responsibilities, and escalation paths for the portfolio?

Trap 1: Portfolio Charter

The Portfolio Charter authorizes the portfolio and provides high-level direction, but it does not typically include detailed governance roles, responsibilities, and escalation paths. Those specifics are developed in the Portfolio Governance Plan, which operationalizes the governance structure.

Trap 2: Portfolio Strategic Plan

The Portfolio Strategic Plan outlines the portfolio's strategic objectives, prioritization criteria, and how the portfolio aligns with organizational strategy. While it informs governance, it does not define decision-making roles, responsibilities, and escalation paths. Those operational governance details are specified in the Portfolio Governance Plan.

Trap 3: Portfolio Management Plan

The Portfolio Management Plan describes how the portfolio will be managed, including processes for component selection, prioritization, and resource allocation. It may reference governance, but it does not typically define the specific decision-making roles, responsibilities, and escalation paths. Those are detailed in the Portfolio Governance Plan.

A
Portfolio Governance Plan
The Portfolio Governance Plan defines the governance structure, including decision rights, roles, responsibilities, and escalation paths. It ensures that component decisions are made at the appropriate level and that strategic alignment is maintained. This document is the foundation for portfolio governance and directly addresses the need to define decision-making roles and escalation paths.
B
Portfolio Charter
Why it fails: The Portfolio Charter authorizes the portfolio and provides high-level direction, but it does not typically include detailed governance roles, responsibilities, and escalation paths. Those specifics are developed in the Portfolio Governance Plan, which operationalizes the governance structure.
C
Portfolio Strategic Plan
Why it fails: The Portfolio Strategic Plan outlines the portfolio's strategic objectives, prioritization criteria, and how the portfolio aligns with organizational strategy. While it informs governance, it does not define decision-making roles, responsibilities, and escalation paths. Those operational governance details are specified in the Portfolio Governance Plan.
D
Portfolio Management Plan
Why it fails: The Portfolio Management Plan describes how the portfolio will be managed, including processes for component selection, prioritization, and resource allocation. It may reference governance, but it does not typically define the specific decision-making roles, responsibilities, and escalation paths. Those are detailed in the Portfolio Governance Plan.

Question 3hardmultiple choice

A portfolio manager is preparing for a quarterly portfolio review. The portfolio includes 12 components with varying risk profiles. The manager needs to present an aggregated view of portfolio risk exposure to the Governance Board. Which technique is MOST appropriate to visualize the portfolio's overall risk and its potential impact on strategic objectives?

Trap 1: Monte Carlo simulation of individual project schedules.

Monte Carlo simulation is useful for quantifying schedule and cost uncertainty for individual projects, but it does not directly aggregate risk exposure across the portfolio or show impact on strategic objectives. The portfolio manager needs a portfolio-level view that integrates risks from multiple components. Using simulation alone would require extensive data and may not provide the holistic risk picture needed for governance decisions.

Trap 2: Fishbone diagram analyzing root causes of a single critical risk.

A fishbone diagram is a root cause analysis tool for a specific problem, not for aggregating portfolio-level risk exposure. It would be too granular and focused on one risk, failing to provide the broad view needed for governance. The portfolio manager requires a technique that consolidates multiple risks and their strategic impact, which a fishbone diagram does not deliver.

Trap 3: SWOT analysis of the portfolio's internal and external environment.

SWOT analysis examines strengths, weaknesses, opportunities, and threats, but it is not a quantitative or visual tool for aggregating risk exposure. It provides a strategic overview but lacks the specificity of probability and impact assessments. For a portfolio risk review, a heat map or similar risk aggregation tool is more effective in showing the relative severity of risks across components.

A
Monte Carlo simulation of individual project schedules.
Why it fails: Monte Carlo simulation is useful for quantifying schedule and cost uncertainty for individual projects, but it does not directly aggregate risk exposure across the portfolio or show impact on strategic objectives. The portfolio manager needs a portfolio-level view that integrates risks from multiple components. Using simulation alone would require extensive data and may not provide the holistic risk picture needed for governance decisions.
B
Fishbone diagram analyzing root causes of a single critical risk.
Why it fails: A fishbone diagram is a root cause analysis tool for a specific problem, not for aggregating portfolio-level risk exposure. It would be too granular and focused on one risk, failing to provide the broad view needed for governance. The portfolio manager requires a technique that consolidates multiple risks and their strategic impact, which a fishbone diagram does not deliver.
C
Risk heat map that plots probability and impact of identified portfolio risks.
A risk heat map provides a visual aggregation of risks based on their likelihood and potential impact, enabling the Governance Board to quickly assess which risks threaten strategic objectives. It synthesizes risks from all components, showing concentration and severity. This technique is standard in portfolio risk management and supports prioritization and mitigation planning. It is the most appropriate for presenting an overall risk exposure view.
D
SWOT analysis of the portfolio's internal and external environment.
Why it fails: SWOT analysis examines strengths, weaknesses, opportunities, and threats, but it is not a quantitative or visual tool for aggregating risk exposure. It provides a strategic overview but lacks the specificity of probability and impact assessments. For a portfolio risk review, a heat map or similar risk aggregation tool is more effective in showing the relative severity of risks across components.

Question 4hardmultiple choice

When conducting a portfolio 'what-if' analysis, which factor must be the primary consideration?

Trap 1: Vendor contract expiration dates.

Contract expiry dates are an operational scheduling input, not a driver of what-if scenario modelling, which tests portfolio outcomes against changed strategic assumptions such as funding cuts or benefit shifts. Expiry tracking belongs in procurement or vendor-management reviews, where renewal timing and commercial leverage are the actual concerns.

Trap 2: Project manager availability.

What-if analysis weighs scenarios by strategic alignment, value and risk; individual project manager availability is a resourcing detail, not the primary factor. It is tempting because capacity constrains portfolios, and would be correct when modelling resource-constrained scenarios, not as the primary consideration.

Trap 3: Team morale.

What-if analysis compares scenarios against strategic objectives, cost, risk and benefit; team morale is not the primary axis. It is tempting because morale affects delivery capacity, and would be correct as a secondary constraint when assessing resource-driven scenarios, not as the primary consideration.

A
Vendor contract expiration dates.
Why it fails: Contract expiry dates are an operational scheduling input, not a driver of what-if scenario modelling, which tests portfolio outcomes against changed strategic assumptions such as funding cuts or benefit shifts. Expiry tracking belongs in procurement or vendor-management reviews, where renewal timing and commercial leverage are the actual concerns.
B
Strategic alignment and impact on portfolio constraints.
What-if analysis models alternative portfolio compositions, so each scenario must be judged by strategic alignment and its effect on portfolio constraints such as budget, resources, and risk. These factors determine whether a simulated change is viable.
C
Project manager availability.
Why it fails: What-if analysis weighs scenarios by strategic alignment, value and risk; individual project manager availability is a resourcing detail, not the primary factor. It is tempting because capacity constrains portfolios, and would be correct when modelling resource-constrained scenarios, not as the primary consideration.
D
Team morale.
Why it fails: What-if analysis compares scenarios against strategic objectives, cost, risk and benefit; team morale is not the primary axis. It is tempting because morale affects delivery capacity, and would be correct as a secondary constraint when assessing resource-driven scenarios, not as the primary consideration.

Question 5hardmultiple choice

You are managing a portfolio with a mix of projects and programs. A new risk has been identified that could affect multiple components simultaneously, but its probability and impact are uncertain. The portfolio board wants to understand the potential worst-case scenario and the likelihood of exceeding the portfolio's risk tolerance. Which technique is most appropriate to use?

Trap 1: SWOT analysis

SWOT analysis examines strengths, weaknesses, opportunities, and threats, but it is qualitative and does not provide probabilistic outcomes or worst-case scenarios. It is useful for strategic planning, not for quantifying the likelihood of exceeding risk tolerance in a portfolio context.

Trap 2: Decision tree analysis

Decision tree analysis evaluates sequential decisions and their outcomes, but it is typically used for specific choices rather than modeling the aggregate effect of multiple portfolio risks. It may not capture the full range of uncertainties or correlations across the portfolio as effectively as simulation.

Trap 3: Risk probability and impact assessment

Risk probability and impact assessment rates individual risks, often qualitatively or semi-quantitatively. It does not aggregate risks or model their combined effect to determine the probability of exceeding portfolio tolerance. It is a component of risk analysis but insufficient for complex, portfolio-wide uncertainty.

A
SWOT analysis
Why it fails: SWOT analysis examines strengths, weaknesses, opportunities, and threats, but it is qualitative and does not provide probabilistic outcomes or worst-case scenarios. It is useful for strategic planning, not for quantifying the likelihood of exceeding risk tolerance in a portfolio context.
B
Decision tree analysis
Why it fails: Decision tree analysis evaluates sequential decisions and their outcomes, but it is typically used for specific choices rather than modeling the aggregate effect of multiple portfolio risks. It may not capture the full range of uncertainties or correlations across the portfolio as effectively as simulation.
C
Risk probability and impact assessment
Why it fails: Risk probability and impact assessment rates individual risks, often qualitatively or semi-quantitatively. It does not aggregate risks or model their combined effect to determine the probability of exceeding portfolio tolerance. It is a component of risk analysis but insufficient for complex, portfolio-wide uncertainty.
D
Monte Carlo simulation
Monte Carlo simulation models the combined effect of multiple uncertain risks by running thousands of iterations, providing a probability distribution of outcomes. It is ideal for assessing worst-case scenarios and the likelihood of exceeding portfolio risk tolerance, especially when risks are correlated or affect multiple components.

Question 6mediummultiple choice

A portfolio manager at a healthcare organization is preparing for the quarterly Portfolio Governance Board meeting. Several components have submitted change requests that would alter their alignment with the strategic objective of expanding telemedicine services. The portfolio manager must ensure the board has the right information to make informed decisions. Which action best supports effective portfolio governance in this scenario?

Trap 1: Approve the change requests that have the highest individual…

Approving changes based solely on individual component ROI ignores portfolio-level strategic alignment and exceeds the portfolio manager's authority. Governance decisions of this magnitude should involve the board. This approach could lead to a collection of high-ROI components that collectively fail to advance the telemedicine objective, misaligning the portfolio with organizational strategy.

Trap 2: Delay the change requests until the next annual portfolio review to…

Delaying decisions can cause missed opportunities and may not be feasible if changes are time-sensitive. Governance should be responsive to significant changes that affect strategic alignment. Waiting a year could render the telemedicine expansion less competitive and ignores the need for timely portfolio adjustments based on evolving conditions.

Trap 3: Forward all change requests directly to the board without analysis…

Forwarding raw requests without analysis burdens the board and fails to provide the context needed for strategic decisions. The portfolio manager's role includes filtering and analyzing information to highlight impacts on portfolio objectives. Without this, the board may make uninformed choices that don't align with the telemedicine strategy, undermining effective governance.

A
Approve the change requests that have the highest individual component ROI and inform the board afterward.
Why it fails: Approving changes based solely on individual component ROI ignores portfolio-level strategic alignment and exceeds the portfolio manager's authority. Governance decisions of this magnitude should involve the board. This approach could lead to a collection of high-ROI components that collectively fail to advance the telemedicine objective, misaligning the portfolio with organizational strategy.
B
Evaluate each change request against the portfolio's strategic objectives and provide a consolidated impact analysis to the board.
This action ensures the board receives a holistic view of how each change affects the portfolio's strategic alignment. By consolidating impact analyses, the portfolio manager enables the board to prioritize changes that best support the telemedicine expansion objective, rather than reviewing isolated requests. This aligns with the governance principle of making decisions based on portfolio-level value and strategic fit.
C
Delay the change requests until the next annual portfolio review to avoid disrupting the current quarter's plans.
Why it fails: Delaying decisions can cause missed opportunities and may not be feasible if changes are time-sensitive. Governance should be responsive to significant changes that affect strategic alignment. Waiting a year could render the telemedicine expansion less competitive and ignores the need for timely portfolio adjustments based on evolving conditions.
D
Forward all change requests directly to the board without analysis to avoid introducing bias.
Why it fails: Forwarding raw requests without analysis burdens the board and fails to provide the context needed for strategic decisions. The portfolio manager's role includes filtering and analyzing information to highlight impacts on portfolio objectives. Without this, the board may make uninformed choices that don't align with the telemedicine strategy, undermining effective governance.

Question 7mediummultiple choice

You are the portfolio manager for a pharmaceutical R&D portfolio with three drug-development programs. A key contract manufacturer shared audited financials showing a debt covenant breach that will likely trigger restructuring within two quarters, which could halt supply of a critical excipient used by two programs. The programs' risk registers list this supplier only as 'medium likelihood, medium impact.' What should you do FIRST as the portfolio manager?

Trap 1: Log the covenant breach as an issue in the portfolio issue log and…

The breach has not yet caused a supply interruption, so it remains a risk rather than a realized issue. Recording it only in the issue log bypasses likelihood and impact analysis and skips escalation to the portfolio board. Delegating monitoring to the supplier's own account manager also removes the independent verification the portfolio needs for a strategic single-source dependency.

Trap 2: Immediately terminate the contract and sole-source the excipient…

Terminating a validated pharmaceutical supplier is not a proportionate first response. Regulatory filings, stability data, and quality agreements tie the excipient to approved processes, so a rapid switch could delay programs more than the supplier event itself. The portfolio manager should first quantify and escalate the exposure, then decide whether qualification of an alternate source is warranted.

Trap 3: Direct each program manager to update their own risk register and…

This is the classic program-level response that fails at portfolio level. Because the same supplier feeds two programs, their mitigation actions would overlap, compete for the same alternate suppliers, and miss the compounding effect on strategic objectives. Program contingency budgets are also sized for program scope, not for a correlated event that simultaneously threatens multiple programs.

A
Log the covenant breach as an issue in the portfolio issue log and assign the supplier's account manager to report progress monthly.
Why it fails: The breach has not yet caused a supply interruption, so it remains a risk rather than a realized issue. Recording it only in the issue log bypasses likelihood and impact analysis and skips escalation to the portfolio board. Delegating monitoring to the supplier's own account manager also removes the independent verification the portfolio needs for a strategic single-source dependency.
B
Immediately terminate the contract and sole-source the excipient from a new manufacturer to eliminate the risk before restructuring occurs.
Why it fails: Terminating a validated pharmaceutical supplier is not a proportionate first response. Regulatory filings, stability data, and quality agreements tie the excipient to approved processes, so a rapid switch could delay programs more than the supplier event itself. The portfolio manager should first quantify and escalate the exposure, then decide whether qualification of an alternate source is warranted.
C
Direct each program manager to update their own risk register and manage the supplier risk within their existing program contingency budgets.
Why it fails: This is the classic program-level response that fails at portfolio level. Because the same supplier feeds two programs, their mitigation actions would overlap, compete for the same alternate suppliers, and miss the compounding effect on strategic objectives. Program contingency budgets are also sized for program scope, not for a correlated event that simultaneously threatens multiple programs.
D
Aggregate the correlated supplier exposure from both programs and raise it to the portfolio risk register with an escalated, portfolio-level rating for board review.
A single supplier feeding two programs creates correlated, portfolio-level exposure that individual program registers understate. Reassessing and aggregating that shared exposure into the portfolio risk register, with an escalated rating, gives the portfolio board the consolidated view needed to authorize mitigation such as qualifying a second excipient source or holding strategic buffer stock.