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

Databricks Data Engineer Associate · free practice question

A team must ingest CRM records from Salesforce into Unity Catalog-governed tables on a reliable schedule, with minimal custom code and managed handling of…

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

A team must ingest CRM records from Salesforce into Unity Catalog-governed tables on a reliable schedule, with minimal custom code and managed handling of incremental changes. The source is a SaaS application, not files in cloud storage. Which ingestion approach is the best fit?

  1. AAuto Loader pointed directly at the Salesforce REST API endpoint, relying on cloudFiles to incrementally poll and pull records from the SaaS application the same way it discovers new files that land in cloud object storage.
  2. BA manual routine where an analyst exports CSV files from Salesforce every morning, emails them to the engineering team, and someone uploads the attachments into a volume so the target tables can be refreshed by hand.
  3. CA COPY INTO command that uses the Salesforce account URL as its source location, since COPY INTO can authenticate to SaaS APIs and incrementally load their records into a governed Delta table on a fixed schedule.
  4. DA Structured Streaming job that reads Salesforce as if it were a Kafka topic, on the basis that enterprise SaaS platforms expose a Kafka-compatible interface that a streaming query can consume for incremental capture.
  5. EA Lakeflow Connect managed connector for Salesforce, which handles authentication, incremental change extraction via a cursor column, and scheduled landing into Unity Catalog tables with very little custom code required.
Answer & explanation

Correct answer: E

WHY E: Lakeflow Connect managed connectors are purpose-built for SaaS sources like Salesforce — they manage auth, incremental pulls (cursor column), and landing into UC tables with little code. WHY NOT A: Auto Loader ingests files from cloud object storage, not arbitrary REST/SaaS API endpoints. WHY NOT C: COPY INTO loads files from a cloud storage location, not SaaS APIs. WHY NOT D: Salesforce does not expose a Kafka topic interface; this premise is false. WHY NOT B: Manual CSV export and email is neither reliable, scheduled, nor low-maintenance.

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 →