The DevOps team has configured a production workload as a collection of notebooks scheduled to run daily using the Jobs Ul. A new data engineering hire is onboarding to the team and has requested…

The correct answer is D. Can Read. Databricks notebook permissions follow a hierarchy: Can Manage > Can Edit > Can Run > Can Read. To allow a new hire to review production logic without any risk of modifying code or accidentally triggering execution that could alter production data, 'Can Read' is the correct…

Data Governance and Security

Question

The DevOps team has configured a production workload as a collection of notebooks scheduled to run daily using the Jobs Ul. A new data engineering hire is onboarding to the team and has requested access to one of these notebooks to review the production logic. What are the maximum notebook permissions that can be granted to the user without allowing accidental changes to production code or data?

Options

ACan manage
BCan edit
CCan run
DCan Read

How the community answered

(31 responses)

A
6% (2)
B
3% (1)
D
90% (28)

Explanation

Databricks notebook permissions follow a hierarchy: Can Manage > Can Edit > Can Run > Can Read. To allow a new hire to review production logic without any risk of modifying code or accidentally triggering execution that could alter production data, 'Can Read' is the correct permission level. It grants view-only access to the notebook content. 'Can Run' (option C) would allow the user to execute the notebook, potentially modifying production data. 'Can Edit' (option B) allows code changes. 'Can Manage' (option A) grants full administrative control. Only 'Can Read' satisfies the maximum-access-without-risk requirement.

Topics

#Databricks Permissions#Notebook Access Control#Security Best Practices#Production Workloads

Community Discussion

No community discussion yet for this question.

Full CERTIFIED-DATA-ENGINEER-PROFESSIONAL Practice