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…

Question

Options

• AThey can set a limit to the number of DBUs that are consumed by the SQL Endpoint.
• BThey can set the query's refresh schedule to end after a certain number of refreshes.
• CThey cannot ensure the query does not cost the organization money beyond the first week of the
• DThey can set a limit to the number of individuals that are able to manage the query's refresh
• EThey can set the query's refresh schedule to end on a certain date in the query scheduler.

• A
  5% (1)
• C
  77% (17)
• D
  5% (1)
• E
  14% (3)

Explanation

In Databricks SQL, query refresh schedules do not support an end date or a maximum number of refreshes after which the schedule automatically stops. Options B and E describe features that do not exist in the Databricks SQL query scheduler UI. Because there is no built-in mechanism to automatically terminate a refresh schedule after a defined period or number of runs, the engineering team cannot guarantee that no compute costs will be incurred beyond the first week. The correct and honest answer is that this cannot be ensured using the query scheduler alone.

No community discussion yet for this question.