SAFe-Agilist Exploring Lean Portfolio Management Practice Question
What is the function of the 'Portfolio Backlog' in SAFe?
⚠ Common exam trap
Candidates often confuse the Portfolio Backlog with the Team or Program Backlog, incorrectly assuming it stores user stories or technical tasks instead of high-level strategic epics.
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
✓
To act as a repository for high-level initiatives known as Epics.
The Portfolio Backlog is the holding area for upcoming business and enabler epics intended to create and evolve the portfolio's solutions. By maintaining this backlog, LPM ensures that there is a prioritized pipeline of work ready for implementation. It serves as the primary input for the Program Increments, ensuring that the Agile Release Trains always have a clear, aligned understanding of the most important strategic work to be completed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To store all the defects found in the production environment.
Why it's wrong here
Production defects belong in a defect tracker or the team's backlog for immediate remediation. The portfolio backlog is reserved for high-level strategic initiatives (epics). Mixing operational bug fixes with strategic epics would clutter the backlog and prevent LPM from focusing on the most critical portfolio-level business objectives.
- ✓
To act as a repository for high-level initiatives known as Epics.
Why this is correct
The portfolio backlog is the designated place for epics that have been reviewed and approved for potential implementation. It serves as the single source of truth for the portfolio's strategic initiatives, allowing the team to manage, prioritize, and track these items as they move through the portfolio lifecycle.
- ✗
To define the detailed requirements for every feature on the roadmap.
Why it's wrong here
Detailed feature requirements are defined at the program level, not the portfolio level. Portfolio epics are high-level descriptions. Asking for detailed requirements at the portfolio level creates a bottleneck and forces executive teams to do work that should be performed by the teams closer to the implementation.
- ✗
To manage the daily work assignments for all developers in the organization.
Why it's wrong here
The portfolio backlog is for strategic, high-level items. Assigning daily tasks is a team-level concern. Managing task assignments at the portfolio level would be an extreme form of micromanagement that would destroy team autonomy and significantly slow down the delivery process, making the organization much less agile.
Visual reference
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.