Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
An engineering manager wants to monitor the performance of a recent project using a Databricks SQL query. For the first week following the project's release, the manager wants the query results to be updated every minute. However, the manager is concerned that the compute resources used for the query will be left running and cost the organization a lot of money beyond the first week of the project's release. Which of the following approaches can the engineering team use to ensure the query does not cost the organization any money beyond the first week of the project's release?
Real Exam
Community
KKeng
A
They can set a limit to the number of DBUs that are consumed by the SQL Endpoint.
B
They can set the query's refresh schedule to end after a certain number of refreshes.
C
They cannot ensure the query does not cost the organization money beyond the first week of the project's release.
D
They can set a limit to the number of individuals that are able to manage the query's refresh schedule.
E
They can set the query's refresh schedule to end on a certain date in the query scheduler.
Explanation:
Explanation
Correct Answer: E - They can set the query's refresh schedule to end on a certain date in the query scheduler.
Why E is correct:
In Databricks SQL, when scheduling a query, you can set an end date for the schedule. This allows you to specify exactly when the scheduled refreshes should stop. For the scenario described:
- The manager wants updates every minute for the first week
- They want to ensure no costs beyond that first week
- By setting the schedule to end on the date marking the end of the first week, the query will automatically stop running after that date, preventing any further compute costs.
Why other options are incorrect:
A: Setting a DBU limit on the SQL Endpoint would only throttle queries if they exceed the limit, but wouldn't stop the query from running entirely. The query would still incur costs up to the limit.
B: The query scheduler in Databricks SQL does not provide an option to end after a certain number of refreshes. You can only set frequency (every minute, hour, day, etc.) and an end date.
C: This is incorrect because Databricks SQL does provide mechanisms to control when scheduled queries stop running.
D: Limiting who can manage the refresh schedule doesn't prevent the query from running and incurring costs. It only controls administrative access.
Key Takeaway: When scheduling queries in Databricks SQL for time-bound monitoring purposes, always set an appropriate end date to prevent unnecessary compute costs after the monitoring period ends.
Comments
Loading comments...