A Data Engineer is cloning a production database for use as a development environment using these commands: USE ROLE CLONE_ADMIN; CREATE DATABASE DB_DEV CLONE DE_PROD AT (OFFSET => -1800); What must t

Question

Options

• ARun this command on all pipes in the DB_DEV to resume loading from them:
• BRun this command on all external stages in the to point them to development files:
• CRun this command on all tables in the DB_DEV to revoke permissions from all production roles:
• DRun this command on all tables with sequences in the DB_DEV to reattach the sequences to the

• A
  82% (40)
• B
  2% (1)
• C
  12% (6)
• D
  4% (2)

Explanation

When Snowflake clones a database, Snowpipe pipes are automatically paused in the cloned environment - they do not inherit the running state from the source. To load data and make the development environment functional, the engineer must explicitly resume each pipe with ALTER PIPE ... RESUME, which is why A is correct.

B is wrong because external stages are cloned intact and still reference their original storage locations - no command is needed to make them functional (though you might redirect them later, it's not required to make the environment "ready to use"). C is wrong because cloning does not grant production roles access to the cloned objects by default; Snowflake's RBAC means permissions must be explicitly granted, so revoking them is not a required step. D is wrong because sequences are cloned as independent objects when a database or schema is cloned - they don't need to be reattached to tables.

Memory tip: Think "CLONE = PAUSE on Pipes." In Snowflake, any time you clone a database, treat pipes like a paused video - the data stream stopped mid-flight and won't restart until you hit resume.

No community discussion yet for this question.