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?
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.