Answer: Cache hit percentage

## Analysis of the Performance Issue The scenario describes a situation where **commonly used queries** are experiencing slow performance, while **infrequently used queries** remain unaffected. This pattern strongly suggests that the issue is related to **caching behavior** rather than general resource contention. ## Why Cache Hit Percentage (Option B) is the Correct Answer ### Primary Reasoning: - **Cache Hit Percentage** directly measures how often queries are served from the result set cache versus needing to compute results from scratch - Commonly used queries should ideally have high cache hit rates, but if the cache is being invalidated or not functioning properly, these queries would need to recompute results, causing performance degradation - Infrequently used queries not being affected supports this hypothesis, as they wouldn't benefit from caching anyway ### Technical Justification: - Azure Synapse Analytics maintains a **result set cache** that stores query results for reuse - When cache hit percentage is low for frequently executed queries, it indicates: - Cache invalidation due to data modifications - Insufficient cache size - Query patterns that prevent caching - Cache configuration issues ## Why Other Options Are Less Suitable ### Option A (DWU Percentage): - Measures overall resource utilization but doesn't specifically address the pattern of only commonly used queries being affected - Would show similar patterns for all query types if it were a general resource issue ### Option C (Data Warehouse Units Used): - Represents overall resource consumption but doesn't explain why only frequently used queries are impacted - If this were the issue, all queries would likely be affected, not just commonly used ones ### Option D (Data IO Percentage): - Focuses on I/O operations but doesn't correlate with the specific pattern of commonly vs. infrequently used query performance differences - I/O issues would typically affect all queries accessing the same data ## Recommended Monitoring Approach Monitor **Cache Hit Percentage** over time, specifically correlating it with the execution of commonly used queries. A low cache hit rate for these queries would confirm the performance issue source and guide optimization efforts such as: - Adjusting cache retention policies - Increasing cache resources - Modifying query patterns to improve cacheability - Investigating data modification patterns that cause cache invalidation

Author: LeetQuiz Editorial Team