Answer-first summary for fast verification
Answer: Databricks jobs must have exactly one owner, which must be an individual user or a service principal; groups cannot be assigned the "Owner" privilege.
### Explanation In Databricks, every job must have exactly one principal with the **IS OWNER** permission. According to Databricks Jobs Access Control List (ACL) rules, this principal **must** be an individual user or a service principal. ### Why the other options are incorrect: * **Job ownership is transferable:** Current owners or Workspace Administrators can transfer ownership to other users or service principals at any time. * **Admin restrictions:** Even Workspace Administrators cannot assign a group as a job owner because the platform architecture does not support groups holding the `IS OWNER` permission. * **Group membership is irrelevant:** The failure is not due to the user's permissions or group membership, but rather because the target entity (a group) is an invalid principal type for the Owner role.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A junior data engineer is attempting to transfer the "Owner" permissions of several Databricks jobs to the "DevOps" group via the Jobs UI. However, the system does not allow this transfer to proceed. Which of the following statements explains why this operation is failing?
A
The original creator of a Databricks job is permanently assigned the "Owner" privilege, and this cannot be modified or reassigned.
B
Granting "Owner" permissions to a group is a restricted action that can only be performed by Workspace Administrators.
C
A user is permitted to transfer job ownership to a group only if they are currently an active member of that specific group.
D
Databricks jobs must have exactly one owner, which must be an individual user or a service principal; groups cannot be assigned the "Owner" privilege.