A code-enforcement app must enqueue failed door-hanger print jobs for later retry without blocking the inspector's UI thread. Which approach should the application code take?
Select an answer to reveal the explanation.
Short Explanation
When the door-hanger printer hiccups, do not freeze the inspector's screen — drop a note on a queue and move on. SQS via the SDK keeps that job durable for a worker to retry. UI stays snappy; work still gets done.
Full Explanation
Application code should use messaging services such as Amazon SQS for durable asynchronous work that must not block interactive paths. Browser localStorage and personal email are not reliable multi-worker backbones. Synchronous vendor calls on the UI thread recreate the original blocking problem. SQS plus a worker (Lambda or otherwise) is the standard pattern for retryable offloaded jobs.