SAFe® 5 DevOps Certification SAFe® 5 DevOps: Continuous Deployment 1 — Questions and Answers
Question 1: In SAFe® 5 DevOps, what is the primary goal of Continuous Deployment?
- To deploy every code change automatically to production without human approval
- To release software to production reliably, frequently, and with minimal manual effort (Correct answer)
- To replace the Release on Demand practice with automated releases
- To eliminate the need for feature testing before deployment
Correct answer: To release software to production reliably, frequently, and with minimal manual effort
Continuous Deployment aims to make releases reliable, frequent, and low-effort by automating the path from code commit to production deployment.
Question 2: Which deployment strategy in SAFe® 5 DevOps runs two identical production environments simultaneously, with traffic routed to only one at a time?
- Canary deployment
- Rolling deployment
- Blue-green deployment (Correct answer)
- Shadow deployment
Correct answer: Blue-green deployment
Blue-green deployment maintains two identical environments (blue and green) so traffic can be instantly switched between them, enabling zero-downtime releases and fast rollbacks.
Question 3: In a canary release deployment strategy, what happens initially?
- The new version is deployed to all users at once and rolled back if errors occur
- The new version is deployed to a small subset of users before a full rollout (Correct answer)
- The new version runs in shadow mode collecting metrics without serving traffic
- The deployment is paused until all automated tests pass in staging
Correct answer: The new version is deployed to a small subset of users before a full rollout
Canary releases route a small percentage of traffic to the new version first, allowing teams to validate behavior in production before expanding rollout to all users.
Question 4: What is a feature toggle (feature flag) used for in SAFe® 5 DevOps Continuous Deployment?
- To configure environment-specific database connection strings
- To separate code deployment from feature release, enabling deployment without exposing new functionality (Correct answer)
- To automatically toggle between blue and green environments during deployment
- To control access to DevOps pipeline configuration in CI/CD tools
Correct answer: To separate code deployment from feature release, enabling deployment without exposing new functionality
Feature toggles decouple deployment from release, allowing code to be deployed to production but hidden from users until the team decides to enable it.
Question 5: Which metric best measures an organization's Continuous Deployment effectiveness in SAFe® 5 DevOps?
- Number of developers on the team
- Lines of code deployed per sprint
- Deployment frequency and change failure rate (Correct answer)
- Total number of automated test cases
Correct answer: Deployment frequency and change failure rate
Deployment frequency and change failure rate are key DORA metrics that together indicate how often a team deploys and how often those deployments cause failures in production.
Question 6: In SAFe® 5, what is the recommended approach for managing environment configurations across development, staging, and production?
- Store environment-specific configurations in the application source code
- Manually configure each environment by the operations team before deployment
- Use Infrastructure as Code (IaC) to version-control and automate environment configuration (Correct answer)
- Keep a separate configuration repository accessible only to release managers
Correct answer: Use Infrastructure as Code (IaC) to version-control and automate environment configuration
Infrastructure as Code (IaC) version-controls environment configurations so they can be applied consistently, automatically, and repeatably across all environments.
Question 7: What does 'deployment pipeline' refer to in SAFe® 5 DevOps?
- A project management tool for tracking deployment tasks in a Kanban board
- An automated sequence of stages that builds, tests, and delivers software to production (Correct answer)
- A network infrastructure component that routes traffic between services
- A SAFe® ceremony where the Release Train Engineer plans deployments
Correct answer: An automated sequence of stages that builds, tests, and delivers software to production
A deployment pipeline is an automated sequence of stages (build, test, deploy) that carries code changes from source control through to production delivery.
