CERTIFIED-DATA-ENGINEER-PROFESSIONAL · Question #41
The DevOps team has configured a production workload as a collection of notebooks scheduled to run daily using the Jobs UI. A new data engineering hire is onboarding to the team and has requested acce
The correct answer is D. Can Read. In Databricks, notebook permissions follow a hierarchy: No Permissions < Can Read < Can Run < Can Edit < Can Manage. 'Can Read' allows a user to view the notebook content - they can read all code and logic - but cannot execute cells or modify anything. 'Can Run' would allow the u
Question
The DevOps team has configured a production workload as a collection of notebooks scheduled to run daily using the Jobs UI. 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
- CNo permissions
- DCan Read
- ECan Run
How the community answered
(29 responses)- B3% (1)
- D93% (27)
- E3% (1)
Explanation
In Databricks, notebook permissions follow a hierarchy: No Permissions < Can Read < Can Run < Can Edit < Can Manage. 'Can Read' allows a user to view the notebook content - they can read all code and logic - but cannot execute cells or modify anything. 'Can Run' would allow the user to execute cells, which could trigger writes to production data sources and cause accidental data changes. 'Can Edit' and 'Can Manage' both allow code modifications. Since the goal is read-only access to review logic without any risk of accidental execution or modification, 'Can Read' (option D) is the correct maximum permission.
Topics
Community Discussion
No community discussion yet for this question.