Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural layers: (1) Activity retry with backoff. (2) On failure/On success routing. (3) @activity().Error in expressions. (4) Try-catch via Execute Pipeline. (5) Web Activity → Logic App for notifications. Why: Prevent silent failures; enable alerting and traceability....
Architectural layers: (1) Activity retry with backoff. (2) On failure/On success routing. (3) @activity().Error in expressions. (4) Try-catch via Execute Pipeline. (5) Web Activity → Logic App for notifications. Why: Prevent silent failures; enable alerting and traceability. Best practice: Retry + backoff; conditional branching; log to table/Blob; Alerts + Action Groups.
Red Flag: No retry or failure handling—production blind spot. Pro-Move: 'We use retry + On Failure → Web Activity to Logic App → Teams; every failure has run ID and error in alert.'
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.