Home / Data Analyst practice test / Importing Data / Question

Databricks Data Analyst Associate · free practice question

A data analyst needs to upload a 5 MB comma-delimited CSV file to Databricks using only the Workspace UI — without writing any code or using the CLI. The file…

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 data analyst needs to upload a 5 MB comma-delimited CSV file to Databricks using only the Workspace UI — without writing any code or using the CLI. The file has a header row and several columns where the inferred data types are incorrect (for example, a column named order_id is inferred as DOUBLE instead of STRING, and order_date is inferred as STRING instead of DATE). Which statement CORRECTLY describes what the analyst can do during the UI upload workflow to fix the type issues before the table is created, and what format the table will be stored in?

  1. AThe upload wizard shows a preview of the parsed data, and the analyst can override the inferred type of individual columns before the table is created, for example changing order_id from DOUBLE to STRING and order_date from STRING to DATE; column names can be edited as well. After the analyst confirms the schema and picks a target catalog and schema, Databricks writes the data as a managed Delta table in Unity Catalog storage, not as a CSV file.
  2. BThe upload wizard infers column types from the CSV header row and does not parse data rows, so the types it shows are a first guess that stays fixed until the table exists. The analyst corrects them afterwards in the SQL Editor with ALTER TABLE catalog.schema.table_name ALTER COLUMN order_id TYPE STRING and the matching statement for order_date. The uploaded table is stored in CSV format on cloud storage to preserve the original file layout.
  3. CThe upload wizard infers types from a statistical profile of the first 1,000 rows and locks them in; overrides are not offered in the wizard, as changing a type would alter how row values are parsed. The table is created with the inferred types and stored in Parquet format. To make order_id a STRING and order_date a DATE, the analyst recreates the table with a CREATE OR REPLACE TABLE statement that casts the columns in its SELECT.
  4. DThe upload creates an external table that points to the uploaded CSV file in DBFS rather than a managed Delta table, and the wizard derives its types from metadata in the CSV header, so they are not editable there. To correct order_date, the analyst renames the header column to order_date_DATE; the Databricks CSV reader recognizes this suffix convention and casts the column to DATE at query time. The table stays in CSV format.
  5. EThe upload wizard lets the analyst change types between numeric and string columns, so order_id can go from DOUBLE to STRING, but DATE and TIMESTAMP are not offered, as date parsing needs a locale and format string. The analyst keeps order_date as STRING and converts it in a downstream view with CAST(order_date AS DATE). The table is stored in Delta format but marked read-only until it is copied with CREATE TABLE ... DEEP CLONE.
Answer & explanation

Correct answer: A

WHY A: The Workspace UI upload wizard includes a schema preview and editing step in which the analyst sees a sample of the parsed data and can change the inferred type of any column before the table is created. Changing order_id from DOUBLE to STRING and order_date from STRING to DATE are both standard adjustments, and column names can be edited in the same step. After the analyst confirms the schema and selects a target catalog and schema in Unity Catalog, Databricks stores the data as a managed Delta table, not as a CSV file. Delta gives ACID transactions, time travel, schema enforcement, and full SQL DML support from the moment the table exists.

WHY NOT B: The wizard parses data rows, not just the header, to infer column types, and it lets the analyst change inferred types before the table is created. The resulting table is stored in Delta format, not CSV. A post-upload ALTER COLUMN is unnecessary when the corrections are made in the wizard.

WHY NOT C: The wizard does not lock in inferred types; column type overrides are part of the schema editing step. Tables created through the wizard are in Delta format, not Parquet: Delta uses Parquet files as its storage layer, but the table format is Delta with its transaction log.

WHY NOT D: The wizard creates a managed Delta table in Unity Catalog storage, not an external table over a CSV in DBFS. Types are inferred from actual data values, not from header metadata, and the order_date_DATE suffix convention is fabricated and does not exist in Databricks.

WHY NOT E: The wizard supports type changes for every column type, including DATE and TIMESTAMP: users pick DATE, TIMESTAMP, STRING, INT, BOOLEAN and other types from a dropdown in the schema editing step. The resulting tables are standard managed Delta tables with full read/write DML; there is no read-only restriction and no DEEP CLONE is required.

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 →