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

Databricks Data Engineer Associate · free practice question

A data engineer must ingest data from a SaaS Salesforce source and a self-managed SQL Server database into Unity Catalog tables using Lakeflow Connect managed…

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 data engineer must ingest data from a SaaS Salesforce source and a self-managed SQL Server database into Unity Catalog tables using Lakeflow Connect managed connectors. Which statement correctly describes how these managed connectors operate?

  1. ABoth connectors require the engineer to provision and manage a dedicated all-purpose cluster, and the Salesforce connector must reload full snapshots each run because SaaS sources cannot expose incremental change columns.
  2. BManaged connectors only land raw files into a cloud storage volume, so the engineer must then run a separate Auto Loader stream to move that data from the volume into the governed Unity Catalog Delta tables downstream.
  3. CThe SQL Server connector supports both change tracking and change data capture, while the Salesforce SaaS connector runs only on serverless compute and incurs serverless Lakeflow pipeline DBU charges for its ingestion.
  4. DThe SQL Server connector supports change data capture only, and the Salesforce connector must run on classic job compute because serverless is limited to Python and SQL notebook cells rather than managed ingestion pipelines.
  5. EBoth connectors are configured purely in code with no UI or API path, and neither writes to Unity Catalog directly; results first land in the hive_metastore and must then be promoted into Unity Catalog by hand later.
Answer & explanation

Correct answer: C

WHY C: The SQL Server managed connector supports both change tracking and CDC, and SaaS connectors like Salesforce run exclusively on serverless, incurring serverless Lakeflow pipeline DBU charges. WHY NOT A: managed connectors are Databricks-operated and do not need a self-managed all-purpose cluster; Salesforce ingests incrementally via a cursor column, not full snapshots. WHY NOT B: managed connectors land data directly into Unity Catalog tables, not into a volume needing a separate Auto Loader step. WHY NOT D: the SQL Server connector supports change tracking as well as CDC, not CDC only. WHY NOT E: managed connectors are configured via UI/API and write directly to Unity Catalog, not through hive_metastore.

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 →