A junior data engineer has manually configured a series of jobs using the Databricks Jobs UI. Upon reviewing their work, the engineer realizes that they are listed as the "Owner" for each job. They…

Question

Options

• ADatabricks jobs must have exactly one owner; "Owner" privileges cannot be assigned to a group.
• BThe creator of a Databricks job will always have "Owner" privileges; this configuration cannot be
• COther than the default "admins" group, only individual users can be granted privileges on jobs.
• DA user can only transfer job ownership to a group if they are also a member of that group.
• EOnly workspace administrators can grant "Owner" privileges to a group.

• A
  92% (46)
• B
  4% (2)
• D
  2% (1)
• E
  2% (1)

Explanation

In Databricks, job ownership is restricted to individual user accounts only - it cannot be assigned to a group, a service principal acting as a group, or any other non-user entity. This is a fundamental platform-level constraint in the Databricks Jobs ownership model. Because groups are not valid ownership targets, the engineer's attempt to transfer ownership to the 'DevOps' group fails regardless of their own permissions or admin status. Option B is wrong because ownership CAN be transferred (just not to a group). Option C is partially misleading - the limitation is specifically about ownership, not all privileges. Option D is fabricated; no such group-membership prerequisite exists. Option E is incorrect because admin status does not unlock group ownership since the feature simply does not exist.

No community discussion yet for this question.