SAFe® 5 DevOps Certification Release on Demand 1 — Questions and Answers
Question 1: What is the primary goal of Release on Demand in SAFe DevOps?
- To release software on a fixed annual schedule
- To deploy only after explicit stakeholder sign-off
- To release value to customers at any time, based on business need (Correct answer)
- To eliminate all manual testing before release
Correct answer: To release value to customers at any time, based on business need
Release on Demand enables organizations to release value to customers whenever the business needs it by decoupling deployment from the release decision.
Question 2: What is the key distinction between 'deployment' and 'release' in SAFe DevOps?
- They are the same process with different names
- Deployment puts code in production; release makes features visible and available to users (Correct answer)
- Release happens in staging; deployment happens in production
- Deployment requires user approval; release is fully automatic
Correct answer: Deployment puts code in production; release makes features visible and available to users
Deployment moves code to production infrastructure while release is the business decision to make features visible and available to end users.
Question 3: Which mechanism allows features to be deployed to production but hidden from end users until a deliberate release decision is made?
- Blue/green deployment environments
- Feature toggles (feature flags) (Correct answer)
- Canary release routing rules
- Rollback scripts
Correct answer: Feature toggles (feature flags)
Feature toggles allow code to be deployed and even tested in production while remaining invisible to end users until deliberately enabled.
Question 4: In SAFe, who typically makes the Release on Demand decision for a PI increment?
- The DevOps engineer who owns the pipeline
- The Scrum Master of the feature team
- Business owners and product management (Correct answer)
- The individual developer who wrote the feature
Correct answer: Business owners and product management
Release decisions in SAFe are made by business owners and product management based on business readiness, market timing, and customer impact.
Question 5: What SAFe concept ensures software is always technically ready to release, even if the business hasn't decided to release it yet?
- Continuous Deployment to a staging environment only
- The Continuous Delivery Pipeline (Correct answer)
- Program Increment boundaries
- ART sync meetings
Correct answer: The Continuous Delivery Pipeline
The Continuous Delivery Pipeline ensures software is always in a releasable state so releases can happen whenever the business makes the call.
Question 6: Release on Demand in SAFe helps organizations achieve what key business benefit?
- Reduced number of developers needed on each team
- The ability to respond rapidly to market opportunities and customer needs (Correct answer)
- Complete elimination of all production incidents
- Fully predictable and fixed release costs
Correct answer: The ability to respond rapidly to market opportunities and customer needs
Release on Demand enables rapid response to market changes and customer needs by removing technical barriers to releasing at any time.
SAFe® 5 DevOps Certification Release on Demand 1
What is the primary goal of Release on Demand in SAFe DevOps?