During a late-night outage, a transit-authority developer finds a misconfigured runtime on a production host and is tempted to SSH in and edit files until the service recovers. Which immutable-infrastructure response is the cloud-native alternative?
Select an answer to reveal the explanation.
Short Explanation
Immutability is like swapping a broken streetlight bulb for a known-good one instead of soldering inside the old housing at midnight. You launch a fresh revision and retire the bad one. Rollback becomes redeploying yesterday’s artifact, not scavenging a drifted box.
Full Explanation
Immutable infrastructure treats hosts and images as disposable: when something is wrong, you replace it with a known-good revision rather than mutating production in place. That keeps environments reproducible and makes rollback a redeploy of a prior artifact. Live patching, silencing health checks, and serving from laptops increase drift and risk.