Question 520
For this Snowflake situation — A resource-intensive scan affects unrelated work and the team considers using Query Acceleration Service. — the team adopts: Evaluate supported Query Acceleration Service for an eligible query and compare performance against additional compute costs. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Track acceleration usage and scan-related query profiles after enabling the service. It controls the recurring exposure associated with this mechanism: Query Acceleration Service can offload eligible scan-heavy work to shared compute, subject to feature criteria. The original action, evaluate supported Query Acceleration Service for an eligible query and compare performance against additional compute costs., still needs operational checks when the environment or workload changes.
Incorrect Answers
The suggested review tracks a different technical risk: Warehouse cache is tied to active compute resources and is not a durable store across suspension. Here the sustained control must address: Query Acceleration Service can offload eligible scan-heavy work to shared compute, subject to feature criteria. Choose “Track acceleration usage and scan-related query profiles after enabling the service”.
That safeguard is relevant to: End-to-end latency can be limited by waiting for source data rather than SQL execution speed. The current failure instead follows from: Query Acceleration Service can offload eligible scan-heavy work to shared compute, subject to feature criteria. Its prevention measure is “Track acceleration usage and scan-related query profiles after enabling the service”.
This routine guards against another mechanism: Unstructured files are managed and discovered differently from ordinary scalar table columns. The recurring exposure in the current case is: Query Acceleration Service can offload eligible scan-heavy work to shared compute, subject to feature criteria. The matching preventive check is “Track acceleration usage and scan-related query profiles after enabling the service”.