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 approach 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 can set the query's refresh schedule to end on a certain date in the query scheduler.
D
They can set a limit to the number of individuals that are able to manage the query's refresh schedule.
Explanation:
Explanation
The correct answer is C because:
-
Query Scheduler End Date Feature: Databricks SQL provides a query scheduler that allows users to set up scheduled refreshes for queries. One of the key features is the ability to specify an end date for the schedule.
-
Preventing Unnecessary Costs: By setting the refresh schedule to end on a specific date (e.g., one week after the project release), the query will automatically stop refreshing after that date. This ensures that compute resources are not left running indefinitely, preventing unnecessary costs.
-
Why Other Options Are Incorrect:
- Option A: Setting a limit to DBUs consumed by the SQL Endpoint doesn't address the specific time-bound requirement. It might limit overall consumption but doesn't automatically stop the query after one week.
- Option B: Setting a limit to the number of refreshes could work in theory, but it's less precise than setting an end date. The manager would need to calculate exactly how many refreshes occur in one week (e.g., 10,080 refreshes for 7 days × 24 hours × 60 minutes), which is error-prone and less maintainable.
- Option D: Limiting who can manage the refresh schedule doesn't prevent the query from continuing to run; it only controls administrative access.
-
Best Practice: Using the end date feature in the query scheduler is the most direct and reliable way to ensure the query stops refreshing after a specific period, aligning perfectly with the requirement to monitor for exactly one week after project release.
Comments
Loading comments...