DATABRICKS-CERTIFIED-DATA-ENGINEER-ASSOCIATE · Question #47
A data engineering team has noticed that their Databricks SQL queries are running too slowly when they are submitted to a non-running SQL endpoint. The data engineering team wants this issue to be…
The correct answer is D. They can turn on the Serverless feature for the SQL endpoint. The core problem is startup latency - the SQL endpoint (warehouse) is not running when queries are submitted, so users must wait for it to start. Enabling the Serverless feature eliminates this cold-start delay because Serverless SQL warehouses are pre-warmed by Databricks and…
Question
Options
- AThey can turn on the Serverless feature for the SQL endpoint and change the Spot Instance Policy
- BThey can turn on the Auto Stop feature for the SQL endpoint.
- CThey can increase the cluster size of the SQL endpoint.
- DThey can turn on the Serverless feature for the SQL endpoint.
- EThey can increase the maximum bound of the SQL endpoint's scaling range.
How the community answered
(33 responses)- A3% (1)
- B3% (1)
- D91% (30)
- E3% (1)
Explanation
The core problem is startup latency - the SQL endpoint (warehouse) is not running when queries are submitted, so users must wait for it to start. Enabling the Serverless feature eliminates this cold-start delay because Serverless SQL warehouses are pre-warmed by Databricks and start almost instantly. Auto Stop controls when an idle warehouse shuts down (not startup speed), increasing cluster size improves query performance (not startup time), and scaling range affects concurrency - none of these address the cold-start problem.
Topics
Community Discussion
No community discussion yet for this question.