Home / DE Associate practice test / Data Ingestion and Loading / Question

Databricks Data Engineer Associate · free practice question

An engineer wants to quickly preview a few CSV files sitting in a cloud storage path from the SQL editor, just to inspect their contents, without building a…

Exam-style question on Data Ingestion and Loading from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Data Ingestion and Loading

An engineer wants to quickly preview a few CSV files sitting in a cloud storage path from the SQL editor, just to inspect their contents, without building a table or setting up any ingestion pipeline. Which approach fits this ad-hoc exploration?

  1. ARun SELECT * FROM read_files('path', format => 'csv') in the SQL editor; the read_files table-valued function reads the files in place and returns their rows with no table or pipeline defined.
  2. BRun COPY INTO to load the CSV files into a new Delta table and then query that table; SQL reads cloud files once they have been ingested into a governed table by an explicit load command.
  3. CRun CREATE TABLE ... USING CSV LOCATION 'path' to register the files as a table and then query it; a SQL SELECT reads cloud files once a table object has been defined over the storage path.
  4. DMount the cloud storage path to DBFS and run a SELECT against the mounted directory; ad-hoc SQL access to files in cloud object storage depends on a mount point being configured up front.
  5. EConfigure an Auto Loader streaming query over the path and read its output table; previewing files in cloud object storage from SQL depends on an incremental ingestion source running first.
Answer & explanation

Correct answer: A

WHY A: read_files() is a table-valued function that reads cloud files directly from SQL for an ad-hoc preview, with no table, mount or pipeline needed first.

WHY NOT B: COPY INTO loads files into a table, which is exactly the table-building step the engineer wants to avoid, and it is not a prerequisite for previewing files with SQL.

WHY NOT C: No table object is required to read files; read_files queries the path directly, and registering a table contradicts the requirement not to build one.

WHY NOT D: A DBFS mount is not required; read_files reads the cloud path directly.

WHY NOT E: Auto Loader is for incremental ingestion, not a prerequisite for an ad-hoc file preview, and it would create the pipeline and table the engineer wants to avoid.

Take the full DE Associate practice test free →

Would you pass today?

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

Start the free test →