A team wants an application to trigger administrative operations, such as creating a catalog association, as part of an automated deployment. What is the appropriate mechanism?
Select an answer to reveal the explanation.
Short Explanation
Administrative work has APIs too, so you can use the documented management APIs with a service identity that has the right permissions. Don't drive the console UI or edit catalog metadata files directly, because the platform expects to own that state.
Full Explanation
The appropriate mechanism is the platform's documented management APIs, called with a service identity holding the required administrative permissions. The platform exposes management APIs for administrative operations, which is what lets deployment automation configure resources reproducibly. The calling service identity needs the appropriate administrative permissions, scoped to what the deployment actually performs.
Scripting the console UI is incorrect because administrative operations are not console-exclusive, and scripting a UI is fragile and unsupported.
Direct modification of catalog metadata files in object storage is incorrect and is actively dangerous. Catalog metadata is managed state with its own consistency rules; editing it underneath the platform risks corrupting tables.
Support requests are incorrect because automation of platform administration is a normal expectation, not something requiring vendor intervention.
For the exam, distinguish data-plane access - drivers and query APIs - from control-plane access through management APIs, both authenticated as identities with scoped rights.