Explanation:
Databricks audit logs provide a precise, per-request record of activity. Each REST API call is logged separately with the specific credentials (token or session) used to make that request.
jobs create event is recorded. This event is permanently tied to User A's identity.runNow API, the audit log generates execution events like runStart. These events include the runCreatorUserName field, which will identify User B as the caller.Audit logs are immutable; later actions by User B do not overwrite the historical record of User A creating the job. Furthermore, identities are recorded regardless of whether the request originates from the UI, CLI, or REST API.
Ultimate access to all questions.
No comments yet.
A data engineer (User A) promotes a new pipeline to production by creating a job in the workspace. Subsequently, a DevOps engineer (User B) configures an external orchestration tool to trigger runs for this job using the Databricks REST API. How will these actions be reflected in the workspace audit logs?
A
User B's identity will be linked to both the creation and execution of the jobs since they were the last to modify the configuration.
B
The use of the REST API for job management and execution results in the exclusion of user identities from the workspace audit logs.
C
User A's identity will be associated with the job creation events, while User B's identity will be linked to the job run events.
D
Both job creation and execution will be automatically attributed to a Service Principal because the REST API was utilized for the automation.
E
User A's identity will be tied to both the creation and the execution events in the audit logs since they are the original owner of the job.