Snowflake SnowPro Core COF-C03 Practice Test 9 - Prepaway
Practice Exams:

Pass Snowflake SnowPro Core COF-C03 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$14.99
$74.99 $89.98

SnowPro Core COF-C03 Premium Bundle


  • Premium File 116 Questions & Answers. Last update: Nov 17, 2026
  • Study Guide 222 Pages

Snowflake SnowPro Core COF-C03 Practice Test 9

Question 80

A Snowflake analyst supporting case document metadata and restricted reporting at a legal services organization intends: Correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics. The reported condition is: A sales dashboard duplicates order totals after adding an event table with several events per order. Identify the most decisive diagnostic record.

  1. Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent.
  2. Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly.
  3. Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads.
  4. Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers.

Correct Answer: D

Explanation

A.

Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.

B.

Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.

C.

Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.

D.

Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Join cardinality affects both query cost and semantic result correctness. To address this, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics. Confirm that a seeded order contributes its intended total once and query row expansion returns to expected levels.

Question 81

The Snowflake data engineering team at a pension administrator investigating member analytics and long-term audit records notes: A compliance team discovers unusual data access after its short-lived dashboard has rolled off the required audit interval. Evidence: A dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. They plan: Configure supported account usage reporting, collection and retention suitable for the approved audit period. Which technical principle justifies the correction?

  1. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering.
  2. Operational dashboards and governed audit history have different retention and access requirements.
  3. Warehouse credit costs can accrue during idle running time separately from actual query work.
  4. Cost governance thresholds must account for workload criticality and the different effects of monitor actions.

Correct Answer: B

Explanation

A.

Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. This choice does not explain the observed failure mechanism. For member analytics and long-term audit records at a pension administrator, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

B.

Operational dashboards and governed audit history have different retention and access requirements. For member analytics and long-term audit records at a pension administrator, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The corresponding fix is to configure supported account usage reporting, collection and retention suitable for the approved audit period. A successful test shows an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.

C.

Warehouse credit costs can accrue during idle running time separately from actual query work. This choice does not explain the observed failure mechanism. For member analytics and long-term audit records at a pension administrator, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

D.

Cost governance thresholds must account for workload criticality and the different effects of monitor actions. This choice does not explain the observed failure mechanism. For member analytics and long-term audit records at a pension administrator, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

Question 82

At an environmental institute, a Snowflake analyst supporting monitoring station records and research datasets finds: A pipeline task reads a curated table before the upstream transform task finishes, producing inconsistent aggregates. They confirm: Task run history shows downstream execution is not gated on completion of the intended upstream dependency. Select the action and acceptance-test pair best matched to these facts.

  1. Provide separate supported streams or an intentional shared change-processing design for independently tracked consumers. — verification: Each intended consumer processes a seeded update once under the documented independent offset strategy.
  2. Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. — verification: A seeded data change appears in the published table within the approved achievable freshness window.
  3. Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. — verification: A newly uploaded sample file appears in the target table once without a manual COPY command.
  4. Model a supported task graph with appropriate predecessor relationships and observable completion states. — verification: An end-to-end rehearsal runs steps in the intended order and publishes a consistent sample aggregate.

Correct Answer: D

Explanation

A.

Provide separate supported streams or an intentional shared change-processing design for independently tracked consumers. Verify that Each intended consumer processes a seeded update once under the documented independent offset strategy. Snowflake streams expose change data using consumable offsets that must match each consumer's semantics. For monitoring station records and research datasets at an environmental institute, task run history shows downstream execution is not gated on completion of the intended upstream dependency. The appropriate correction is to model a supported task graph with appropriate predecessor relationships and observable completion states. Confirm that an end-to-end rehearsal runs steps in the intended order and publishes a consistent sample aggregate.

B.

Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. Verify that a seeded data change appears in the published table within the approved achievable freshness window. Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. For monitoring station records and research datasets at an environmental institute, task run history shows downstream execution is not gated on completion of the intended upstream dependency. The appropriate correction is to model a supported task graph with appropriate predecessor relationships and observable completion states. Confirm that an end-to-end rehearsal runs steps in the intended order and publishes a consistent sample aggregate.

C.

Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. Verify that a newly uploaded sample file appears in the target table once without a manual COPY command. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. For monitoring station records and research datasets at an environmental institute, task run history shows downstream execution is not gated on completion of the intended upstream dependency. The appropriate correction is to model a supported task graph with appropriate predecessor relationships and observable completion states. Confirm that an end-to-end rehearsal runs steps in the intended order and publishes a consistent sample aggregate.

D.

Model a supported task graph with appropriate predecessor relationships and observable completion states. Verify that an end-to-end rehearsal runs steps in the intended order and publishes a consistent sample aggregate. For monitoring station records and research datasets at an environmental institute, task run history shows downstream execution is not gated on completion of the intended upstream dependency. Task orchestration must represent data dependencies rather than assuming independent schedules stay aligned.

Question 83

In inventory traceability and shipping records at a pharmaceutical wholesaler, a validated correction is proposed: Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. It responds to: A reporting view exposes full national identifiers to a broad analyst role despite a requirement to show only redacted values. Choose the best measurable success criterion.

  1. Positive and negative tenant tests return only authorized records for each role.
  2. Restricted roles receive redacted test values and a specifically authorized role receives only approved detail.
  3. A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.
  4. A synthetic policy finding reaches an accountable security queue with evidence and response tracking.

Correct Answer: B

Explanation

A.

Positive and negative tenant tests return only authorized records for each role. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. A confirming test shows that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

B.

Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Dynamic masking can enforce column-value protection according to access context. To correct it, attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.

C.

A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. A confirming test shows that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

D.

A synthetic policy finding reaches an accountable security queue with evidence and response tracking. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. A confirming test shows that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

Question 84

To correct this issue at a regional law practice involving legal matter metrics and billing data marts: A reporting view exposes full national identifiers to a broad analyst role despite a requirement to show only redacted values. The team applies: Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. What outcome should close the incident?

  1. Positive and negative tenant tests return only authorized records for each role.
  2. A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.
  3. The user loses unauthorized read access in all permitted role combinations while approved data remains accessible.
  4. Restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

Correct Answer: D

Explanation

A.

Positive and negative tenant tests return only authorized records for each role. Row-level security requires correct identity-to-row entitlement logic. For legal matter metrics and billing data marts at a regional law practice, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Verify that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

B.

A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For legal matter metrics and billing data marts at a regional law practice, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Verify that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

C.

The user loses unauthorized read access in all permitted role combinations while approved data remains accessible. Snowflake authorization can aggregate primary and enabled secondary role privileges. For legal matter metrics and billing data marts at a regional law practice, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Verify that restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

D.

Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. For legal matter metrics and billing data marts at a regional law practice, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Dynamic masking can enforce column-value protection according to access context. To address this, attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.

Question 85

Administrators at a regional transit agency plan: Set explicit intended database and schema context or fully qualify production-sensitive object references. They are addressing the following problem in fleet schedules and passenger ridership datasets: A developer runs the same SQL from an IDE and Snowsight but receives a table-not-found error only in the IDE. Which test demonstrates resolution?

  1. Both approved client sessions resolve the same intended table without using elevated roles.
  2. A sanctioned notebook cell completes using its documented compute environment with no extra account privileges.
  3. The permitted operation succeeds under the correct role and an unrelated privileged action is denied.
  4. A dry run targets the approved development account and refuses to modify unrelated environments.

Correct Answer: A

Explanation

A.

Both approved client sessions resolve the same intended table without using elevated roles. For fleet schedules and passenger ridership datasets at a regional transit agency, the IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace. Snowflake session context and object qualification determine how SQL names are resolved. The corresponding fix is to set explicit intended database and schema context or fully qualify production-sensitive object references.

B.

A sanctioned notebook cell completes using its documented compute environment with no extra account privileges. Interactive development tools still require supported execution compute and role context. For fleet schedules and passenger ridership datasets at a regional transit agency, the IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace. A meaningful check confirms that both approved client sessions resolve the same intended table without using elevated roles.

C.

The permitted operation succeeds under the correct role and an unrelated privileged action is denied. Snowsight executes SQL within the selected session role, database, schema and warehouse context. For fleet schedules and passenger ridership datasets at a regional transit agency, the IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace. A meaningful check confirms that both approved client sessions resolve the same intended table without using elevated roles.

D.

A dry run targets the approved development account and refuses to modify unrelated environments. A successful client connection does not establish that the selected account context is correct. For fleet schedules and passenger ridership datasets at a regional transit agency, the IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace. A meaningful check confirms that both approved client sessions resolve the same intended table without using elevated roles.

Question 86

The supplier pricing and regional inventory models environment at a food distribution cooperative has an incident: A transformation query spills heavily on a small warehouse while designers propose multi-cluster scale-out to shorten that one query. The difference-making observation is: Query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. Choose the most defensible corrective response.

  1. Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.
  2. Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency.
  3. Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely.
  4. Inspect query planning, object statistics, metadata and query shape before changing compute sizing.

Correct Answer: B

Explanation

A.

Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The better-matched action is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency.

B.

Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. For supplier pricing and regional inventory models at a food distribution cooperative, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. Warehouse scale-up and multi-cluster scale-out address different performance bottlenecks. A suitable check should show that the same query meets its resource target with less spill while total cost remains within budget.

C.

Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The better-matched action is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency.

D.

Inspect query planning, object statistics, metadata and query shape before changing compute sizing. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The better-matched action is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency.

Question 87

To correct this issue at a public university involving student analytics and research-grant reporting: An analyst exports a filtered customer dataset with COPY INTO location but the chosen stage points at an unauthorized storage prefix. The team applies: Use a reviewed external stage and scoped storage integration, then test approved unload output permissions. What outcome should close the incident?

  1. A controlled load reads authorized files through approved integration and no plaintext secret is required in the script.
  2. A seeded export appears only in the authorized destination and a test unauthorized prefix is denied.
  3. A controlled new document appears in the governed directory inventory and is retrievable by approved users.
  4. Representative old and new files load into correct columns and invalid fields raise reviewed exceptions.

Correct Answer: B

Explanation

A.

A controlled load reads authorized files through approved integration and no plaintext secret is required in the script. Storage integrations provide a governed trust boundary for external staged data. For student analytics and research-grant reporting at a public university, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. A confirming test shows that a seeded export appears only in the authorized destination and a test unauthorized prefix is denied.

B.

A seeded export appears only in the authorized destination and a test unauthorized prefix is denied. For student analytics and research-grant reporting at a public university, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. Unloading data creates an outbound data-governance boundary that requires destination authorization. To correct it, use a reviewed external stage and scoped storage integration, then test approved unload output permissions.

C.

A controlled new document appears in the governed directory inventory and is retrievable by approved users. Directory metadata can require refresh or event configuration independent of files stored externally. For student analytics and research-grant reporting at a public university, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. A confirming test shows that a seeded export appears only in the authorized destination and a test unauthorized prefix is denied.

D.

Representative old and new files load into correct columns and invalid fields raise reviewed exceptions. Bulk ingestion correctness requires explicit handling of changing file schema and COPY options. For student analytics and research-grant reporting at a public university, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. A confirming test shows that a seeded export appears only in the authorized destination and a test unauthorized prefix is denied.

Question 88

For instrument results and governed case metadata at a medical testing laboratory, engineers propose: Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Their incident states: A report team expects a repeated SELECT to use the persisted result cache but keeps modifying the SQL text and underlying data. What evidence should be verified before implementing the change?

  1. Query contexts differ in security and session conditions and tests do not control source change timing.
  2. Query Profile shows a data scan and row access predicates, not a metadata-only computation.
  3. Query history shows new execution work and source-table modification timestamps between otherwise similar report runs.
  4. Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads.

Correct Answer: C

Explanation

A.

Query contexts differ in security and session conditions and tests do not control source change timing. Query result reuse depends on relevant session and security conditions as well as SQL text. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Instead, inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.

B.

Query Profile shows a data scan and row access predicates, not a metadata-only computation. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Instead, inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.

C.

Query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Snowflake persisted query results are reused only when the required consistency and context conditions are met. To address this, inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Confirm that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results; the reported setting is: for instrument results and governed case metadata at a medical testing laboratory, engineers propose: inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on as.

D.

Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. Query optimization governance needs observable workload attribution, not only raw credits. For instrument results and governed case metadata at a medical testing laboratory, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Instead, inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.

Question 89

The supplier pricing and regional inventory models team at a food distribution cooperative records: A data team hardcodes a cloud storage key in a CREATE STAGE statement shared with many analysts. Logs confirm: Configuration review finds a plaintext storage secret stored in a copied deployment script. The recommended action is: Use a supported storage integration and scoped external stage access rather than embedding long-lived credentials. What underlying Snowflake solution principle applies?

  1. Unloading data creates an outbound data-governance boundary that requires destination authorization.
  2. Directory metadata can require refresh or event configuration independent of files stored externally.
  3. Snowflake load parsing depends on the staged file format matching the actual source encoding.
  4. Storage integrations provide a governed trust boundary for external staged data.

Correct Answer: D

Explanation

A.

Unloading data creates an outbound data-governance boundary that requires destination authorization. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, configuration review finds a plaintext storage secret stored in a copied deployment script. The controlling principle is that storage integrations provide a governed trust boundary for external staged data.

B.

Directory metadata can require refresh or event configuration independent of files stored externally. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, configuration review finds a plaintext storage secret stored in a copied deployment script. The controlling principle is that storage integrations provide a governed trust boundary for external staged data.

C.

Snowflake load parsing depends on the staged file format matching the actual source encoding. This choice does not explain the observed failure mechanism. For supplier pricing and regional inventory models at a food distribution cooperative, configuration review finds a plaintext storage secret stored in a copied deployment script. The controlling principle is that storage integrations provide a governed trust boundary for external staged data.

D.

Storage integrations provide a governed trust boundary for external staged data. For supplier pricing and regional inventory models at a food distribution cooperative, configuration review finds a plaintext storage secret stored in a copied deployment script. The corresponding fix is to use a supported storage integration and scoped external stage access rather than embedding long-lived credentials. A successful test shows a controlled load reads authorized files through approved integration and no plaintext secret is required in the script.

Question 90

The Snowflake data engineering team at a renewable energy utility plans to: Correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. The issue affecting meter ingestion and maintenance trend analysis is: A shared case table returns records for customers in unrelated business units under a narrowly scoped analyst role. Which finding best distinguishes this cause from other Snowflake failures?

  1. A low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column.
  2. Data profiling finds untagged sensitive fields and a generic table tag provides no reliable column inventory.
  3. Notification configuration references an unmonitored destination and the latest known control finding has no ticket.
  4. A controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping.

Correct Answer: D

Explanation

A.

A low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. Dynamic masking can enforce column-value protection according to access context. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

B.

Data profiling finds untagged sensitive fields and a generic table tag provides no reliable column inventory. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

C.

Notification configuration references an unmonitored destination and the latest known control finding has no ticket. Security monitoring requires actionable ownership and alert delivery, not just a healthy detection engine. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

D.

A controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. Row-level security requires correct identity-to-row entitlement logic. The documented change is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. The acceptance check is whether positive and negative tenant tests return only authorized records for each role.

SnowPro Core COF-C03 Practice Tests