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