Snowflake SnowPro Core COF-C03 Practice Test 18 - 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 18

Question 170

A Snowflake analyst supporting care utilization metrics and de-identified clinical reporting at a hospital network intends: Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. The reported condition is: An analyst runs a Snowflake Notebook that accesses a table successfully in one session but fails in another because no valid execution warehouse is assigned. Identify the most decisive diagnostic record.

  1. Worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role.
  2. Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct.
  3. The IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace.
  4. Query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized.

Correct Answer: B

Explanation

A.

Worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. The better-matched action is to configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.

B.

Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. Interactive development tools still require supported execution compute and role context. The documented change is to configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. The acceptance check is whether a sanctioned notebook cell completes using its documented compute environment with no extra account privileges.

C.

The IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. The better-matched action is to configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.

D.

Query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. The better-matched action is to configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.

Question 171

The Snowflake data engineering case at a manufacturing group concerns factory telemetry and supplier quality dashboards. Problem: An engineer grants a service external API integration unrestricted access when its stored procedure only requires one approved endpoint. Evidence: Integration inventory shows an allowed destination list much wider than the program's documented business requirement. Which paired corrective action and verification is best?

  1. Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. — verification: A controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible.
  2. Pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution. — verification: A controlled release executes only reviewed SQL and rejects unapproved branch changes.
  3. Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. — verification: A permitted endpoint call works while an unrelated destination cannot be contacted through the integration.
  4. Use a reviewed external stage and scoped storage integration, then test approved unload output permissions. — verification: A seeded export appears only in the authorized destination and a test unauthorized prefix is denied.

Correct Answer: C

Explanation

A.

Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. Verify that a controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible. Snowflake connectivity spans internal roles and external provider identity policy. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. The appropriate correction is to define a scoped supported API integration with reviewed network rules and controlled invocation privileges. Confirm that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.

B.

Pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution. Verify that a controlled release executes only reviewed SQL and rejects unapproved branch changes. Source integration needs version control and approval just like any other production schema deployment. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. The appropriate correction is to define a scoped supported API integration with reviewed network rules and controlled invocation privileges. Confirm that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.

C.

Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. Verify that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. External network and API integrations should constrain egress destinations and execution privileges.

D.

Use a reviewed external stage and scoped storage integration, then test approved unload output permissions. Verify that a seeded export appears only in the authorized destination and a test unauthorized prefix is denied. Unloading data creates an outbound data-governance boundary that requires destination authorization. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. The appropriate correction is to define a scoped supported API integration with reviewed network rules and controlled invocation privileges. Confirm that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.

Question 172

For cargo scans and berth utilization reports at a container port operator, an engineer diagnoses: A role investigation finds a user can access a table even after the primary active role lost its SELECT privilege. The observation is: Session diagnostics show an enabled secondary role still grants access to the table. The response is: Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. Which principle best explains the decision?

  1. Database roles scope database privileges and are activated through account-role inheritance.
  2. Snowflake authorization can aggregate primary and enabled secondary role privileges.
  3. Snowflake role authorization must cover both referenced data and chosen execution warehouse.
  4. Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.

Correct Answer: B

Explanation

A.

Database roles scope database privileges and are activated through account-role inheritance. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

B.

Snowflake authorization can aggregate primary and enabled secondary role privileges. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. To address this, review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. A successful test shows the user loses unauthorized read access in all permitted role combinations while approved data remains accessible.

C.

Snowflake role authorization must cover both referenced data and chosen execution warehouse. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

D.

Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

Question 173

In regulated batch tracking and delivery datasets at a healthcare distributor, a validated correction is proposed: Configure supported account usage reporting, collection and retention suitable for the approved audit period. It responds to: A compliance team discovers unusual data access after its short-lived dashboard has rolled off the required audit interval. Choose the best measurable success criterion.

  1. A controlled cost report reconciles key service charges and supports assigned service ownership.
  2. An authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.
  3. After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully.
  4. A controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

Correct Answer: B

Explanation

A.

A controlled cost report reconciles key service charges and supports assigned service ownership. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. A meaningful check confirms that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.

B.

An authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. Operational dashboards and governed audit history have different retention and access requirements. The corresponding fix is to configure supported account usage reporting, collection and retention suitable for the approved audit period.

C.

After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. A meaningful check confirms that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.

D.

A controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. A meaningful check confirms that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.

Question 174

The Snowflake data engineering team at an identity verification firm plans to: Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. The issue affecting verification logs and service risk scoring is: A query runs quickly in isolation but takes minutes during the busiest hour, and engineers rewrite SQL unnecessarily. Which finding best distinguishes this cause from other Snowflake failures?

  1. Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads.
  2. Query History separates long queued time from short actual execution and shows many simultaneous sessions.
  3. Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly.
  4. Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent.

Correct Answer: B

Explanation

A.

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 verification logs and service risk scoring at an identity verification firm, query History separates long queued time from short actual execution and shows many simultaneous sessions. The better-matched action is to tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL.

B.

Query History separates long queued time from short actual execution and shows many simultaneous sessions. Total query latency includes queue time as well as execution and compilation. The documented change is to tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. The acceptance check is whether peak reports complete within queue wait targets while isolated query execution time stays stable.

C.

Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For verification logs and service risk scoring at an identity verification firm, query History separates long queued time from short actual execution and shows many simultaneous sessions. The better-matched action is to tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL.

D.

Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Pruning efficiency depends on how filter predicates interact with micro-partition metadata. For verification logs and service risk scoring at an identity verification firm, query History separates long queued time from short actual execution and shows many simultaneous sessions. The better-matched action is to tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL.

Question 175

At a customs broker, a Snowflake analyst supporting cross-border shipment data and clearance events finds: An operations team assumes suspending its only virtual warehouse will erase permanent customer data and keeps compute running all night. They confirm: Billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. Select the action and acceptance-test pair best matched to these facts.

  1. Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. — verification: An idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.
  2. Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. — verification: Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes.
  3. Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. — verification: Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies.
  4. Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production. — verification: A controlled create, query and snapshot lifecycle test follows the documented ownership model without orphaned files.

Correct Answer: A

Explanation

A.

Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Verify that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. Snowflake separates independently scalable query compute from persistent managed table storage.

B.

Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. Verify that Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes. Compute-credit consumption and managed storage usage are distinct cost drivers. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. The appropriate correction is to separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Confirm that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

C.

Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. Verify that Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies. Independent virtual warehouses support workload isolation over shared centralized data. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. The appropriate correction is to separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Confirm that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

D.

Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production. Verify that a controlled create, query and snapshot lifecycle test follows the documented ownership model without orphaned files. Open table format interoperability needs explicit metadata and storage management boundaries. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. The appropriate correction is to separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Confirm that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

Question 176

In network event logs and account churn models at a telecommunications provider, a validated correction is proposed: Review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases. It responds to: Business users ask an AI analyst for net revenue but the semantic model describes gross invoice amount as net revenue. Choose the best measurable success criterion.

  1. A controlled search locates the approved updated policy while respecting source access constraints.
  2. A permitted viewer sees only approved aggregates and cannot retrieve underlying restricted rows.
  3. Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies.
  4. The seeded net-revenue query matches a reviewed SQL baseline across sample periods.

Correct Answer: D

Explanation

A.

A controlled search locates the approved updated policy while respecting source access constraints. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. Verify that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

B.

A permitted viewer sees only approved aggregates and cannot retrieve underlying restricted rows. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. Verify that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

C.

Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. Verify that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

D.

The seeded net-revenue query matches a reviewed SQL baseline across sample periods. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. Natural language analytics accuracy depends on governed metric definitions and source semantics. To address this, review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases.

Question 177

The Snowflake data engineering team at an identity verification firm plans to: Use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment. The issue affecting verification logs and service risk scoring is: A scheduled Snowflake CLI task applies a schema migration to staging instead of the intended development account. Which finding best distinguishes this cause from other Snowflake failures?

  1. The IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace.
  2. Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct.
  3. CLI connection profile and resolved account locator do not match the change request despite successful authentication.
  4. The application session explicitly sets the same parameter and its effective value differs from the new account default.

Correct Answer: C

Explanation

A.

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. For verification logs and service risk scoring at an identity verification firm, cLI connection profile and resolved account locator do not match the change request despite successful authentication. To address this, use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment.

B.

Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. Interactive development tools still require supported execution compute and role context. For verification logs and service risk scoring at an identity verification firm, cLI connection profile and resolved account locator do not match the change request despite successful authentication. To address this, use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment.

C.

CLI connection profile and resolved account locator do not match the change request despite successful authentication. A successful client connection does not establish that the selected account context is correct. The corresponding fix is to use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment. A successful test should show that a dry run targets the approved development account and refuses to modify unrelated environments; the reported setting is: the snowflake data engineering team at an identity verification firm plans to: use explicit vetted cli connection profiles, validate active account and role, and add preflight context assertions to deploym.

D.

The application session explicitly sets the same parameter and its effective value differs from the new account default. Snowflake parameters can be overridden at narrower scopes according to documented precedence. For verification logs and service risk scoring at an identity verification firm, cLI connection profile and resolved account locator do not match the change request despite successful authentication. To address this, use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment.

Question 178

At a municipal authority, a Snowflake analyst supporting citizen service reporting and licensed contractor data finds: A security team grants a database role to a user and expects the user to choose it directly as their active session role. They confirm: Role hierarchy records show the database role is not granted through an account role with supported activation. Select the action and acceptance-test pair best matched to these facts.

  1. Grant the database role to an appropriate account role and grant that account role to approved users. — verification: The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.
  2. Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. — verification: The user loses unauthorized read access in all permitted role combinations while approved data remains accessible.
  3. Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants. — verification: A query runs on the specified warehouse without granting access to unrelated compute resources.
  4. Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. — verification: A permitted service connection works from its approved egress address while an unauthorized source remains denied.

Correct Answer: A

Explanation

A.

Grant the database role to an appropriate account role and grant that account role to approved users. Verify that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. Database roles scope database privileges and are activated through account-role inheritance.

B.

Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. Verify that 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 citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The appropriate correction is to grant the database role to an appropriate account role and grant that account role to approved users. Confirm that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

C.

Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants. Verify that a query runs on the specified warehouse without granting access to unrelated compute resources. Snowflake role authorization must cover both referenced data and chosen execution warehouse. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The appropriate correction is to grant the database role to an appropriate account role and grant that account role to approved users. Confirm that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

D.

Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Verify that a permitted service connection works from its approved egress address while an unauthorized source remains denied. Network policies add source-network restrictions independent of SQL role grants. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The appropriate correction is to grant the database role to an appropriate account role and grant that account role to approved users. Confirm that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

Question 179

A Snowflake analyst supporting settlement reconciliation and fraud-monitoring datasets at a payments processor intends: Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. The reported condition is: A batch job experiences slower initial scans after each warehouse resume and administrators misinterpret the warm-cache difference. Identify the most decisive diagnostic record.

  1. Query contexts differ in security and session conditions and tests do not control source change timing.
  2. The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse.
  3. Query history shows new execution work and source-table modification timestamps between otherwise similar report runs.
  4. Query History separates long queued time from short actual execution and shows many simultaneous sessions.

Correct Answer: B

Explanation

A.

Query contexts differ in security and session conditions and tests do not control source change timing. This choice does not explain the observed failure mechanism. For settlement reconciliation and fraud-monitoring datasets at a payments processor, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. For this incident, compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it.

B.

The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. Virtual warehouse local data cache behavior differs from the persisted query result cache. To correct it, compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. Verification should establish that a repeat benchmark documents expected cold-start cost and maintains the agreed total workload SLA.

C.

Query history shows new execution work and source-table modification timestamps between otherwise similar report runs. This choice does not explain the observed failure mechanism. For settlement reconciliation and fraud-monitoring datasets at a payments processor, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. For this incident, compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it.

D.

Query History separates long queued time from short actual execution and shows many simultaneous sessions. This choice does not explain the observed failure mechanism. For settlement reconciliation and fraud-monitoring datasets at a payments processor, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. For this incident, compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it.

Question 180

The Snowflake data engineering team at a regional bank plans to: Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. The issue affecting customer risk analytics and branch transaction reports is: A dynamically refreshed reporting dataset is consistently older than the declared freshness target even though source tables update. Which finding best distinguishes this cause from other Snowflake failures?

  1. Task run history shows downstream execution is not gated on completion of the intended upstream dependency.
  2. Refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target.
  3. Service traces show time spent creating and notifying object-storage files rather than processing incoming rows.
  4. The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing.

Correct Answer: B

Explanation

A.

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. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. Instead, inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload.

B.

Refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. To address this, inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. Confirm that a seeded data change appears in the published table within the approved achievable freshness window.

C.

Service traces show time spent creating and notifying object-storage files rather than processing incoming rows. Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. Instead, inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload.

D.

The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. Instead, inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload.

SnowPro Core COF-C03 Practice Tests