What is NOT a SAFe-recommended practice for DevOps?

Question

Options

• AMaintain development and test environments to better match production.
• BDeploy to staging every sprint.
• CPut everything under version control.
• DStart automating the actual deployment process.
• EBuild and maintain a production-equivalent staging environment.
• FContinuously synchronize all Feature and team branches.
• GCreate the ability to automatically build environments.

• A
  3% (1)
• B
  3% (1)
• D
  11% (4)
• F
  76% (28)
• G
  8% (3)

Explanation

Option F is the correct answer because SAFe DevOps encourages trunk-based development and short-lived branches that are merged frequently - not the continuous maintenance and synchronization of long-lived Feature and team branches. Continuously syncing multiple parallel branches increases integration complexity and creates "merge debt," which is the opposite of the fast flow SAFe promotes.

The other options are all legitimate SAFe DevOps recommendations: matching dev/test environments to production (A) and building a production-equivalent staging environment (E) reduce environment-related defects; deploying to staging every sprint (B) validates releasability on a regular cadence; version-controlling everything (C) is a foundational DevOps principle; automating the deployment process (D) directly supports the Continuous Delivery Pipeline; and automatically building environments (G) enables on-demand, consistent infrastructure.

Memory tip: Think of SAFe's mantra - reduce batch size and integrate often. Long-lived branches that need constant syncing are a symptom of big batches and delayed integration, which is exactly what SAFe DevOps works against. If an answer describes maintaining complex, parallel branch structures, it's the odd one out.

No community discussion yet for this question.