Retry and failure behavior depends on invocation source. A handler should tolerate eligible repeated events and identify one logical operation.
Before you start
You should understand regions, identity permissions and the responsibilities of the AWS service being discussed. Sketch request flow and failure boundaries before choosing configuration. Work through these scenarios as designs; provisioning real resources can introduce charges and requires an account-specific permissions and capacity plan.
The practical goal is to reason through this situation: An event-triggered processor stores the event’s business identity with its update. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Read the event-source contract
Synchronous, asynchronous and queue-driven paths have different failure behavior.
Step 2: Preserve business identity
Repeated events must represent one logical mutation where required.
Step 3: Configure recovery
Use the source’s supported failure handling and observable outcomes.
Worked scenario
An event-triggered processor stores the event’s business identity with its update.
A queue-driven handler processes an event successfully but acknowledgment fails. It can receive the event again. Its business record should recognize the same event identity rather than issuing another payment. A generic statement that ‘Lambda retries’ is insufficient without identifying the invocation source and its configured behavior.
Common mistake
Assuming every invocation source retries identically creates missing or duplicate processing.
Verify the behavior
Test repeated events and source-specific failure destinations.
Interview exercise
Design failure handling.
Answer and reasoning
Read the source’s delivery contract, configure its supported failure destination and make side effects idempotent.
Continue learning
Compare the scenario with the AWS interview questions and test your understanding with the AWS MCQs. For terminology and implementation details, consult the reference material.