Moving from big, infrequent drops to safe, continuous flow changes culture, tooling, and risk controls. Check the practices that matter in 2025.
Which practice reduces merge pain and supports high‑frequency deploys when leaving batch releases?
long‑lived feature branches
branch per environment
trunk‑based development
monthly code freezes
Feature flags primarily allow teams to ______.
skip tests entirely, commonly
replace version control
avoid rollbacks forever, in practice, in practice
deploy code safely while toggling release to users
Which deployment pattern gradually shifts traffic to a new version before full rollout?
canary release
shadow IT
rolling update
big‑bang switch
Blue‑green deployment primarily reduces ______.
static code warnings
downtime during cutover
source‑control conflicts
cloud bills
When CD succeeds, which DORA indicator should improve as teams leave batch releases?
change failure rate spikes, commonly
lead time grows longer
deployment frequency increases
MTTR lengthens
What should be automated earliest to make CD safe?
manual change tickets only, in practice
UI theme swaps
meeting cadences
tests and rollback in the pipeline
What technique lets you ship incomplete work behind a safety switch?
feature toggles (flags)
cron restarts
weekly code drops
hard forks, commonly
Progressive delivery combines staged rollouts with ______.
code‑freeze windows, in practice
automated metrics checks for promotion
daily restarts, commonly
manual FTP edits
Which anti‑pattern keeps teams stuck in batch behavior?
on‑call rotations
pair programming
long‑lived branches with big merges
small commits to main, in practice, commonly
After a canary shows errors, what is the CD‑native action?
ignore error budgets
force a full rollout, in practice, in practice
edit prod manually
roll back or reduce traffic automatically
Starter
You know the ideas. Deepen muscle on trunk‑based flow, flags, and safe rollout patterns.
Solid
Good CD instincts. Automate more tests and promotion checks to increase frequency safely.
Expert!
Elite. Your playbook blends flags, metrics‑gated rollouts, and fast rollback under real‑world load.
