A ticketing company's checkout API calls a seat-allocation service synchronously. During on-sale events for popular concerts the allocation service is overwhelmed, calls fail, and some paid checkouts never receive seats. Allocation may complete a few minutes after checkout, but no checkout can be dropped, and allocation capacity must grow with demand. Which combination of steps should a solutions architect take? (Select TWO.)
Choose TWO.
Two halves make a spike-proof hand-off: a durable queue between producer and consumer so nothing is dropped, and a consumer tier that scales on the queue's backlog so capacity follows demand.
The stem tolerates a few minutes of delay but no loss, which is exactly what an asynchronous queue provides: SQS stores each checkout until a worker deletes it, and scaling the worker group on the queue's backlog adds allocation capacity during an on-sale event. The load balancer with request-count scaling is the near-twin: it scales, but checkouts still depend on the allocation service answering in time, so the ones caught while it is saturated fail. Retrying with backoff and jitter is good client hygiene but only postpones the failure. SNS over HTTPS is push delivery; it has no consumer-paced storage, so an endpoint that stays overwhelmed past the retry policy loses the message.
- Read the constraint: delay is acceptable, loss is not, so the hand-off can be asynchronous.
- Choose a durable buffer: SQS keeps each checkout until a worker processes and deletes it.
- Pair it with consumer scaling on the queue backlog so capacity grows with demand.
- Reject options that keep the synchronous call (load balancer, retries) or push without storage (SNS over HTTPS).
Exam tip: No-loss plus elastic capacity = SQS between the tiers and workers scaling on queue backlog.
Scalable, Loosely Coupled Architectures: SQS, SNS, EventBridge, Step Functions — the lesson that teaches this.