New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake ADA-C01 Exam - Topic 1 Question 44 Discussion

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

A team is provisioning new lower environments from the production database using cloning. All production objects and references reside in the database, and do not have

external references.

What set of object references needs to be re-pointed before granting access for usage?

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the Snowflake documentation1, when an object in a schema is cloned, any future grants defined for this object type in the schema are applied to the cloned object unless the COPY GRANTS option is specified in the CREATE statement for the clone operation. However, some objects may still reference the source object or external objects after cloning, which may cause issues with access or functionality. These objects include:

* Sequences: If a table column references a sequence that generates default values, the cloned table may reference the source or cloned sequence, depending on where the sequence is defined. To avoid conflicts, the sequence reference should be re-pointed to the desired sequence using the ALTER TABLE command2.

* Storage integrations: If a stage or a table references a storage integration, the cloned object may still reference the source storage integration, which may not be accessible or valid in the new environment. To avoid errors, the storage integration reference should be re-pointed to the desired storage integration using the ALTER STAGE or ALTER TABLE command34.

* Views, secure views, and materialized views: If a view references another view or table, the cloned view may still reference the source object, which may not be accessible or valid in the new environment. To avoid errors, the view reference should be re-pointed to the desired object using the CREATE OR REPLACE VIEW command5.

1: Cloning Considerations | Snowflake Documentation 2: [ALTER TABLE | Snowflake Documentation] 3: [ALTER STAGE | Snowflake Documentation] 4: [ALTER TABLE | Snowflake Documentation] 5: [CREATE VIEW | Snowflake Documentation]


Contribute your Thoughts:

0/2000 characters
Jeannetta
1 day ago
Wait, are you sure there are no external references at all? Sounds risky!
upvoted 0 times
...
Emeline
7 days ago
A seems too limited, you can't ignore materialized views.
upvoted 0 times
...
Dorthy
12 days ago
I think D is a bit too optimistic, there are always references to check.
upvoted 0 times
...
Latanya
17 days ago
I'm going with B. Gotta make sure all those internal database objects are properly set up in the new environment.
upvoted 0 times
...
Avery
22 days ago
Haha, option D is like saying "just use the production database as-is, what could go wrong?"
upvoted 0 times
...
Starr
27 days ago
D is definitely wrong. There's no way you can just grant access without re-pointing the object references.
upvoted 0 times
...
Alecia
1 month ago
I agree with B. Cloning the production database would require updating all the internal references.
upvoted 0 times
...
Gianna
1 month ago
I’m leaning towards option B because it seems like all the relevant objects would need to be checked, but I’m not completely confident.
upvoted 0 times
...
Charlette
1 month ago
I think we practiced a similar question where we had to identify which objects needed re-pointing, and I feel like materialized views were included in that one.
upvoted 0 times
...
Kirk
2 months ago
I remember we discussed how sequences and views can have dependencies that might need to be updated, but I'm not sure about secure views.
upvoted 0 times
...
Felix
2 months ago
This is a tricky one. The wording about "external references" is throwing me off a bit. I think I'll eliminate option D first, since the question specifically asks what needs to be re-pointed. Then I'll compare the remaining options to see which one best fits the description.
upvoted 0 times
...
Jonell
2 months ago
I'm leaning towards option B. Sequences, views, secure views, and materialized views all seem like they could have internal references that would need to be re-pointed when creating the new environments. Better safe than sorry!
upvoted 0 times
...
Barrett
2 months ago
Option D seems like the most straightforward answer, but I want to double-check that there really aren't any internal references that need to be updated when cloning the database. I'll review the details carefully.
upvoted 0 times
...
Franklyn
2 months ago
Definitely B, you need to cover all bases with materialized views.
upvoted 0 times
...
Carmela
2 months ago
Option B seems correct. Sequences, views, secure views, and materialized views would need to be re-pointed before granting access.
upvoted 0 times
...
Tandra
3 months ago
I recall that sometimes there are no references that need to be changed, but that seems unlikely here with all the production objects involved.
upvoted 0 times
...
Olen
3 months ago
C covers everything. Storage integrations matter too.
upvoted 0 times
...
Laurene
3 months ago
Hmm, I'm a bit confused. The question says "all production objects and references reside in the database, and do not have external references." Does that mean there are no object references that need to be re-pointed?
upvoted 0 times
...
Zona
3 months ago
I think the key here is to identify all the objects that have references to other objects in the database. The question mentions sequences, views, and secure views, so I'll focus on those.
upvoted 0 times
...

Save Cancel