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....
This easy-level Cloud/Tools question appears frequently in data engineering interviews at companies like Deloitte. While less common, it tests deeper understanding that distinguishes strong candidates.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
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.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer β FreeAccording to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.