You are responsible for managing a Snowflake environment where data loading and transformation are performed. You need to monitor the resource consumption of various tasks and identify potential bottl

Question

Options

• AACCOUNT USAGE.WAREHOUSE LOAD HISTORY
• BACCOUNT USAGE.TASK HISTORY
• CACCOUNT_USAGE.QUERY HISTORY and join it with ACCOUNT_USAGE.WAREHOUSE
• DDATABASE STORAGE USAGE HISTORY
• EINFORMATION SCHEMA.TABLES

• A
  2% (1)
• B
  76% (32)
• C
  12% (5)
• D
  2% (1)
• E
  7% (3)

Explanation

ACCOUNT_USAGE.TASK_HISTORY is correct because it is specifically designed to expose per-task execution metadata, including the warehouse used, execution duration, error messages, and status - exactly what you need to identify bottlenecks in task-based pipelines.

Why the distractors are wrong:

• A. WAREHOUSE_LOAD_HISTORY shows aggregate warehouse credit consumption over time, not individual task breakdowns - useful for capacity planning, not task-level debugging.
• C. QUERY_HISTORY joined with WAREHOUSE gives raw query execution details, but tasks are orchestrated workflows; correlating them with queries requires extra effort and TASK_HISTORY already surfaces the relevant metrics directly.
• D. DATABASE_STORAGE_USAGE_HISTORY tracks storage consumption (bytes), not compute or execution time - entirely different concern.
• E. INFORMATION_SCHEMA.TABLES is a DDL/metadata view about table structure; it has nothing to do with execution or resource consumption.

Memory tip: Think "task monitoring = TASK_HISTORY." Snowflake follows a naming convention where the object type matches the history view - TASK_HISTORY is your go-to any time an exam question pairs tasks with execution time, warehouse usage, or bottlenecks.

No community discussion yet for this question.