ADA-C01 Question 299
Single answerStepsA Snowflake administrator is troubleshooting a task that orchestrates a stored procedure and several SQL statements. The task history shows the run as FAILED, but the administrator needs to determine which individual actions completed successfully before the failure occurred so they can decide whether rerunning the workflow is safe. Which approach should the administrator use to inspect the execution at the step level?
- A
Query the task history only, because task runs do not expose lower-level execution details for the statements they invoke
- B
Use Snowsight or SQL to inspect the query history for the task run and review the individual statements/steps executed under that task execution
- C
Review the warehouse load history, because step-level execution details for a failed task are stored with warehouse utilization metrics
- D
Use ACCESS_HISTORY to identify the failed step, because it records procedural execution order and step success or failure for tasks
Show answer and explanation
Correct answer: B
Explanation
In Snowflake, task troubleshooting usually starts with task-level metadata such as TASK_HISTORY, but when an administrator must understand what happened inside a failed run, they should drill into the underlying query execution details. Query history is the appropriate place to inspect the statements issued during the task run, including statements executed by stored procedures where applicable. This aligns with Snowflake operational best practices: use task history to identify the failed run and query history to investigate the exact step or statement that failed before deciding whether a rerun is safe. Documentation areas relevant to this include Snowflake Tasks, TASK_HISTORY, and Query History in Snowsight or ACCOUNT_USAGE/INFORMATION_SCHEMA query history views and functions.
- A. Incorrect.
Incorrect. TASK_HISTORY helps identify task-level status, scheduling, error messages, and timing, but it is not sufficient by itself when the administrator needs to understand the individual statements executed within the task run. For troubleshooting a multi-statement workflow, the administrator should correlate the task run with query-level execution details.
- B. Correct.
Correct. To determine what happened within a task execution, the administrator should review the query history associated with that run, either in Snowsight or through Snowflake views/functions that expose query history. This allows inspection of the individual SQL statements executed by the task or stored procedure and helps identify which step failed and which earlier steps completed successfully.
- C. Incorrect.
Incorrect. Warehouse load history is useful for analyzing compute utilization, queuing, and performance patterns, but it does not provide a procedural breakdown of task workflow execution. An administrator might choose this option if they confuse performance telemetry with execution tracing.
- D. Incorrect.
Incorrect. ACCESS_HISTORY is designed for auditing data access, such as which objects were accessed and by whom, rather than reconstructing ordered task workflow steps or indicating statement-by-statement success within a task run. It may show object access patterns, but it is not the right tool for step-level troubleshooting of task execution.