Option B is correct. The program can be scheduled to run daily as a Databricks job, and Python control flow can determine whether the final query runs only when the current day is Sunday. Databricks jobs support scheduled execution, and PySpark notebooks can run SQL through Spark while using Python logic around those commands. Official Databricks extract: jobs can be configured "to run it on a time-based schedule," and spark.sql/Spark DataFrame operations allow Python-based workflows to interact with SQL data.

Databricks SQL uses a query cache to store the results of queries that have been executed previously. This improves the performance and efficiency of repeated queries. To determine if a query result was pulled from the cache, you can go to the Query History tab in the Databricks SQL UI and click on the text of the query. A slideout will appear on the right side of the screen, showing the query details, including the cache status. If the result came from the cache, the cache status will show "Cached". If the result did not come from the cache, the cache status will show "Not cached". You can also see the cache hit ratio, which is the percentage of queries that were served from the cache. References: The answer can be verified from Databricks SQL documentation which provides information on how to use the query cache and how to check the cache status.
Reference link: Databricks SQL - Query Cache

The correct answer is C because Databricks SQL Editor is used to create and save SQL queries. A saved query can later be opened, reused, shared, visualized, and added to a dashboard. A dashboard is not the saved SQL statement itself; it is a reporting object that can contain query results and visualizations. Query History stores past executions, but it is not the correct object for saving a reusable SQL statement.
Official documentation extract used: Databricks states that the SQL editor can be used to "author queries" and
"create visualizations." It also states that the Save button "saves your query," and query results can be added to a dashboard.

Databricks SQL offers a unified platform where computations, data storage, and analytical tools coexist seamlessly. This integration allows business intelligence (BI) analytics projects to be executed more efficiently, as users can perform data processing and analysis without the need to transfer data between disparate systems. By consolidating these components, Databricks SQL streamlines workflows, reduces latency, and enhances data governance. While third-party BI tools may offer advanced dashboarding capabilities, simultaneous multi-user support, and automated alerting systems, they often require integration with separate data processing platforms, which can introduce complexity and potential inefficiencies.

Markdown-based text boxes are useful as labels on a dashboard. They allow the data analyst to add text to a dashboard using the %md magic command in a notebook cell and then select the dashboard icon in the cell actions menu. The text can be formatted using markdown syntax and can include headings, lists, links, images, and more. The text boxes can be resized and moved around on the dashboard using the float layout option. Reference: Dashboards in notebooks, How to add text to a dashboard in Databricks