Question 91

An analyst reports that a dashboard query against a serverless SQL warehouse returns instantly but "doesn't reflect the new data we just merged." You investigate: - The underlying Delta table was updated by a `MERGE` 10 minutes ago. - When the analyst re-runs the exact same query text, results are still instant and you cannot open a **query profile** for that run. - You need to (1) force the query to actually execute so the new data is returned and (2) be able to open the query profile to analyze the execution. Which action both forces fresh execution and makes a query profile available?

• AMake a trivial change to the query (for example, change or remove the `LIMIT`) so it bypasses the result cache; the next run executes and a query profile becomes available.
• BRun `OPTIMIZE` on the Delta table; this invalidates Azure Databricks query caching and forces re-execution with a profile.
• CRestart the SQL warehouse; the remote result cache is tied to the warehouse and is cleared on restart, so the next run re-executes.
• DIncrease `spark.sql.shuffle.partitions`; this disables result caching for the session and produces a query profile.