SAFe® 5 DevOps Certification Release on Demand 3

Question 1

What type of feature toggle is specifically designed to gradually roll out a feature to increasing percentages of users over time?

Accepted Answer

Release toggle

Answer

Kill switch toggle

Answer

Ops toggle

Answer

Permission toggle

Question 2

What is a 'kill switch' in the context of SAFe feature toggle management?

Accepted Answer

An emergency toggle that instantly disables a problematic feature in production

Answer

A toggle that permanently deletes a feature from the codebase

Answer

A toggle that terminates the entire CI/CD pipeline execution

Answer

A setting that forcibly terminates active user sessions

Question 3

What is the main risk of leaving feature toggles in the production codebase long after the feature has fully launched?

Accepted Answer

They accumulate as technical debt, making the code increasingly complex and hard to maintain

Answer

They significantly slow down CI/CD pipeline execution speed

Answer

They prevent canary releases from functioning correctly

Answer

They create conflicts with blue/green deployment routing

Question 4

In SAFe, what role does a Feature Freeze typically play in release management?

Accepted Answer

It stabilizes the codebase before a release by halting new feature additions

Answer

It permanently stops all new feature development on the team

Answer

It freezes infrastructure configuration changes only

Answer

It pauses all PI planning and ARTactivities

Question 5

Which SAFe practice helps ensure release decisions are based on both technical readiness AND business readiness simultaneously?

Accepted Answer

Release criteria and release readiness reviews

Answer

Definition of Done only

Answer

Sprint Review ceremonies

Answer

Product Backlog refinement sessions

Question 6

In a true continuous delivery model, how often should a SAFe team theoretically be able to release to production?

Accepted Answer

At any time the business decides, because the pipeline always maintains release readiness

Answer

Only once per Program Increment on the PI boundary

Answer

Once per sprint at most, after sprint review

Answer

Only after all regression tests are executed and signed off manually