What steps are typically involved in troubleshooting query performance issues in Snowflake? (Select all that apply)

Question

Options

• AAnalyzing system hardware for faults
• BModifying warehouse configurations
• CReviewing query history and usage logs
• DExamining Query Profile attributes

• A
  17% (4)
• B
  83% (20)

Explanation

Troubleshooting query performance in Snowflake is handled entirely within the Snowflake platform using its built-in tools and configurations. Reviewing query history and usage logs (C) lets you identify slow or resource-heavy queries over time, while examining Query Profile attributes (D) gives you a visual breakdown of execution steps, bottlenecks, and operator-level stats for a specific query. Modifying warehouse configurations (B) - such as scaling up size or enabling multi-cluster warehouses - directly addresses performance constraints tied to compute resources.

Option A is wrong because Snowflake is a cloud-managed SaaS platform; you have no access to underlying hardware, and hardware faults are handled entirely by the cloud provider (AWS/Azure/GCP), not the user.

Memory tip: Think "WHL" - Warehouse config, History logs, Look at Query Profile. All three are Snowflake-native actions you control; anything outside the platform (like hardware) is off-limits.

No community discussion yet for this question.