A municipal web tier must replace unhealthy instances automatically without waiting for human change windows. Which architecture best meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
Self-healing fleets swap a bad snowplow without waiting for Monday’s meeting. Auto Scaling plus ELB health checks retire sick instances automatically. One pet server, mandatory CAB during outages, or ignoring health checks leaves citizens staring at an error page.
Full Explanation
Architectures that recover from failure use Auto Scaling groups and Elastic Load Balancing health checks to detect unhealthy instances and launch replacements without manual intervention. That pattern meets municipal uptime goals when change windows cannot gate emergency replacement. Single manually managed instances, freezing replacements behind change boards during outages, or disabling health checks prevent automatic recovery.