DevOps & Continuous Delivery Flashcards
7 cards from real DAC practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 DevOps & Continuous Delivery flashcards as text
In a Disciplined Agile team, how should 'done' be defined in relation to Continuous Delivery?
Answer: Done means the feature is deployed to production and working as intended
In a true CD context, 'done' extends through deployment to production, not just development completion.
What is a 'canary release' in Continuous Delivery?
Answer: Releasing a new version to a small subset of users first to validate before full rollout
Canary releases limit blast radius by exposing new changes to a small percentage of traffic before full deployment.
Which DA process goal is most closely aligned with achieving high deployment frequency?
Answer: Accelerate Value Delivery
Accelerating value delivery directly targets reducing cycle time and increasing how often working software reaches users.
A team's automated test suite takes 45 minutes to run, blocking their pipeline. What is the best DA-aligned approach?
Answer: Parallelize tests, stratify by speed, and run fast tests early in the pipeline
Parallelizing and stratifying tests by speed maintains quality gates while reducing pipeline feedback time.
What is 'environment parity' and why is it important in Continuous Delivery?
Answer: Keeping development, staging, and production environments as similar as possible to prevent 'works on my machine' failures
Environment parity eliminates configuration drift between environments, making test results predictive of production behavior.
In DevOps, what does 'you build it, you run it' mean?
Answer: The team that develops a service also owns its operation and on-call responsibility in production
This principle gives development teams operational ownership, aligning incentives to build reliable, observable, and maintainable systems.
Which technique helps a DA team safely deploy database schema changes in a Continuous Delivery pipeline?
Answer: Use expand-and-contract (parallel change) pattern to make backward-compatible schema changes before removing old structures
The expand-and-contract pattern adds new schema alongside old, migrates data, then removes old structures — all in backward-compatible steps.