Home › MCA Cloud Computing › cloudcomputing › cloudobservability › A canary deployment differs from a blue/green de…
A canary deployment differs from a blue/green deployment because:
ACanary always uses encrypted disks; blue/green never does
BThey are identical patterns with different names by region
CCanary is only used for migrating to mainframes; blue/green is cloud-only
DA canary ramps the new version to a small percentage of real users first (e.g. 1% then 10% then 50% then 100%); blue/green keeps two full environments and flips all traffic at once
Answer & Solution
Correct answer: D. A canary ramps the new version to a small percentage of real users first (e.g. 1% then 10% then 50% then 100%); blue/green keeps two full environments and flips all traffic at once
Canary = gradual percentage ramp; blue/green = instant cutover between two full environments. Each has different rollback profiles; neither is region- or disk-specific.
Related questions
What does an SRE typically aim for when setting the WHITE-BOX vs BLACK-BOX monitoring balaWhich managed-observability service maps to its cloud correctly?A hybrid cloud architecture connects on-premises systems to one or more public clouds. WhiA common trade-off when adopting a strict multi-cloud architecture is:A multi-cloud strategy primarily aims to:Which observability practice helps a SRE diagnose a specific slow user request in a microsAn error budget is computed from an SLO. If an SLO is 99.9% success over 30 days, the erroService-level objectives (SLOs) are best described as: