SAFe® 5 DevOps: Continuous Deployment Flashcards
7 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 7 SAFe® 5 DevOps: Continuous Deployment flashcards as text
In SAFe® 5 DevOps, what is the primary goal of Continuous Deployment?
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.
Which deployment strategy in SAFe® 5 DevOps runs two identical production environments simultaneously, with traffic routed to only one at a time?
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.
In a canary release deployment strategy, what happens initially?
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.
What is a feature toggle (feature flag) used for in SAFe® 5 DevOps Continuous Deployment?
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.
Which metric best measures an organization's Continuous Deployment effectiveness in SAFe® 5 DevOps?
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.
In SAFe® 5, what is the recommended approach for managing environment configurations across development, staging, and production?
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.
What does 'deployment pipeline' refer to in SAFe® 5 DevOps?
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.