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

- Free Preparation Discussions

Snowflake Exam ADA-C01 Topic 3 Question 23 Discussion

Actual exam question for Snowflake's ADA-C01 exam
Question #: 23
Topic #: 3
[All ADA-C01 Questions]

A team of developers created a new schema for a new project. The developers are assigned the role DEV_TEAM which was set up using the following statements:

USE ROLE SECURITYADMIN;

CREATE ROLE DEV TEAM;

GRANT USAGE, CREATE SCHEMA ON DATABASE DEV_DB01 TO ROLE DEV_TEAM;

GRANT USAGE ON WAREHOUSE DEV_WH TO ROLE DEV_TEAM;

Each team member's access is set up using the following statements:

USE ROLE SECURITYADMIN;

CREATE ROLE JDOE_PROFILE;

CREATE USER JDOE LOGIN NAME = 'JDOE' DEFAULT_ROLE='JDOE_PROFILE';

GRANT ROLE JDOE_PROFILE TO USER JDOE;

GRANT ROLE DEV_TEAM TO ROLE JDOE_PROFILE;

New tables created by any of the developers are not accessible by the team as a whole.

How can an Administrator address this problem?

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the Snowflake documentation1, future grants are a way to automatically grant privileges on future objects of a specific type that are created in a database or schema. By setting up future grants on the newly-created schemas, the administrator can ensure that any tables created by the developers in those schemas will be accessible by the DEV_TEAM role, without having to grant privileges on each table individually. Option A is incorrect because assigning ownership privilege to DEV_TEAM on the newly-created schema does not grant privileges on the tables in the schema, only on the schema itself. Option B is incorrect because assigning usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE does not affect the access to the tables in the schemas, only the ability to use the warehouse. Option D is incorrect because setting up the new schema as a managed-access schema does not grant privileges on the tables in the schema, but rather requires explicit grants for each table.


Contribute your Thoughts:

Glenn
2 months ago
This question is giving me a headache! I think I need to take a coffee break before tackling it. Maybe that'll help me see the obvious answer.
upvoted 0 times
Janet
22 days ago
Just remember to come back refreshed and ready to tackle the problem!
upvoted 0 times
...
Phyliss
1 months ago
I agree, sometimes stepping away for a bit can make the solution more obvious.
upvoted 0 times
...
Krystina
1 months ago
Don't worry, take your time. Maybe a break will help clear your mind.
upvoted 0 times
...
...
Cory
2 months ago
I'm a bit confused by this one. Wouldn't option B, assigning usage privilege on the virtual warehouse to the JDOE_PROFILE role, also be a valid solution?
upvoted 0 times
...
Arthur
2 months ago
I'm not sure. Maybe setting up the new schema as a managed-access schema could also solve the problem.
upvoted 0 times
...
Keva
2 months ago
Haha, this is a tricky one! I'm going to go with C. Setting up future grants on the newly-created schemas seems like a good way to handle this problem proactively.
upvoted 0 times
Dana
1 months ago
D) Set up the new schema as a managed-access schema.
upvoted 0 times
...
Shonda
1 months ago
C) Set up future grants on the newly-created schemas.
upvoted 0 times
...
Cheryll
1 months ago
C) Set up future grants on the newly-created schemas.
upvoted 0 times
...
Theresia
1 months ago
B) Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
upvoted 0 times
...
Ryan
2 months ago
B) Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
upvoted 0 times
...
Xochitl
2 months ago
A) Assign ownership privilege to DEV_TEAM on the newly-created schema.
upvoted 0 times
...
Peter
2 months ago
A) Assign ownership privilege to DEV_TEAM on the newly-created schema.
upvoted 0 times
...
...
Fletcher
2 months ago
I agree with Elfriede. That way, the team will have access to the new tables created by any of the developers.
upvoted 0 times
...
Elfriede
2 months ago
I think the Administrator should assign ownership privilege to DEV_TEAM on the newly-created schema.
upvoted 0 times
...
Marya
2 months ago
Hmm, I'm not sure. The question mentions that the new tables are not accessible by the team as a whole, so I'm leaning towards A. Assigning ownership privilege to DEV_TEAM seems like the most straightforward solution.
upvoted 0 times
...
Vivan
3 months ago
I think the answer is D. Setting up the new schema as a managed-access schema would ensure that all team members have the necessary privileges to access the tables.
upvoted 0 times
Noemi
1 months ago
C) Set up future grants on the newly-created schemas.
upvoted 0 times
...
Haydee
1 months ago
B) Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
upvoted 0 times
...
Sarina
2 months ago
A) Assign ownership privilege to DEV_TEAM on the newly-created schema.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77