Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural logic: Retry handles transient failures; Catch routes terminal failures to notifications or DLQ. Config: Retry with ErrorEquals, IntervalSeconds, BackoffRate, MaxAttempts; Catch with Next (e.g., NotifyFailure). Example: Lambda.ServiceException retry 3x with...
Architectural logic: Retry handles transient failures; Catch routes terminal failures to notifications or DLQ. Config: Retry with ErrorEquals, IntervalSeconds, BackoffRate, MaxAttempts; Catch with Next (e.g., NotifyFailure). Example: Lambda.ServiceException retry 3x with exponential backoff; States.ALL → NotifyFailure (SNS). Why: Observability; no lost failures. Best practice: Retry for transient; Catch for terminal; DLQ for replay; log execution ARN.
Red Flag: No Catch block—failures disappear. Pro-Move: 'We Catch States.ALL, write to DynamoDB, and SNS to Slack—every failure is traced and replayable.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.