Release on Demand Flashcards
6 cards from real SAFe® 5 DevOps Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Release on Demand flashcards as text
What type of feature toggle is specifically designed to gradually roll out a feature to increasing percentages of users over time?
Answer: Release toggle
Release toggles control the gradual rollout of new features, allowing teams to slowly increase the percentage of users who experience the feature.
What is a 'kill switch' in the context of SAFe feature toggle management?
Answer: An emergency toggle that instantly disables a problematic feature in production
A kill switch is a feature toggle used as an emergency brake to instantly disable a feature in production when critical defects are detected.
What is the main risk of leaving feature toggles in the production codebase long after the feature has fully launched?
Answer: They accumulate as technical debt, making the code increasingly complex and hard to maintain
Stale feature toggles accumulate as technical debt when not removed, creating complex conditional branching logic that makes code harder to understand and maintain.
In SAFe, what role does a Feature Freeze typically play in release management?
Answer: It stabilizes the codebase before a release by halting new feature additions
Feature freeze stabilizes the codebase by stopping new feature additions, allowing the team to focus entirely on quality, testing, and release readiness.
Which SAFe practice helps ensure release decisions are based on both technical readiness AND business readiness simultaneously?
Answer: Release criteria and release readiness reviews
Release criteria and readiness reviews ensure both technical quality gates and business readiness conditions are fully satisfied before releasing to customers.
In a true continuous delivery model, how often should a SAFe team theoretically be able to release to production?
Answer: At any time the business decides, because the pipeline always maintains release readiness
Continuous delivery means the pipeline maintains a perpetually releasable product state, so the release timing is purely a business decision unconstrained by technical readiness.