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

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?
A . Sequences, views, and secure views
B . Sequences, views, secure views, and materialized views
C . Sequences, storage integrations, views, secure views, and materialized views
D . There are no object references that need to be re-pointed

View Answer

Answer: C

Explanation:

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]