The mean value of a variable is the average of all the values in a data set, calculated by dividing the sum of the values by the number of values. The median value of a variable is the middle value of the ordered data set, or the average of the middle two values if the data set has an even number of values. The mean value is sensitive to outliers, which are values that are very different from the rest of the data. Outliers can skew the mean value and make it less representative of the central tendency of the data. The median value is more robust to outliers, as it only depends on the middle values of the data. Therefore, when the variable contains a lot of extreme outliers, the mean value and the median value will be meaningfully different, as the mean value will be pulled towards the outliers, while the median value will remain close to the majority of the data1. References: Difference Between Mean and Median in Statistics (With Example) - BYJU'S

Option D is correct. A temporary view is session-scoped and does not store physical data. It is suitable when the relational object is only needed in the current session or query context and should not be available to others in other sessions. A regular view also avoids copying physical data, but it is persistent and can be shared beyond the current session. Official Databricks extract: a view is a "virtual table that has no physical data," and temporary views are scoped to the notebook/script or query level and cannot be referenced outside that scope.

Data engineers are primarily responsible for building, managing, and optimizing data pipelines and architectures. They use Databricks Data Science and Engineering service to perform tasks such as data ingestion, transformation, quality, and governance. Data engineers may use Databricks SQL as a secondary service to query, analyze, and visualize data from the lakehouse, but this is not their main focus. References: Databricks SQL overview, Databricks Data Science and Engineering overview, Data engineering with Databricks

Option D is correct. Gold tables are refined, business-ready datasets used for analytics, dashboards, reporting, and other downstream consumption. A workload that queries aggregated data designed to feed a dashboard is therefore using Gold-layer data. Raw streaming ingestion belongs to Bronze, cleaning malformed records belongs to Silver, and aggregating uncleaned data is not the recommended Gold pattern. Official Databricks extract: the Gold layer "consists of aggregated data tailored for analytics and reporting" and is optimized for
"queries and dashboards."

Option E is correct. The Depends On field is used to define task dependencies in a Databricks job, so a downstream task waits for an upstream task according to the dependency rules. The standard use case is when one task must complete successfully before the next task starts. Official Databricks extract: "You can control the execution order of tasks by specifying dependencies between them," and Databricks runs upstream tasks before downstream tasks.