Blue-green, rolling, canary, recreate — vocabulary for discussing deployment strategies and trade-offs. Intermediate
0 / 10 completed
1 / 10
A DevOps engineer says: "We're using blue-green deployment — the green environment is currently live."
What happens when the new version is deployed in a blue-green strategy?
Blue-green deployment maintains two identical environments. Only one handles traffic at a time. The cutover is a DNS or load balancer switch — instantaneous for users. Rollback is equally fast: switch back to the previous environment.
Term
Meaning
blue-green cutover
The traffic switch from the old (live) environment to the new (updated) environment
zero-downtime deployment
No users experience interruption — traffic switches atomically
rollback cost
Very low — just switch traffic back to the previous environment
infrastructure cost
Higher — two full environments must be maintained simultaneously
2 / 10
A platform engineer says: "We're doing a canary deployment — the new build is serving 10% of traffic."
What is the key purpose of a canary deployment?
The canary deployment name comes from "canary in the coal mine" — a small signal of danger. A small traffic percentage routes to the new version; if metrics look good, the percentage increases. If not, rollback affects only the canary slice.
Term
Meaning
canary percentage
The fraction of traffic routed to the new version (e.g. 1%, 5%, 10%)
observation window
The monitoring period before deciding to promote or roll back the canary
promote to full rollout
Increase canary traffic to 100% after validation passes
traffic weight
The percentage split between the stable version and the canary version
3 / 10
A release note says: "The rolling deployment replaced containers one-at-a-time with the new version."
What is the main trade-off of a rolling deployment compared to a blue-green deployment?
During a rolling deployment, old and new instances coexist. If the new version has a different API shape (e.g. renamed field), requests may hit either version — causing inconsistency. Blue-green avoids this because the switch is atomic.
Concept
Rolling
Blue-green
Extra capacity
Not required
Requires 2× infrastructure
Version coexistence
Old + new run together during rollout
Atomic switch — no coexistence
N-1 compatibility
Required — must handle both API versions
Not required
Rollback speed
Slower — must redeploy old version
Instant — switch traffic back
Key vocabulary: maxSurge (max extra pods during rollout) and maxUnavailable (max pods down at once) are Kubernetes rolling update parameters.
4 / 10
A team is choosing a deployment strategy for a database migration that requires all application instances to run the new schema version simultaneously.
When should a team choose a "recreate" (big-bang) deployment strategy over rolling or blue-green?
The recreate strategy stops all old instances, then starts all new instances. This causes deliberate downtime but guarantees all instances run the same version — essential when split-version running would cause data corruption or schema conflicts.
Term
Meaning
maintenance window
A scheduled period of planned downtime communicated to users in advance
big-bang deployment
All instances updated at once — the entire version change happens in one operation
pre-upgrade migration
A database migration run before the application update to prepare the schema
planned downtime
Intentional service unavailability communicated and scheduled in advance
5 / 10
A PR description reads: "This release uses an immutable infrastructure pattern — new AMIs are built for every release."
What does "immutable infrastructure" mean in a deployment context?
Immutable infrastructure means every release produces a new server image (AMI, container image). Old instances are destroyed; new ones are created from the known-good image. This eliminates configuration drift and makes rollback simple: destroy new, launch old image.
Concept
Immutable
Mutable
Update method
Destroy and replace with new image
Patch running instances in place
Configuration drift
Impossible — each instance is identical
Likely — servers diverge over time
Rollback
Launch previous image, destroy new
Complex — reverse patches
Key vocabulary: golden image (the pre-built base image), cattle vs. pets (immutable = cattle — replaceable; mutable = pets — individually managed).
6 / 10
Reviewer: 'I noticed you're deploying directly to production with this hotfix. While it's quick, have you considered a phased rollout, perhaps starting with a small percentage of users via a canary deployment?'
What is the primary benefit highlighted by the reviewer regarding a canary deployment?
The reviewer is concerned about risk mitigation. Canary deployments allow for monitoring and data collection on a small subset of users before impacting everyone. The core purpose isn't just speed; it's controlled testing in a low-risk environment. Options A and C misrepresent the key benefit – immediate deployment isn't necessarily the best approach when dealing with potentially unstable code.
7 / 10
DevOps Lead (via Slack): 'Hey team, we're aiming for a blue-green deployment tomorrow. Please ensure your services are configured to point to the green environment after the switchover.'
What does it mean to configure services to 'point to the green environment' in this context?
The phrasing 'point to the green environment' is a common shorthand in deployment scenarios. It refers to configuring routing mechanisms (like load balancers or DNS) to direct traffic to the currently active and functioning environment – which, at that moment, is designated as 'green'. Options A and C are misinterpretations of the term; options B and D are too granular.
8 / 10
PR Description: 'This commit introduces a new feature flag. We're utilizing a dynamic rollout strategy, initially targeting 5% of users with the flag enabled via a percentage-based traffic routing rule in our load balancer.'
What does 'percentage-based traffic routing' refer to when implementing this feature flag deployment?
'Percentage-based traffic routing' is a critical aspect of dynamic rollout strategies like feature flags. It describes how a load balancer (or similar routing mechanism) is configured to direct a certain percentage of user requests to the new version of the feature flag – allowing for controlled testing and monitoring without impacting all users. Options A and C are unrelated; option B misrepresents the role of the load balancer.
9 / 10
Team Lead (during standup): 'Sarah, can you give us a quick update on the database migration? We're using a rolling deployment. How's it progressing?'
What is the primary advantage of utilizing a 'rolling deployment' strategy for this database migration?
Rolling deployments are designed for minimal disruption. By applying updates in stages across servers, the system remains available throughout the process – and a rollback is simpler than with a 'big-bang' approach. Option A describes a database shutdown; option C is an incorrect description of schema replication.
10 / 10
Release Manager: 'We've adopted an immutable infrastructure pattern for our microservices. Each new release builds a completely fresh AMI with the updated code and dependencies.'
What is the core principle of 'immutable infrastructure' as applied in this scenario?
Immutable infrastructure centers around the concept that deployed components – in this case, AMIs – should *not* be modified after creation. Instead, a new AMI is built for each release, ensuring consistency and simplifying rollback procedures. Option A describes patching; option C refers to IaC but doesn't capture the core immutable principle.
What will I practice in "Deployment Strategy Language Exercises"?
This is a Release Management exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of release management terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 10 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the release management vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Release Management exercises?
See the Release Management exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — release management vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.