Home / Data Engineer Associate / Objective 2.1

Domain 2: Data Ingestion and Loading · 21% of the exam · Full exam outline

2.1 Enable and detail data ingestion patterns, including batch, streaming, and incremental loading, and import data from sources such as local files, Lakeflow Connect standard connectors, and Lakeflow Connect managed connectors.

Practice questions

Question 1easy

A team must land Salesforce objects in Unity Catalog tables and is deciding which ingestion layer to start from. What does Databricks guidance recommend?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Databricks recommends starting with the most managed layer and dropping down only if it does not meet requirements, for example when the source is unsupported. Salesforce has a fully-managed connector, so that is the starting point.

It is true that SQL and Spark APIs in Lakeflow pipelines give more customization, which is why this is tempting. But customization is the reason to drop down a layer, not where to start, and nothing here says the managed connector falls short.

DIY connectors are possible on Databricks, but the premise is wrong: fully-managed connectors include automated schema evolution along with authentication, CDC and retries.

Federation avoids copying data, but SaaS data can be ingested into tables; Lakeflow Connect has SaaS connectors for Salesforce specifically.

Question 2easy

A finance analyst has a small CSV export saved on her laptop and needs it as a table in Databricks today. No recurring pipeline is wanted. Which ingestion option fits?

Included in Master: master every domain.See plans