You have a CSV file locally with a static list of company office locations. You need to recommend a method to perform a one-time copy to ingest the CSV file into the lakehouse with minimal administrative effort.

You have a CSV file locally with a static list of company office locations. You need to recommend a method to perform a one-time copy to ingest the CSV file into the lakehouse with minimal administrative effort.

• A. a data factory pipeline
• B. a local file upload by using Lakehouse explorer
• C. external table
• D. manual SQL insert

Answer: (B)

Uploading the file directly from your local machine using the Lakehouse Explorer local file upload is the simplest way to bring a one-off CSV into the lakehouse. It requires almost no setup—no pipelines to build, no external data sources to manage, and no manual row-by-row inserts. The CSV is copied into lakehouse storage and can be registered as a table or viewed as a ready-to-query dataset right away. Using a data factory pipeline would add unnecessary overhead for a single, one-time load, especially if you don’t need ongoing automation. An external table references data stored elsewhere rather than ingesting it, which means you’re not actually making a true copy in the lakehouse. Manual SQL inserts would be tedious and error-prone for a sizable CSV and are not the efficient path for a quick, minimal-effort ingestion.

Uploading the file directly from your local machine using the Lakehouse Explorer local file upload is the simplest way to bring a one-off CSV into the lakehouse. It requires almost no setup—no pipelines to build, no external data sources to manage, and no manual row-by-row inserts. The CSV is copied into lakehouse storage and can be registered as a table or viewed as a ready-to-query dataset right away.

Using a data factory pipeline would add unnecessary overhead for a single, one-time load, especially if you don’t need ongoing automation. An external table references data stored elsewhere rather than ingesting it, which means you’re not actually making a true copy in the lakehouse. Manual SQL inserts would be tedious and error-prone for a sizable CSV and are not the efficient path for a quick, minimal-effort ingestion.