Exam Certified Data Engineer Associate topic 1 question 38 discussion

Just got 100% on the test. E was correct. C was not in the available options.

The query scheduler only gives the option on what the interval is to run the query. It does not provide a way to stop after x iterations or at a point in time. The question is confusing. From what i found the only option is to limit users access to the query (and therefore query scheduler). https://docs.databricks.com/security/auth-authz/access-control/query-acl.html Not convinced how this would be helping the organization save money if no-one is manually stopping the schedule. Answer C seems most correct Answer D can be achieved using acl however how is this helpful in the use case described?

Option E is correct. Although there in not an 'direct' option to select an end date, cron expressions allows run schedules on a specific time period (in this case a specific week).

Answer is E. There is an option to specify schedule with CRON syntax which enables to set schedule for a chosen week. For example, when you specify CRON: 0 0 0 23-29 SEP ? 2024, the query will be run At 12:00 AM, between day 23 and 29 of the month, only in September 2024.

E is correct because the engineering team can use the query scheduler in Databricks to set a specific end date for the query refresh schedule. This way, after the first week, the automatic refreshes will stop, and the associated compute costs will be avoided.

The correct answer is E for this question.

Answer is E

Answer is E It´s true natively the query can´t be scheduled to stop, but the scheduler allow us to use cron syntax. So we can define the year, month and days of the first week and the trigger won´t run after that

The query scheduler does not give option to have end date (or iterations). Dashboards might give one, but the question specifically mentions queries. https://learn.microsoft.com/en-gb/azure/databricks/sql/user/queries/schedule-query

E. They can set the query’s refresh schedule to end on a certain date in the query scheduler. Explanation: Query Scheduler: Databricks offers a Query Scheduler that allows users to schedule the execution of SQL queries at specific intervals or for specific durations. Setting a Specific End Date: The team can configure the query's refresh schedule to conclude or end on a certain date. By specifying an end date within the first week of the project's release, the query will automatically stop refreshing after that date. This action ensures that compute resources aren't continuously utilized beyond the specified timeframe, preventing unnecessary costs. This approach allows the team to control and limit the execution of the query to the required duration without incurring additional costs beyond the first week of the project's release.

C is the correct answer Source : https://docs.databricks.com/en/sql/user/queries/schedule-query.html

E is the correct answer. From the docs: If a dashboard is configured for automatic updates, it has a Scheduled button at the top, rather than a Schedule button. To stop automatically updating the dashboard and remove its subscriptions: Click Scheduled. In the Refresh every drop-down, select Never. Click Save. The Scheduled button label changes to Schedule. Source: https://learn.microsoft.com/en-us/azure/databricks/sql/user/dashboards/

Option E is correct answer

The picker scrolls and allows you to choose: An interval: 1-30 minutes, 1-12 hours, 1 or 30 days, 1 or 2 weeks Since the schedule picker allows to choose interval to refresh query every 1 or 2 weeks. If we choose 1 week the schedule ends after a week. So the answer is B.

Correct Answer E.

agree with BigDaddyAus

Answer is C. According to documentation it cant be scheduled up until a certain date. It has to be in intervals and then canceled manually. They don't mention end date. Only start date and intervals. https://docs.databricks.com/en/workflows/jobs/schedule-jobs.html