SnowflakeAssociate levelCOF-C03Page 2 of 4

COF-C03 exam dumps: questions 101 to 200 of 350

Page 2 of the free COF-C03 question bank for the SnowPro® Core Certification (COF-C03) exam. Questions 101 to 200 are listed below, the first 5 in full with answers and explanations. Back to page 1 for the exam overview and FAQ.

Question bank last updated April 2026

Start timed practice exam Questions 101 to 200

Free COF-C03 practice questions

Questions 101 to 105 of 350

Pick an answer before you open the explanation. Each question also has its own page with a permalink.

COF-C03 Question 101

Single answerTemporary

A data engineering team runs a daily ETL process in Snowflake. During each run, the process creates several staging tables that are only needed for the duration of the user session and must not remain after the session ends. The team also wants to avoid the risk of these tables being recovered later through Time Travel. Which table type should the engineer use for these staging tables?

A
Permanent tables, because they support full recovery and can be automatically dropped at session end
B
Transient tables, because they do not have Fail-safe and are removed automatically when the session ends
C
Temporary tables, because they exist only within the session and are purged when the session ends
D
External tables, because they reference staged data without storing it in Snowflake

Show answer and explanation

Correct answer: C

Explanation

Temporary tables are designed for short-lived, session-specific workloads such as ETL staging, scratch work, and intermediate transformations. They are only visible within the creating session and are automatically dropped when that session ends. This makes them the best choice when data should not persist beyond the session. By contrast, transient tables are persistent until dropped, although they do not have Fail-safe; they are better for non-permanent data that still must survive across sessions. Permanent tables are intended for durable storage with full data protection features. Snowflake documentation distinguishes these table types based on persistence, recovery, and lifecycle behavior, and temporary tables are the recommended option for session-only staging use cases.

A. Incorrect.
Incorrect. Permanent tables are the default table type and persist until explicitly dropped. They support Time Travel and Fail-safe, so they are not appropriate when the requirement is for the table to disappear automatically at the end of the session and not be recoverable later.
B. Incorrect.
Incorrect. Transient tables do not have Fail-safe, which can make them useful for lower-cost, non-permanent data storage. However, they persist until explicitly dropped and are not automatically removed at the end of a session. They can still have Time Travel retention, so they do not meet the stated requirement as well as temporary tables.
C. Correct.
Correct. Temporary tables are session-scoped objects in Snowflake. They are only available to the session that created them and are automatically dropped at the end of that session. Because they are session-based and purged when the session ends, they are the right fit for ETL staging tables needed only during a single run.
D. Incorrect.
Incorrect. External tables are used to query data stored outside Snowflake, such as in cloud storage. They are not designed to provide session-scoped temporary relational storage for ETL intermediates.

COF-C03 Question 102

Single answerTransient

A data engineering team loads high-volume clickstream data into Snowflake and keeps it for only 5 days before it is re-created from source systems. The team wants to reduce storage costs associated with historical data retention, but they still need a short recovery window for accidental deletes or updates. Which Snowflake object type best fits this requirement?

A
Create a permanent table and set DATA_RETENTION_TIME_IN_DAYS = 90
B
Create a transient table with an appropriate Time Travel retention period
C
Create a temporary table because it supports fail-safe-free recovery across sessions
D
Create an external table because external tables provide the same recovery behavior as transient tables

Show answer and explanation

Correct answer: B

Explanation

The best choice is a transient table. In Snowflake, transient tables are intended for data that needs to persist beyond a session but does not require the extra data protection of Fail-safe. Because Fail-safe storage is not available for transient tables, they are commonly used for staging, transient operational data, and other re-creatable datasets where cost optimization matters. Unlike temporary tables, transient tables persist until explicitly dropped and can be shared across sessions and users. They still support Time Travel for a configurable short retention window, which satisfies the requirement to recover from accidental DML changes. This aligns with Snowflake guidance that permanent objects are best for business-critical data requiring Fail-safe, while transient objects are suitable when reduced data protection is acceptable in exchange for lower storage cost.

A. Incorrect.
Incorrect. A permanent table includes Fail-safe storage costs and is intended for data that requires stronger long-term recovery protection. Setting a long retention period such as 90 days increases historical storage rather than reducing it, which conflicts with the team's cost-saving goal for short-lived data.
B. Correct.
Correct. Transient tables are designed for data that does not require Fail-safe protection, which can reduce storage costs for short-lived or re-creatable data. They still support Time Travel, with a limited retention period, allowing recovery from accidental deletes or updates for a short window. This matches the stated need for lower cost plus short-term recoverability.
C. Incorrect.
Incorrect. Temporary tables are session-scoped and are dropped automatically at the end of the session. They are useful for intermediate or scratch data, not for shared operational datasets that must remain available for multiple sessions or users over several days. Also, describing them as providing recovery across sessions is incorrect.
D. Incorrect.
Incorrect. External tables reference data stored outside Snowflake and are used to query external files. They do not provide the same managed storage, Time Travel, and transient-table behavior for internal Snowflake table data. Choosing an external table would not address the requirement for a Snowflake-managed short recovery window on loaded clickstream data.

COF-C03 Question 103

Single answerTransient

A data engineering team loads large daily staging datasets into Snowflake and keeps them for 5 days before deleting them. The team wants to reduce storage costs associated with historical data retention, but they still need protection from accidental drops and the ability to recover the data for a short period if a mistake occurs. Which table type best meets these requirements?

A
A permanent table, because it supports Fail-safe and the longest retention options
B
A temporary table, because it avoids all historical storage costs and can be recovered after the session ends
C
A transient table, because it supports Time Travel but does not incur Fail-safe storage costs
D
An external table, because data recovery is handled automatically outside Snowflake

Show answer and explanation

Correct answer: C

Explanation

The best answer is a transient table. In Snowflake, transient tables are intended for non-permanent data that must survive beyond a session but does not need Fail-safe protection. This makes them well suited for staging, intermediate transformation outputs, and short-lived operational datasets. Compared to permanent tables, transient tables can reduce storage costs because they do not incur Fail-safe storage. Unlike temporary tables, they persist until explicitly dropped and are accessible across sessions. Snowflake documentation and best practices describe transient objects as appropriate when Time Travel is useful but the additional data protection and cost of Fail-safe are not required.

A. Incorrect.
Incorrect. Permanent tables do provide Time Travel and Fail-safe protection, but the scenario specifically emphasizes reducing storage costs related to historical retention. Permanent tables incur Fail-safe storage costs after the Time Travel period, so they are not the best fit when short-term recoverability is needed without the extra Fail-safe cost.
B. Incorrect.
Incorrect. Temporary tables exist only for the duration of the session and are not suitable for data that must remain available for 5 days across sessions. In addition, once the session ends, the table is purged and is not intended for recovery in the way described.
C. Correct.
Correct. Transient tables are designed for data that needs to persist beyond a single session but does not require the same level of data protection as permanent tables. They support Time Travel for a limited retention period, which helps protect against accidental changes or drops, but they do not have a Fail-safe period. This makes them a common choice for staging or intermediate data when cost reduction is important.
D. Incorrect.
Incorrect. External tables reference data stored outside Snowflake, typically in cloud object storage. They do not provide Snowflake-managed data recovery for internal table data and are not the right choice for this staging-table use case.

COF-C03 Question 104

Single answerApache Iceberg™

A data engineering team stores Apache Iceberg™ tables in external cloud storage and wants analysts to query those tables from Snowflake without copying the data into native Snowflake tables. The team also wants Snowflake to stay aware of metadata changes made to the Iceberg table by another engine. Which approach best meets these requirements?

A
Create an external table on the Iceberg data files and use AUTO_REFRESH so Snowflake can interpret Iceberg snapshots automatically.
B
Create a Snowflake-managed Iceberg table so Snowflake stores the metadata and automatically tracks any commits made by external engines.
C
Create an externally managed Iceberg table in Snowflake and configure catalog integration so Snowflake can use the external Iceberg catalog metadata.
D
Load the Iceberg data into a permanent Snowflake table using COPY INTO, then create a stream to detect future Iceberg metadata changes.

Show answer and explanation

Correct answer: C

Explanation

The best answer is to create an externally managed Iceberg table and use catalog integration. Snowflake supports Iceberg tables so customers can work with Apache Iceberg data in object storage while relying on Iceberg metadata for table state. When another engine updates the Iceberg table, Snowflake must reference the external catalog metadata to see the latest snapshots and schema state. This is different from external tables, which operate on files rather than full Iceberg table semantics, and different from Snowflake-managed Iceberg tables, where Snowflake controls the catalog metadata. This aligns with Snowflake guidance on choosing between Snowflake-managed and externally managed Iceberg tables based on where the catalog and metadata are managed.

A. Incorrect.
Incorrect. External tables in Snowflake are designed to query files in cloud storage, but they do not provide native Apache Iceberg table semantics by automatically interpreting Iceberg metadata, snapshots, and table state the way Iceberg tables do. AUTO_REFRESH helps detect file changes for supported scenarios, but it does not make an external table behave like a native Iceberg table backed by an Iceberg catalog.
B. Incorrect.
Incorrect. A Snowflake-managed Iceberg table uses Snowflake as the catalog and manages the table metadata on behalf of the user. This is useful when Snowflake is the primary manager of the Iceberg table, but it does not match the requirement that another engine can make metadata changes that Snowflake must detect through an external catalog. The scenario specifically calls for externally managed metadata.
C. Correct.
Correct. An externally managed Iceberg table lets Snowflake query Iceberg data stored externally without ingesting it into native Snowflake storage. By using a catalog integration, Snowflake can access the external Iceberg catalog and stay aligned with metadata changes committed by other engines. This is the appropriate design when the table lifecycle and metadata are managed outside Snowflake.
D. Incorrect.
Incorrect. COPY INTO would physically load data into a native Snowflake table, which violates the requirement to avoid copying the data into Snowflake-managed storage. In addition, a stream on a Snowflake table tracks DML changes to that Snowflake table, not Iceberg metadata commits occurring in an external catalog.

COF-C03 Question 105

Single answerApache Iceberg™

A data engineering team stores product catalog data as Apache Iceberg™ tables in external cloud storage. Analysts want to query this data in Snowflake without copying it into native Snowflake tables, and the engineering team wants Snowflake to use Iceberg table metadata to keep the table definition current. Which approach should the team use?

A
Create an external table in Snowflake over the Parquet files and let Snowflake infer Iceberg snapshots automatically.
B
Create a Snowflake-managed Iceberg table so Snowflake stores the data files in internal stages and manages metadata in external cloud storage.
C
Create an externally managed Iceberg table in Snowflake and integrate it with a catalog that tracks the Iceberg metadata.
D
Load the Iceberg data into a transient table and enable automatic synchronization with the Iceberg manifest files.

Show answer and explanation

Correct answer: C

Explanation

The best answer is to create an externally managed Iceberg table in Snowflake and connect it to the appropriate catalog metadata. This matches the scenario where data already exists as Apache Iceberg tables in external object storage and the organization wants Snowflake to query that data without ingesting it into standard Snowflake tables. In Snowflake, Iceberg support distinguishes between Snowflake-managed and externally managed Iceberg tables. Externally managed Iceberg tables are appropriate when another system or catalog is the source of truth for the Iceberg metadata. By contrast, external tables over raw files do not provide Iceberg-native table semantics, and loading into transient or permanent native tables would require copying data. This aligns with Snowflake guidance that Iceberg tables use Iceberg metadata and catalogs rather than simple file inference.

A. Incorrect.
Incorrect. External tables in Snowflake can query data in external stages, but they do not use Apache Iceberg table metadata as the governing table metadata layer. Iceberg tables rely on snapshots, manifests, and metadata files managed through an Iceberg catalog. Treating the data as a generic external table would miss the requirement to keep the table definition aligned through Iceberg metadata management.
B. Incorrect.
Incorrect. A Snowflake-managed Iceberg table is managed by Snowflake, but this option contradicts the scenario in two ways: the team already stores the data as Iceberg tables in external cloud storage, and they want Snowflake to use the existing Iceberg metadata rather than move to a Snowflake-managed arrangement. Snowflake-managed Iceberg tables are not the best fit when the source-of-truth metadata is already maintained externally.
C. Correct.
Correct. Externally managed Iceberg tables are designed for this scenario: the data remains in external cloud storage, and Snowflake reads table state using Iceberg metadata maintained outside Snowflake through a supported catalog or catalog integration. This allows analysts to query the data in Snowflake without copying it into native Snowflake storage while preserving the existing Iceberg table management pattern.
D. Incorrect.
Incorrect. Loading data into a transient table copies the data into Snowflake-managed storage, which violates the requirement to avoid copying it into native Snowflake tables. In addition, transient tables do not automatically synchronize with Iceberg manifest or snapshot metadata.

Timed practice exam

Take a COF-C03 practice test under exam conditions

100 questions in 115 minutes, drawn from this bank, with a score report and a per-question review when you finish.

Start timed exam

COF-C03 practice questions 101 to 200 of 350

Every question has a page with the answer and explanation. Numbers are stable, so you can bookmark or share them. The bank is split into 4 pages of up to 100 questions.