A 311 intake fleet on Auto Scaling may terminate instances during scale-in. In-flight citizen reports must not be lost when a worker dies. Which design best prevents lost work?
Select an answer to reveal the explanation.
Short Explanation
Don’t keep the only copy of a 311 report in a worker’s short-term memory. Park it on a durable queue, hide it while working, and make handlers safe to retry.
Full Explanation
Design-for-failure patterns keep work on durable queues with visibility timeouts and idempotent consumers so instance termination does not lose in-flight messages. Memory-only or ephemeral-disk processing creates data loss on scale-in. Freezing Auto Scaling avoids termination but does not create recoverability and harms elasticity. For municipal 311, queue-backed idempotent workers are the reliability pattern.