The DROP TABLE command removes a table from the metastore and deletes the associated data files. The syntax for this command is DROP TABLE [IF EXISTS] [database_name.] table_name;. The optional IF EXISTS clause prevents an error if the table does not exist. The optional database_name. prefix specifies the database where the table resides. If not specified, the current database is used. Therefore, the correct command to remove the table table_name from the database database_name and all of the data files associated with it is DROP TABLE database_name.table_name;. The other commands are either invalid syntax or would produce undesired results. References: Databricks - DROP TABLE

The correct answer is C because the issue is a resource constraint failure, and the analyst needs to identify which operator is consuming excessive memory. In Query Profile, Memory peak shows memory usage at the operator level and helps identify the operator causing resource overuse. Time spent helps identify slow operators, shuffle read size helps analyze data movement, and bytes spilled to disk indicates spill behavior, but the most direct metric for resource overuse due to memory pressure is memory peak.
Official documentation extract used: Databricks Query Profile graph view shows metrics such as "Time spent, Memory peak, and Rows."

Delta Lake is a storage layer that enhances data lakes with features like ACID transactions, schema enforcement, and time travel. While it stores table data as Parquet files, Delta Lake also keeps a transaction log (stored in the _delta_log directory) that contains detailed table metadata.
This metadata includes:
Table schema
Partitioning information
Data file paths
Transactional operations like inserts, updates, and deletes
Commit history and version control
This metadata is critical for supporting Delta Lake's advanced capabilities such as time travel and efficient query execution. Delta Lake does not store data summary visualizations or owner account information directly alongside the data files.

Option B is correct. Delta Lake supports time travel, which allows users to query previous table versions by timestamp or version number. The version can be obtained from table history and queried using VERSION AS OF. Restoring the table would change the current table state for everyone, which is not necessary when the analyst only needs to analyze a historical snapshot. VACUUM would remove old data files and can prevent time travel. Official Databricks extract: time travel supports "querying previous table versions," and the syntax includes SELECT * FROM people10m VERSION AS OF 123. Databricks also states that the version can be obtained from DESCRIBE HISTORY. Note: the two-week snapshot is queryable only if the required log and data files are still retained.

A Dashboard Parameter is a parameter that is configured for one or more visualizations within a dashboard and appears at the top of the dashboard. The parameter values specified for a Dashboard Parameter apply to all visualizations reusing that particular Dashboard Parameter1. Therefore, if the analyst chooses "Dashboard Parameter" for the query parameter associated with the area chart, the area chart will use whatever is selected in the Dashboard Parameter along with all of the other visualizations in the dashboard that use the same parameter. This allows the user to filter the data across multiple visualizations using a single parameter widget2. Reference: Databricks SQL dashboards, Query parameters