Monitor and Tune Workloads ARA-C01 Practice Questions (Page 5)

Questions 21–24

1. 21foundation · easy

   Which Snowflake feature allows you to proactively monitor warehouse credit usage and receive notifications when a threshold is exceeded?

   • AQuery Profile.
   • BResource monitors with alert actions.
   • CAutomatic Clustering.
   • DSearch Optimization Service.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   In the Query Profile, you see that one operator has a very high 'Percentage of Time' compared to others. What is the most direct way to interpret this?

   • AThe operator is reading data from a remote region.
   • BThe operator is spilling data to disk.
   • CThe operator is using a suboptimal clustering key.
   • DThe operator is the most likely bottleneck in the query execution.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   A warehouse is configured with 'Auto-Suspend = 5 minutes' and 'Auto-Resume = true'. What is the primary benefit of this configuration?

   • AIt reduces cost by suspending the warehouse when idle, while auto-resume allows it to start automatically for new queries.
   • BIt improves query performance by keeping the warehouse warm.
   • CIt ensures the warehouse never suspends, so queries always run immediately.
   • DIt prevents concurrent queries from conflicting with each other.
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   A data engineer is troubleshooting a slow query. The Query Profile shows a 'Join' node with 'Left Input' = 10 million rows and 'Right Input' = 10 million rows, but the 'Output' is 100 million rows. The join is on a non-unique column. The query runs on a Medium warehouse and takes 15 minutes. The engineer notices that the right input is being read from a table that has a clustering key on the join column. What is the most likely cause of the slow performance?

   • AThe join is producing a large intermediate result due to a fan-out, causing spilling.
   • BThe query is scanning too many files due to poor file sizing.
   • CThe warehouse is too small to handle the join.
   • DThe clustering key on the right table is causing the join to be slower.
   Reveal Solution Discussion Select an answer first