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