SAFe-Agilist Exploring Lean Portfolio Management Practice Question
Which THREE of the following are examples of Lean Portfolio Management guardrails?
⚠ Common exam trap
Candidates often select options related to 'team-level' metrics (like velocity) instead of 'portfolio-level' financial and strategic constraints that govern the entire organization's investment strategy.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Applying investment horizon distributions to ensure portfolio balance.
Guardrails are policies and practices that provide the necessary constraints for decentralized decision-making in a SAFe portfolio. By using guardrails, LPM can ensure that investments are balanced across horizons, that technical debt is managed, and that spend remains within agreed-upon limits. These controls allow teams to act with autonomy while ensuring they remain within the financial and technical boundaries established for the healthy operation of the portfolio.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Applying investment horizon distributions to ensure portfolio balance.
Why this is correct
Investment horizon distribution is a critical guardrail that prevents over-focusing on current product needs while neglecting future innovations or operational maintenance. It ensures that the enterprise maintains a healthy mix of short-term, mid-term, and long-term investments, which is crucial for long-term survival and competitiveness.
- ✗
Mandating that every team uses the same Jira workflow template.
Why it's wrong here
Mandating specific tool workflows is not a portfolio-level guardrail. SAFe promotes team autonomy, and forcing a single workflow across different domains can hinder team performance. Guardrails should be about outcomes, financial boundaries, and architectural runway, not the specific tools or process steps used at the team level.
- ✓
Requiring a minimum allocation of capacity for capacity allocation to technical debt.
Why this is correct
Allocating capacity to address technical debt is a vital guardrail to prevent the accumulation of 'interest' that can stifle future development. It ensures the system remains maintainable and scalable, protecting the long-term investment by forcing teams to address the health of their architectural runway during development.
- ✓
Setting spending limits on value streams to ensure fiscal responsibility.
Why this is correct
Spending limits allow LPM to delegate budget authority to the value stream level while maintaining overall fiscal control. This guardrail empowers teams to make local decisions within their approved budget without needing constant re-approval, effectively balancing the need for speed with the need for financial oversight.
- ✗
Reviewing all individual code commits at the portfolio level.
Why it's wrong here
Reviewing code at the portfolio level is a massive bottleneck and a violation of decentralized decision-making principles. LPM should focus on strategic alignment and high-level outcomes, not the technical minutiae of individual code changes, which are the responsibility of the development teams themselves.
About these practice questions
One of 315 original SAFe-Agilist practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.