A data engineer, User A, has promoted a new pipeline to production by using the REST API to programmatically create several jobs. A DevOps engineer, User B, has configured an external orchestration to

Question

Options

• ABecause the REST API was used for job creation and triggering runs, a Service Principal will be
• BBecause User B last configured the jobs, their identity will be associated with both the job creation
• CBecause these events are managed separately, User A will have their identity associated with the
• DBecause the REST API was used for job creation and triggering runs, user identity will not be
• EBecause User A created the jobs, their identity will be associated with both the job creation

• B
  4% (2)
• C
  93% (43)
• E
  2% (1)

Explanation

Databricks workspace audit logs record the identity of the authenticated caller for every API action. Since User A used their own personal access token to create the jobs, audit logs will associate User A's identity with the job creation events. Since User B used their own personal access token to trigger the job runs, audit logs will associate User B's identity with the run trigger events. Each event is independently attributed to whoever made that specific API call. Using the REST API does not anonymize identity or attribute actions to a Service Principal (ruling out A and D), and the last person to interact with a job does not retroactively own all events for it (ruling out B and E).

No community discussion yet for this question.