SAFe-Agilist Exploring Lean Portfolio Management Practice Question
Which of the following describes the 'Portfolio Backlog' in SAFe?
⚠ Common exam trap
Candidates often confuse the Portfolio Backlog with the Program Backlog, incorrectly assuming it contains features or stories rather than the high-level business and enabler epics that drive strategic investment.
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
✓
A repository of upcoming business and enabler epics for the portfolio.
The Portfolio Backlog is the high-level container for all upcoming business and enabler epics intended to realize the portfolio's strategic themes. It is a prioritized list that represents the portfolio's investment plan. By managing this backlog through a Kanban system, LPM ensures that the most valuable and strategic initiatives are always in focus, providing a clear path for the organization to achieve its long-term objectives while maintaining alignment with current capacity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A list of all user stories that need to be developed in the next Program Increment.
Why it's wrong here
User stories reside in the Team Backlog, not the Portfolio Backlog. The Portfolio Backlog deals with high-level epics that require investment and cross-program coordination. Including user stories at the portfolio level would cause massive information overload and detract from the strategic focus that LPM is intended to maintain.
- ✓
A repository of upcoming business and enabler epics for the portfolio.
Why this is correct
The Portfolio Backlog holds all the epics that have been approved or are under consideration for the portfolio. This ensures that the portfolio has a transparent, prioritized, and manageable list of future strategic work, allowing for better planning and alignment of resources across the entire value stream over time.
- ✗
A document that tracks the financial budget for each team in the Agile Release Train.
Why it's wrong here
The Portfolio Backlog is not a financial ledger or a tracking document for team-level budgets. Financial tracking happens through other tools and portfolio management processes. The backlog is strictly for managing the flow and prioritization of epics that contribute to the portfolio's strategic goals and overall business outcomes.
- ✗
A database for storing historical data on team velocity and past performance.
Why it's wrong here
Historical velocity and team performance metrics are typically tracked at the Program or Team level within ALM tools. Storing them in the Portfolio Backlog is inappropriate as it would clutter the view of strategic initiatives and does not assist in the primary function of prioritizing upcoming epic investments.
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.