Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
An engineering manager is overseeing the performance of a newly released project and requires frequent updates on its status. Specifically, for the first week post-launch, the manager needs the project performance data to be refreshed every minute using a Databricks SQL query. The manager, however, is worried about the potential financial burden if the compute resources continue running beyond the first week, resulting in unnecessary costs for the organization. What strategy can the engineering team implement to guarantee that these query computations cease after the initial week, thereby preventing any additional expenses?
An engineering manager is overseeing the performance of a newly released project and requires frequent updates on its status. Specifically, for the first week post-launch, the manager needs the project performance data to be refreshed every minute using a Databricks SQL query. The manager, however, is worried about the potential financial burden if the compute resources continue running beyond the first week, resulting in unnecessary costs for the organization. What strategy can the engineering team implement to guarantee that these query computations cease after the initial week, thereby preventing any additional expenses?
Explanation:
The best approach for the engineering team to ensure the query does not cost the organization any money beyond the first week of the project’s release is to set the query’s refresh schedule to end on a certain date in the query scheduler. This allows the team to automatically stop the query refresh after the specified period, ensuring that no additional compute resources are used and thus preventing unnecessary costs.