Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 4 of 119
Free Preview · 119 of 395 · questions 1–119 of 395 are free. Sign up free to sync your progress across devices.
Select all answers that apply.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
,B - Correct answer s : A, B — `GRANT USAGE, CREATE ON SCHEMA main.analytics` plus `GRANT USAGE ON CATALOG main` to the analyst, enabling new function registration.; `GRANT EXECUTE ON FUNCTION main.analytics.existing_func` to the analyst, enabling the analyst to call the function someone else owns. A . Registering a new function requires `USAGE` and `CREATE` on the target schema together with `USAGE` on the containing catalog; without both, the registration attempt fails with a permission error. B . Calling a function owned by another principal requires an explicit `EXECUTE` grant on that function; ownership of the schema or catalog alone does not confer the right to run someone else's function. C . `MODIFY` is not the privilege that governs invoking a function; running a function is controlled by the `EXECUTE` privilege, and `MODIFY`-style grants do not substitute for it. D . Granting metastore-wide `ALL PRIVILEGES` is a far broader change than needed for either failure and is not the targeted grant Unity Catalog uses to resolve schema-level or function-level permission errors. E . Transferring ownership of the whole schema is unnecessary and overly broad just to let one analyst create functions there, and it still would not resolve the separate failure to call another owner's existing function. F . `SELECT` is a table- and view-level privilege; it has no effect on the ability to invoke a function, so granting it on the schema would not resolve either reported failure.