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 attempt to transfer "Owner" privileges to the "DevOps" group, but cannot successfully accomplish this task.
Which statement explains what is preventing this privilege transfer?
Databricks jobs must have exactly one owner; 'Owner' privileges cannot be assigned to a group. This ensures the job has a single point of accountability and control. While other permissions can be delegated using Access Control Lists (ACLs), the 'Owner' role itself cannot be transferred to a group.
Correct A job cannot have more than one owner. A job cannot have a group as an owner
did a test. "group cannot be owner" is displayed.
In Databricks, each job must have exactly one owner, which is typically the user who created the job. This “Owner” privilege allows the user to perform any action on the job, including modifying its settings or deleting it. However, this privilege cannot be assigned to a group. If you want to allow multiple users or a group of users to manage a job, you can use ACLs (Access Control Lists) to grant them the necessary permissions. But the “Owner” privilege will still remain with the individual user who created the job.