SAFe-Agilist Exploring Lean Portfolio Management Practice Question
In the context of SAFe, what is the main purpose of the 'Portfolio Backlog'?
⚠ Common exam trap
Test-takers frequently confuse the Portfolio Backlog with raw ideation funnels or active execution states, overlooking its specific function as a holding area for approved 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 the holding area for approved Portfolio Epics ready for implementation.
The Portfolio Backlog acts as a holding area for approved Portfolio Epics that are ready for implementation. It represents the 'ready' state of the portfolio, where initiatives have been vetted, analyzed, and prioritized. By maintaining a clean and prioritized backlog, the organization ensures that the Agile Release Trains always have a clear, high-value pipeline of work, enabling them to begin development without delay.
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 raw ideas generated by anyone in the company.
Why it's wrong here
A backlog of raw, unvetted ideas is a 'junk drawer' that creates noise and confusion. Raw ideas belong in the Funnel, where they are screened and refined. The Portfolio Backlog should only contain initiatives that have successfully passed through the 'Review' and 'Analyze' phases, ensuring it contains only high-value, actionable items.
- ✓
To act as the holding area for approved Portfolio Epics ready for implementation.
Why this is correct
The backlog serves as the queue for the Agile Release Trains. Having approved and prioritized epics in the backlog ensures that the organization can start high-value work immediately as capacity becomes available. This is critical for maintaining a steady flow of value and ensuring that the most impactful work is consistently prioritized.
- ✗
To track the daily status of all team-level user stories.
Why it's wrong here
Tracking team-level user stories is the responsibility of the Agile Release Train's backlog, not the Portfolio Backlog. The Portfolio Backlog remains at the high-level Epic scope. Mixing user stories into the portfolio level creates unnecessary complexity and destroys the strategic focus of the Portfolio Manager and executive stakeholders.
- ✗
To serve as the final repository for archived and completed projects.
Why it's wrong here
The Portfolio Backlog is for future work, not past work. Archived or completed projects belong in a historical repository or reporting system. Storing completed work in the backlog makes it difficult for teams to find what they need to work on next, cluttering the system and reducing the effectiveness of the prioritization process.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.