SAFe-Agilist Product Development Flow Practice Question
A SAFe Practitioner is analyzing a value stream and notices that work items often wait in a queue before being deployed to production. The team has automated testing and continuous integration, but deployment still requires manual approval from a change advisory board (CAB) that meets only once a week. What is the primary flow issue in this scenario?
⚠ Common exam trap
The trap here is assuming that automation of testing or deployment is the issue, when the real bottleneck is the approval gate.
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
✓
The change advisory board (CAB) is a bottleneck that introduces a long queue and delays flow.
The weekly CAB meeting creates a queue that delays deployment, increasing lead time and disrupting flow. SAFe encourages reducing batch sizes and eliminating approval bottlenecks through automation and decentralized decision-making to achieve continuous delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The deployment process is not automated, causing manual errors.
Why it's wrong here
The scenario mentions that deployment requires manual approval, but it does not state that the deployment itself is manual or error-prone. The issue is the waiting time for approval, not the execution of deployment. Automating deployment would not eliminate the weekly CAB queue. The primary flow issue is the approval bottleneck.
- ✗
The team is not using a Program Kanban to visualize work.
Why it's wrong here
While visualizing work is important, the scenario does not indicate that lack of a Kanban is the cause of delays. The specific delay is due to the weekly CAB meeting. Even with a Kanban, the queue would persist. The root cause is the approval process, not the visualization tool. SAFe emphasizes addressing the actual constraint, not just visualizing it.
- ✓
The change advisory board (CAB) is a bottleneck that introduces a long queue and delays flow.
Why this is correct
The weekly CAB meeting creates a waiting period for deployment approval, which is a classic queue. In SAFe, such approval gates often become bottlenecks that increase lead time and reduce flow. To improve flow, the organization should consider decentralizing approvals or automating compliance checks, enabling faster deployment and reducing batch size.
- ✗
The team lacks automated testing, causing delays.
Why it's wrong here
The scenario states that automated testing and continuous integration are already in place. Therefore, the delay is not due to missing automated testing. The bottleneck is the weekly CAB meeting, which introduces a long queue between development and deployment. Focusing on testing would not address the actual constraint in the flow.
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.