
Answer-first summary for fast verification
Answer: User B’s email address will always appear in this field, as their credentials are always used to trigger the run.
The `creator_user_name` field in the Databricks Jobs run information reflects the identity of the user whose credentials were used to trigger the job run. In this scenario, User B's external orchestration tool uses their personal access token to trigger job runs via the REST API. Even after User C takes ownership of the jobs, the runs are still initiated using User B's credentials, so User B's email address will always appear in the `creator_user_name` field. Ownership changes (via User C) affect job configuration management but do not alter the run-triggering identity, which is determined by the API credentials used.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A data engineer (User A) deployed a pipeline to production by programmatically creating multiple jobs via the REST API. A DevOps engineer (User B) set up an external orchestration tool to initiate job runs through the REST API, with both users authenticating using their personal access tokens.
Later, a workspace admin (User C) assumes responsibility for managing this pipeline and uses the Databricks Jobs UI to take ownership of each job. The jobs continue to be executed using User B's credentials and orchestration tool.
An application collects and processes run information returned by the REST API. What value appears in the creator_user_name field?
A
Once User C takes "Owner" privileges, their email address will appear in this field; prior to this, User A’s email address will appear in this field.
B
User B’s email address will always appear in this field, as their credentials are always used to trigger the run.
C
User A’s email address will always appear in this field, as they still own the underlying notebooks.
D
Once User C takes "Owner" privileges, their email address will appear in this field; prior to this, User B’s email address will appear in this field.
E
User C will only ever appear in this field if they manually trigger the job, otherwise it will indicate User B.