Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Debug flow: (1) Monitor → Pipeline runs → filter Failed. (2) Activity details → Error tab. (3) Output → View Data for counts/samples. (4) Diagnostic settings → Log Analytics; Kusto queries. (5) SHIR: Windows Event Log, IR logs. Example: Connection timeout → verify SHIR...
Debug flow: (1) Monitor → Pipeline runs → filter Failed. (2) Activity details → Error tab. (3) Output → View Data for counts/samples. (4) Diagnostic settings → Log Analytics; Kusto queries. (5) SHIR: Windows Event Log, IR logs. Example: Connection timeout → verify SHIR reachability, firewall. Best practice: Detailed error in expressions; retry with logging; Alerts on failure; run ID in logs.
Red Flag: No diagnostic settings—blind debugging. Pro-Move: 'We send all runs to Log Analytics; Kusto query by run ID—mean time to resolution dropped 50%.'
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.