Home › AWS SysOps Associate › cloudcomputing › sysopsdeployment › Which rollout strategy minimises blast radius wh…
Which rollout strategy minimises blast radius when shipping a risky change to a fleet of EC2 instances?
ACanary: deploy to a small percentage of instances first, monitor metrics, then expand
BBig-bang: redeploy plus restart every instance during business hours
CAll-at-once: redeploy 100% of instances simultaneously
DManual: ssh into each instance and run a script with no monitoring
Answer & Solution
Correct answer: A. Canary: deploy to a small percentage of instances first, monitor metrics, then expand
Canary contains risk by exposing only a small slice first. All-at-once and big-bang increase risk; manual SSH defeats the point.
Related questions
Which feature of AWS Resource Access Manager (RAM) lets one account share resources like sA CloudFormation stack fails midway with an `IAM role doesn't have permission` error and lWhich AWS service lets a team package and version their own internal application configuraA new EC2 launch in a private subnet repeatedly fails to download a yum package. The instaWhich CloudFormation feature lets you reference a value created in one stack from another Which combination correctly provisions a centrally-managed multi-account landing zone for Which AWS Systems Manager capability lets administrators run a documented automation sequeAn organisation needs to deploy a new version of a web app to 100 EC2 instances behind an