DATABRICKS-CERTIFIED-DATA-ENGINEER-ASSOCIATE · Question #66
A data analysis team has noticed that their Databricks SQL queries are running too slowly when connected to their always-on SQL endpoint. They claim that this issue is present when many members of…
The correct answer is B. They can increase the maximum bound of the SQL endpoint's scaling range. The problem is high concurrency: many users running small queries simultaneously. A SQL endpoint (warehouse) can scale out by adding more clusters to handle concurrent queries. Increasing the maximum bound of the scaling range allows the endpoint to spin up additional clusters…
Question
Options
- AThey can increase the cluster size of the SQL endpoint.
- BThey can increase the maximum bound of the SQL endpoint's scaling range.
- CThey can turn on the Auto Stop feature for the SQL endpoint.
- DThey can turn on the Serverless feature for the SQL endpoint.
- EThey can turn on the Serverless feature for the SQL endpoint and change the Spot Instance Policy
How the community answered
(40 responses)- A13% (5)
- B78% (31)
- C5% (2)
- D3% (1)
- E3% (1)
Explanation
The problem is high concurrency: many users running small queries simultaneously. A SQL endpoint (warehouse) can scale out by adding more clusters to handle concurrent queries. Increasing the maximum bound of the scaling range allows the endpoint to spin up additional clusters when demand is high, reducing queue wait time and improving latency. Increasing cluster size (option A) improves performance for individual large queries, not concurrency. Auto Stop (option C) reduces cost but does not help latency. Serverless (option D/E) may help but is not the most direct answer to a scaling range configuration question.
Topics
Community Discussion
No community discussion yet for this question.