Answer-first summary for fast verification
Answer: Databricks jobs must have exactly one owner; "Owner" privileges cannot be assigned to a group.
In Databricks, each job must have exactly one individual user as the owner. Ownership privileges cannot be assigned to a group, even if the user has administrative permissions. While job ownership can be transferred to another user, the system does not allow groups to be designated as owners. This explains why the junior engineer cannot assign the 'DevOps' group as the owner. Options B, C, and D are incorrect because ownership can be transferred to other users (not groups), workspace admins are not required for this specific action, and group membership does not affect the inability to assign group ownership.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A junior data engineer manually configured multiple jobs in the Databricks Jobs UI and discovered they are listed as the "Owner" for each job. When attempting to transfer "Owner" privileges to the "DevOps" group, the operation fails.
What is preventing the successful transfer of ownership privileges?
A
Databricks jobs must have exactly one owner; "Owner" privileges cannot be assigned to a group.
B
The creator of a Databricks job will always have "Owner" privileges; this configuration cannot be changed.
C
Only workspace administrators can grant "Owner" privileges to a group.
D
A user can only transfer job ownership to a group if they are also a member of that group.
No comments yet.