SAFe Continuous Delivery Pipeline and DevOps 1 — Questions and Answers
Question 1: What are the four aspects of the SAFe Continuous Delivery Pipeline?
- Plan, Build, Test, Deploy
- Continuous Exploration, Continuous Integration, Continuous Deployment, Release on Demand (Correct answer)
- Design, Develop, Test, Release
- Backlog, Sprint, Review, Retrospective
Correct answer: Continuous Exploration, Continuous Integration, Continuous Deployment, Release on Demand
SAFe's Continuous Delivery Pipeline consists of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand.
Question 2: What is the purpose of 'Continuous Exploration (CE)' in the SAFe Continuous Delivery Pipeline?
- Automated testing of all code changes
- Continuously researching customer needs, market dynamics, and emerging technologies to shape the backlog (Correct answer)
- Deploying software to staging environments
- Exploring new technology stacks for the platform
Correct answer: Continuously researching customer needs, market dynamics, and emerging technologies to shape the backlog
CE is the ongoing process of hypothesizing, researching, and discovering customer needs to fill the Program Backlog with high-value Features.
Question 3: In SAFe, what does 'Continuous Integration (CI)' require teams to do?
- Hold daily integration meetings
- Frequently integrate code changes into a shared mainline with automated build and test verification (Correct answer)
- Integrate with third-party vendor systems
- Merge code only at the end of each sprint
Correct answer: Frequently integrate code changes into a shared mainline with automated build and test verification
CI requires developers to integrate code into the shared mainline multiple times daily, with automated builds and tests catching integration failures immediately.
Question 4: What is the difference between 'Continuous Deployment' and 'Release on Demand' in SAFe?
- There is no difference — they are the same concept
- Continuous Deployment pushes to production automatically; Release on Demand activates features for customers when the business decides (Correct answer)
- Continuous Deployment is optional; Release on Demand is mandatory
- Release on Demand is for hardware; Continuous Deployment is for software
Correct answer: Continuous Deployment pushes to production automatically; Release on Demand activates features for customers when the business decides
CD deploys code to production continuously, while Release on Demand is the business decision to make features available to customers — often enabled by feature toggles.
Question 5: What is the 'CALMR' approach in SAFe's DevOps health radar?
- A risk assessment framework
- Culture, Automation, Lean Flow, Measurement, Recovery — five dimensions of DevOps health (Correct answer)
- A code review checklist
- A deployment pipeline stage gate
Correct answer: Culture, Automation, Lean Flow, Measurement, Recovery — five dimensions of DevOps health
CALMR is SAFe's DevOps framework: Culture (collaboration), Automation (CI/CD), Lean Flow (reduce WIP), Measurement (outcomes), Recovery (fast failure recovery).
Question 6: What does 'Hypothesis-Driven Development' mean in SAFe's Continuous Exploration?
- Writing code without requirements
- Framing features as hypotheses, testing them with users, and using data to decide whether to pivot or persevere (Correct answer)
- Using AI to predict feature success
- Building multiple feature prototypes simultaneously
Correct answer: Framing features as hypotheses, testing them with users, and using data to decide whether to pivot or persevere
Hypothesis-Driven Development treats each feature as an experiment — defining the hypothesis, measuring outcomes, and pivoting or persevering based on real data.
SAFe Continuous Delivery Pipeline and DevOps 1
What are the four aspects of the SAFe Continuous Delivery Pipeline?