Home / Data Analyst practice test / Importing Data / Question

Databricks Data Analyst Associate · free practice question

A business analyst with no engineering background wants to load a 15 MB CSV file of monthly sales data into Databricks for ad-hoc analysis in a SQL notebook…

Exam-style question on Importing Data from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Importing Data

A business analyst with no engineering background wants to load a 15 MB CSV file of monthly sales data into Databricks for ad-hoc analysis in a SQL notebook. The analyst has Contributor access to a Unity Catalog workspace. A colleague suggests using the Databricks Workspace UI file upload feature. Which description MOST ACCURATELY describes the file upload experience and what happens to the data after the upload completes?

  1. AThe Workspace UI file upload is reserved for workspace administrators; Contributor-level users do not see it, as uploads bypass Unity Catalog lineage capture and Databricks limits that bypass to administrators. After an administrator uploads the CSV, the raw file sits in the chosen schema, and the analyst converts it to a Delta table by running CONVERT TO DELTA in a SQL notebook before it can be queried with the three-part namespace.
  2. BThe Workspace UI upload accepts Apache Parquet and ORC files, as those formats embed the schema metadata the wizard uses to generate the CREATE TABLE statement. The analyst first converts the CSV to Parquet on a local machine, for example with pandas.DataFrame.to_parquet(), and then uploads it; a CSV submitted directly raises an 'UnsupportedFileTypeException' in the wizard. The resulting table is a managed Delta table.
  3. CThe Workspace UI upload places the raw CSV file in the DBFS root at dbfs:/FileStore/tables/ and creates no table; the upload step has no awareness of Unity Catalog catalogs or schemas. The analyst then opens a notebook, parses the file with a PySpark spark.read.csv() command, and persists it with .write.format('delta').saveAsTable('catalog.schema.table_name') before it can be queried in the SQL notebook.
  4. DThe analyst uploads the CSV from a local machine through the Workspace UI, using the 'Add data' or 'Create table' workflow or the upload entry point in Catalog Explorer. The wizard previews the parsed data, lets the analyst adjust inferred column types and names, and asks for a target catalog and schema. On completion, Databricks writes the data to a new managed Delta table that is queryable as catalog.schema.table with no separate conversion step.
  5. EThe Workspace UI upload creates a temporary table that lasts for the current browser session; when the analyst closes the workspace tab or the session times out, the table and its data are removed, as upload tables live in an in-memory session-scoped schema. For a persistent table, the analyst runs the CLI command databricks fs cp localfile.csv dbfs:/tables/ and then loads the file with a COPY INTO SQL statement.
Answer & explanation

Correct answer: D

WHY D: The Workspace UI offers a data upload experience for non-admin users with appropriate workspace access (Contributor). The flow, reachable from the SQL Editor's 'Add data' button, AI/BI Dashboard dataset upload, or Catalog Explorer, lets analysts upload files (including CSV) from a local machine. The wizard previews the data, infers column names and data types and allows adjustments, and the target Unity Catalog catalog and schema are selected in the wizard. On completion, Databricks stores the data as a new managed Delta table in that location, queryable right away with the standard three-part namespace and no further conversion or code. The experience is designed for non-technical users who need to bring small datasets into the platform quickly.

WHY NOT A: File upload in the Workspace UI is not restricted to workspace administrators; it is available to users with appropriate permissions such as Contributor. The wizard also creates a Delta table directly, so no manual CONVERT TO DELTA step is needed.

WHY NOT C: The modern, Unity Catalog-integrated upload flow does not drop files in the DBFS root at dbfs:/FileStore/tables/ and leave a raw file to parse by hand; the wizard handles parsing, type inference and table creation. The DBFS-based pattern is a legacy workflow that this wizard has superseded.

WHY NOT B: The upload feature supports CSV files, one of the wizard's primary use cases, so nothing has to be pre-converted to Parquet. The wizard parses the CSV, infers the schema and creates a Delta table, and no 'UnsupportedFileTypeException' is raised for CSV uploads.

WHY NOT E: Tables created through the file upload are persistent managed Delta tables in Unity Catalog-managed cloud storage, not session-scoped or in-memory. They survive browser session closures, workspace restarts and cluster terminations like any other managed Delta table. The CLI plus COPY INTO route is a valid alternative but is not required for persistence.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →