A 311 team must pull the prior day's closed tickets into bronze with managed batch ingest. Which approach fits?

A 311 team pulling the prior day’s closed tickets into bronze with managed batch ingest should use Lakeflow Connect in batch mode. Batch Connect fits closed-ticket extracts that arrive on a daily cadence into bronze without inventing a custom loader for each overnight pull. Managed batch ingest keeps the municipal closed-ticket landing repeatable, observable, and aligned with Unity Catalog destinations when configured for that path.

Using Auto Loader in batch mode to pull the prior day's closed tickets into bronze is the wrong pattern because Auto Loader ingests files from cloud object storage, not a managed pull from the ticketing database. Using Lakehouse Federation in batch mode to pull the prior day's closed tickets into bronze is incorrect because Federation provides federated reads of the external source rather than managed landing into bronze. Using Databricks SQL in batch mode to pull the prior day's closed tickets into bronze misses managed ingest because Databricks SQL queries data inside the lakehouse and does not pull from the external ticketing system.

Exam caveat: Lakeflow Connect supports batch and streaming modes—pick batch when the civic requirement is a prior-day extract, not Auto Loader in batch mode for file ingestion, and still validate bronze quality before silver promotion. Operational check: configure Lakeflow Connect in batch for the closed-ticket source, land yesterday’s closed tickets in bronze, validate counts against the 311 system’s closed-ticket report, monitor failed syncs, and ensure dashboards that need curated metrics read downstream silver or gold rather than attempting the pull with Databricks SQL in batch mode.