Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
A new data engineering team has been assigned to work on a project. The team will need access to database customers in order to see what tables already exist. The team has its own group team. Which command can be used to grant the necessary permission on the entire database to the new team?
Real Exam
Community
KKeng
A
GRANT VIEW ON CATALOG customers TO team;
B
GRANT CREATE ON DATABASE customers TO team;
C
GRANT USAGE ON CATALOG team TO customers;
D
GRANT USAGE ON DATABASE customers TO team;
Explanation:
Explanation
Correct Answer: D
Why Option D is correct:
- The
USAGEprivilege on a database allows users/groups to see the database and its contents (tables, views, etc.) - The syntax
GRANT USAGE ON DATABASE customers TO team;grants the team group permission to access and view the database structure - This matches the requirement: "access to database customers in order to see what tables already exist"
Why other options are incorrect:
Option A: GRANT VIEW ON CATALOG customers TO team;
VIEWis not a valid privilege for catalogs in Databricks Unity Catalogcustomersis a database, not a catalog- The syntax is incorrect for the requirement
Option B: GRANT CREATE ON DATABASE customers TO team;
CREATEprivilege allows creating objects (tables, views) within the database- This goes beyond the requirement of just viewing existing tables
- The team only needs to see what tables exist, not create new ones
Option C: GRANT USAGE ON CATALOG team TO customers;
- This reverses the grant direction (granting to customers instead of team)
teamis a group, not a catalog- The syntax is completely backwards
Key Concepts:
- In Databricks Unity Catalog,
USAGEprivilege on a database allows:- Viewing the database
- Listing tables/views in the database
- Describing the database
- The privilege hierarchy in Unity Catalog is: Catalog → Schema (Database) → Table/View
GRANT USAGE ON DATABASE <database_name> TO <group_name>;is the correct syntax for granting database access
Comments
Loading comments...