An application team needs their service to read governed lakehouse tables as part of a nightly process. What is the appropriate integration approach?
Select an answer to reveal the explanation.
Short Explanation
You give the application a supported client and its own service identity. Anything else—scripting the UI, borrowing a human's session, going straight to the bucket—breaks when something changes and skips governance in the meantime.
Full Explanation
Programmatic access is served by supported drivers and interfaces against an engine. That path is stable across releases, and a service principal with scoped permissions means the access is auditable and limited to what the job requires. Automating the web console with a headless browser and reading the rendered results is incorrect because the web console is a human interface with no compatibility contract. Layout changes break the integration silently, and the approach carries no proper authentication model. Giving the service an administrator's session cookie so it can reuse the console session is incorrect and is a serious security failure. Sharing a session cookie means the service acts as that administrator, with their full rights and no distinguishable audit trail. Having the service read the underlying objects from the bucket directly using storage keys is incorrect because reading objects directly bypasses the governance layer entirely, and the service would see raw files rather than governed tables. For the exam, treat scraping the UI and sharing credentials as automatically wrong; the supported client is the answer.