BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Databricks Exam Databricks-Certified-Professional-Data-Engineer Topic 6 Question 11 Discussion

Actual exam question for Databricks's Databricks-Certified-Professional-Data-Engineer exam
Question #: 11
Topic #: 6
[All Databricks-Certified-Professional-Data-Engineer Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Granting a user 'Can Read' permissions on a notebook within Databricks allows them to view the notebook's content without the ability to execute or edit it. This level of permission ensures that the new team member can review the production logic for learning or auditing purposes without the risk of altering the notebook's code or affecting production data and workflows. This approach aligns with best practices for maintaining security and integrity in production environments, where strict access controls are essential to prevent unintended modifications. Reference: Databricks documentation on access control and permissions for notebooks within the workspace (https://docs.databricks.com/security/access-control/workspace-acl.html).


Contribute your Thoughts:

Titus
5 months ago
Option D - Can Read. Safety first, you know? We don't want this new guy accidentally launching the nuclear missiles or something. Baby steps, people!
upvoted 0 times
...
Corinne
5 months ago
Haha, I've got an idea - let's give him all the permissions and see what happens! Might make for a fun learning experience. Or a complete disaster. Either way, it'll be entertaining!
upvoted 0 times
Jerry
4 months ago
Maybe we can start with 'Can Read' permission first.
upvoted 0 times
...
Bette
4 months ago
Yeah, we should be cautious with production code.
upvoted 0 times
...
Rene
5 months ago
I think giving all permissions might be risky.
upvoted 0 times
...
...
Geoffrey
5 months ago
C - No permissions. Who does this new guy think he is, the CEO? Let him earn his stripes first before we let him loose on the production environment.
upvoted 0 times
...
Iesha
5 months ago
Definitely D - Can Read. We can't just give them the keys to the kingdom on their first day! Slow and steady wins the race.
upvoted 0 times
...
Ivette
5 months ago
I'd go with E - Can Run. That way they can execute the notebook but not make any changes. Gotta let the new kid play with the toys, but not break them, you know?
upvoted 0 times
Keith
4 months ago
Definitely, it's important to give access but also maintain control over the production environment.
upvoted 0 times
...
Giovanna
4 months ago
Agreed, it allows them to execute the notebook without risking any changes to production code.
upvoted 0 times
...
Katy
4 months ago
I think E - Can Run is the best option for the new hire.
upvoted 0 times
...
...
Lyla
5 months ago
Option D - Can Read is the way to go. We don't want this new hire messing with the production code, but they need to understand the logic. Safety first!
upvoted 0 times
Adelle
4 months ago
Agreed, we need to prioritize safety when granting access to production workloads.
upvoted 0 times
...
Keena
4 months ago
Option D - Can Read is the best choice. It allows access without the risk of accidental changes.
upvoted 0 times
...
Jennifer
5 months ago
Agreed, that way they can review the logic without risking any accidental changes.
upvoted 0 times
...
Roslyn
5 months ago
I think we should give them Can Read permissions.
upvoted 0 times
...
...

Save Cancel