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

Question 640

For settlement reconciliation and fraud-monitoring datasets at a payments processor, an engineer diagnoses: A batch job experiences slower initial scans after each warehouse resume and administrators misinterpret the warm-cache difference. The observation is: The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. The response is: Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. Which principle best explains the decision?

  1. Query result reuse depends on relevant session and security conditions as well as SQL text.
  2. Snowflake persisted query results are reused only when the required consistency and context conditions are met.
  3. Virtual warehouse local data cache behavior differs from the persisted query result cache.
  4. Total query latency includes queue time as well as execution and compilation.

Correct Answer: C

Explanation

A.

Query result reuse depends on relevant session and security conditions as well as SQL text. 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. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

B.

Snowflake persisted query results are reused only when the required consistency and context conditions are met. 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. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

C.

Virtual warehouse local data cache behavior differs from the persisted query result cache. 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. To address this, compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. A successful test shows a repeat benchmark documents expected cold-start cost and maintains the agreed total workload SLA.

D.

Total query latency includes queue time as well as execution and compilation. 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. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

Question 641

An operations review of member analytics and long-term audit records at a pension administrator reports: A developer grants table read permissions to a pipeline service user and expects that to authorize management of a Snowpipe pipe. The differentiating observation is: Privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. Which proposed fix and test pair most directly addresses the failure?

  1. Grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. — verification: An authorized report reads the target table and cannot access an unrelated schema.
  2. Choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation. — verification: A test execution completes the controlled multi-step process with an auditable outcome and no unsupported UDF side effects.
  3. Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. — verification: A new authorized session retrieves the intended prepared dataset after the original session ends.
  4. Apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. — verification: The service role performs the intended pipe operation but remains unable to administer unrelated objects.

Correct Answer: D

Explanation

A.

Grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. Verify that an authorized report reads the target table and cannot access an unrelated schema. This action and its verification do not address the identified failure together. For member analytics and long-term audit records at a pension administrator, privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. The appropriate correction is to apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Confirm that the service role performs the intended pipe operation but remains unable to administer unrelated objects.

B.

Choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation. Verify that a test execution completes the controlled multi-step process with an auditable outcome and no unsupported UDF side effects. This action and its verification do not address the identified failure together. For member analytics and long-term audit records at a pension administrator, privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. The appropriate correction is to apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Confirm that the service role performs the intended pipe operation but remains unable to administer unrelated objects.

C.

Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. Verify that a new authorized session retrieves the intended prepared dataset after the original session ends. This action and its verification do not address the identified failure together. For member analytics and long-term audit records at a pension administrator, privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. The appropriate correction is to apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Confirm that the service role performs the intended pipe operation but remains unable to administer unrelated objects.

D.

Apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Verify that the service role performs the intended pipe operation but remains unable to administer unrelated objects. For member analytics and long-term audit records at a pension administrator, privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. Pipes, stages, file formats, and tables are distinct Snowflake objects with different privileges.

Question 642

The Snowflake data engineering team at a public health agency investigating population program aggregates and access reviews notes: A batch job experiences slower initial scans after each warehouse resume and administrators misinterpret the warm-cache difference. Evidence: The first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. They plan: Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. Which technical principle justifies the correction?

  1. Virtual warehouse local data cache behavior differs from the persisted query result cache.
  2. Query result reuse depends on relevant session and security conditions as well as SQL text.
  3. Snowflake persisted query results are reused only when the required consistency and context conditions are met.
  4. Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior.

Correct Answer: A

Explanation

A.

Virtual warehouse local data cache behavior differs from the persisted query result cache. For population program aggregates and access reviews at a public health agency, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. The documented change is to compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. A successful test shows a repeat benchmark documents expected cold-start cost and maintains the agreed total workload SLA.

B.

Query result reuse depends on relevant session and security conditions as well as SQL text. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

C.

Snowflake persisted query results are reused only when the required consistency and context conditions are met. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

D.

Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, the first execution after resume performs more remote reads while subsequent queries show more warehouse-local reuse. The controlling principle is that virtual warehouse local data cache behavior differs from the persisted query result cache.

Question 643

At a legal services organization, a Snowflake analyst supporting case document metadata and restricted reporting finds: A data engineer executes a destructive administrative statement from a worksheet without noticing it inherited an elevated role. They confirm: Worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. Select the action and acceptance-test pair best matched to these facts.

  1. Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. — verification: A sanctioned notebook cell completes using its documented compute environment with no extra account privileges.
  2. Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. — verification: The permitted operation succeeds under the correct role and an unrelated privileged action is denied.
  3. Set explicit intended database and schema context or fully qualify production-sensitive object references. — verification: Both approved client sessions resolve the same intended table without using elevated roles.
  4. Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. — verification: A scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity.

Correct Answer: B

Explanation

A.

Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. Verify that 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 case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The appropriate correction is to change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Confirm that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.

B.

Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Verify that the permitted operation succeeds under the correct role and an unrelated privileged action is denied. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. Snowsight executes SQL within the selected session role, database, schema and warehouse context.

C.

Set explicit intended database and schema context or fully qualify production-sensitive object references. Verify that Both approved client sessions resolve the same intended table without using elevated roles. Snowflake session context and object qualification determine how SQL names are resolved. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The appropriate correction is to change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Confirm that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.

D.

Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. Verify that a scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity. Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The appropriate correction is to change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Confirm that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.

Question 644

An operations review of tenant repair requests and funding reporting at a nonprofit housing network reports: A team stores financial audit records in a transient table while its policy expects Fail-safe-based disaster recovery behavior. The differentiating observation is: Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. Which proposed fix and test pair most directly addresses the failure?

  1. 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.
  2. Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. — verification: A new authorized session retrieves the intended prepared dataset after the original session ends.
  3. Apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. — verification: The service role performs the intended pipe operation but remains unable to administer unrelated objects.
  4. Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. — verification: A documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe.

Correct Answer: D

Explanation

A.

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. This action and its verification do not address the identified failure together. For tenant repair requests and funding reporting at a nonprofit housing network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The appropriate correction is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. Confirm that a documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe.

B.

Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. Verify that a new authorized session retrieves the intended prepared dataset after the original session ends. This action and its verification do not address the identified failure together. For tenant repair requests and funding reporting at a nonprofit housing network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The appropriate correction is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. Confirm that a documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe.

C.

Apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Verify that the service role performs the intended pipe operation but remains unable to administer unrelated objects. This action and its verification do not address the identified failure together. For tenant repair requests and funding reporting at a nonprofit housing network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The appropriate correction is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. Confirm that a documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe.

D.

Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. Verify that a documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe. For tenant repair requests and funding reporting at a nonprofit housing network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. Permanent, transient and temporary tables have different lifecycle and data protection characteristics.

Question 645

The Snowflake data engineering team at a wholesale retailer investigating sales aggregates and supplier order tracking notes: A finance warehouse auto-suspends overnight but scheduled morning jobs fail because the service cannot resume it. Evidence: Warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. They plan: Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. Which technical principle justifies the correction?

  1. Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity.
  2. Warehouse scale-up and multi-cluster scale-out address different performance bottlenecks.
  3. Compute-credit consumption and managed storage usage are distinct cost drivers.
  4. Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads.

Correct Answer: D

Explanation

A.

Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. The controlling principle is that warehouse auto-suspend and auto-resume must be configured together for intermittent workloads.

B.

Warehouse scale-up and multi-cluster scale-out address different performance bottlenecks. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. The controlling principle is that warehouse auto-suspend and auto-resume must be configured together for intermittent workloads.

C.

Compute-credit consumption and managed storage usage are distinct cost drivers. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. The controlling principle is that warehouse auto-suspend and auto-resume must be configured together for intermittent workloads.

D.

Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads. For sales aggregates and supplier order tracking at a wholesale retailer, warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. The corresponding fix is to review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. A successful test shows a scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity.

Question 646

Administrators at an education charity plan: Review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases. They are addressing the following problem in program attendance and donor outcome reports: Business users ask an AI analyst for net revenue but the semantic model describes gross invoice amount as net revenue. Which test demonstrates resolution?

  1. A controlled search locates the approved updated policy while respecting source access constraints.
  2. The seeded net-revenue query matches a reviewed SQL baseline across sample periods.
  3. A permitted viewer sees only approved aggregates and cannot retrieve underlying restricted rows.
  4. A dry run targets the approved development account and refuses to modify unrelated environments.

Correct Answer: B

Explanation

A.

A controlled search locates the approved updated policy while respecting source access constraints. A retrieval service needs its own indexed-data freshness and authorization controls. For program attendance and donor outcome reports at an education charity, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The outcome should establish that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

B.

The seeded net-revenue query matches a reviewed SQL baseline across sample periods. For program attendance and donor outcome reports at an education charity, 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. The documented change is to review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases.

C.

A permitted viewer sees only approved aggregates and cannot retrieve underlying restricted rows. Application interfaces do not replace authorization checks at the data and execution boundary. For program attendance and donor outcome reports at an education charity, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The outcome should establish that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

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 program attendance and donor outcome reports at an education charity, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The outcome should establish that the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

Question 647

The verification logs and service risk scoring team at an identity verification firm records: A large fact table has well-partitioned date values but a report wraps the date in a function and scans most partitions. Logs confirm: Query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. The recommended action is: Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. What underlying Snowflake solution principle applies?

  1. Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning.
  2. Temporary tables are scoped to sessions and should not be treated as persistent shared datasets.
  3. Open table format interoperability needs explicit metadata and storage management boundaries.
  4. A successful client connection does not establish that the selected account context is correct.

Correct Answer: A

Explanation

A.

Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning. For verification logs and service risk scoring at an identity verification firm, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. To correct it, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. A successful test shows a seeded date-range query returns the same records while substantially fewer partitions are scanned.

B.

Temporary tables are scoped to sessions and should not be treated as persistent shared datasets. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. The controlling principle is that Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning.

C.

Open table format interoperability needs explicit metadata and storage management boundaries. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. The controlling principle is that Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning.

D.

A successful client connection does not establish that the selected account context is correct. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. The controlling principle is that Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning.

Question 648

The Snowflake data engineering team at a container port operator plans to: Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. The issue affecting cargo scans and berth utilization reports is: An application creates an intermediate dataset as a temporary table then expects another session to retrieve it the following morning. Which finding best distinguishes this cause from other Snowflake failures?

  1. Governance review finds external catalog or metadata ownership assumptions do not match the configured Iceberg management mode.
  2. Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables.
  3. The second session cannot resolve the temporary object although the creator session could query it earlier.
  4. The IDE connection has a different current database and schema and unqualified table names resolve to a stale namespace.

Correct Answer: C

Explanation

A.

Governance review finds external catalog or metadata ownership assumptions do not match the configured Iceberg management mode. Open table format interoperability needs explicit metadata and storage management boundaries. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

B.

Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. Permanent, transient and temporary tables have different lifecycle and data protection characteristics. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

C.

The second session cannot resolve the temporary object although the creator session could query it earlier. Temporary tables are scoped to sessions and should not be treated as persistent shared datasets. To address this, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. Confirm that a new authorized session retrieves the intended prepared dataset after the original session ends; the reported setting is: the snowflake data engineering team at a container port operator plans to: use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary st.

D.

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 cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

Question 649

For meter ingestion and maintenance trend analysis at a renewable energy utility, an engineer diagnoses: A team assumes every zero-copy clone immediately duplicates all source storage bytes and cancels a development test environment. The observation is: Storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The response is: Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Which principle best explains the decision?

  1. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.
  2. Time Travel provides configurable historical recovery only within supported object retention limits.
  3. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.
  4. Marketplace listing audience and share-grant design are independent governance controls.

Correct Answer: A

Explanation

A.

Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The corresponding fix is to assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. A successful test shows a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.

B.

Time Travel provides configurable historical recovery only within supported object retention limits. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The controlling principle is that Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.

C.

Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The controlling principle is that Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.

D.

Marketplace listing audience and share-grant design are independent governance controls. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The controlling principle is that Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.

Question 650

An operations review of building event streams and supplier invoices at a facilities management group reports: A web analytics team doubles warehouse size repeatedly but interactive users still queue during simultaneous peak requests. The differentiating observation is: Query history reports queuing across many concurrent sessions rather than individual query resource starvation. Which proposed fix and test pair most directly addresses the failure?

  1. Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. — verification: The same query meets its resource target with less spill while total cost remains within budget.
  2. Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. — verification: Peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters.
  3. Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. — verification: A scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity.
  4. 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.

Correct Answer: B

Explanation

A.

Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Verify that the same query meets its resource target with less spill while total cost remains within budget. This action and its verification do not address the identified failure together. For building event streams and supplier invoices at a facilities management group, query history reports queuing across many concurrent sessions rather than individual query resource starvation. The appropriate correction is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. Confirm that peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters.

B.

Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. Verify that Peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters. For building event streams and supplier invoices at a facilities management group, query history reports queuing across many concurrent sessions rather than individual query resource starvation. Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity.

C.

Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. Verify that a scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity. This action and its verification do not address the identified failure together. For building event streams and supplier invoices at a facilities management group, query history reports queuing across many concurrent sessions rather than individual query resource starvation. The appropriate correction is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. Confirm that peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters.

D.

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. This action and its verification do not address the identified failure together. For building event streams and supplier invoices at a facilities management group, query history reports queuing across many concurrent sessions rather than individual query resource starvation. The appropriate correction is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. Confirm that peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters.

SnowPro Core COF-C03 Practice Tests