Databricks-DA-Assoc Importing Data Practice Question
A data analyst has a 5 MB pipe-delimited text file with a header row on their local laptop and needs to load it into a Databricks Unity Catalog table for a one-time analysis. They want the fastest path with the least configuration. Which approach should they use?
⚠ Common exam trap
The trap here is assuming that any ingestion method can read a file sitting on a local laptop, when most Databricks ingestion paths require cloud storage paths.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the Add Data UI to upload the file and create the table through the guided wizard.
For a small local file that needs to become a table once, the Add Data UI is the intended workflow: it uploads the file, previews it, lets the analyst confirm delimiter and header handling, and creates the table. The other approaches assume cloud storage paths or streaming infrastructure that a laptop file simply does not have.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use the Add Data UI to upload the file and create the table through the guided wizard.
Why this is correct
The Add Data UI is designed for exactly this case: small local files uploaded through the browser, with a wizard that previews the data, lets the analyst set the delimiter and header options, and creates a Unity Catalog table without writing code. It is the fastest low-configuration path for a one-time small-file load.
- ✗
Run COPY INTO against the local filesystem path of the downloaded file.
Why it's wrong here
COPY INTO reads from cloud storage locations such as S3, ADLS, or GCS, not from a laptop filesystem. A local path would not be accessible to the compute cluster running the command. The analyst would first have to upload the file to cloud storage, which defeats the goal of a fast, low-configuration load.
- ✗
Configure an Auto Loader stream pointing at a cloud storage location to ingest the file.
Why it's wrong here
Auto Loader is built for incrementally ingesting files that arrive in cloud object storage, not for a single file sitting on a laptop. It requires a cloud path and a streaming pipeline, which adds significant setup overhead. For a one-time 5 MB local upload, this is far more configuration than the scenario needs.
- ✗
Create an external table over the local file so the data stays in place.
Why it's wrong here
External tables point at data in cloud object storage or other external systems that the metastore can reach; a file on a personal laptop is not addressable that way. Additionally, external tables do not move data into managed storage, so this approach cannot work for a purely local file.
About these practice questions
This Databricks-DA-Assoc question is part of Courseiva's 291-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DA-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DA-Assoc exam.