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?
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.