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

Question 780

For sales aggregates and supplier order tracking at a wholesale retailer, Snowflake administrators supporting sales aggregates and supplier order tracking report: A security team grants a database role to a user and expects the user to choose it directly as their active session role. Their diagnostic record states: Role hierarchy records show the database role is not granted through an account role with supported activation. Which corrective action is best supported by the evidence?

  1. Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.
  2. Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants.
  3. Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.
  4. Grant the database role to an appropriate account role and grant that account role to approved users.

Correct Answer: D

Explanation

A.

Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. Snowflake authorization can aggregate primary and enabled secondary role privileges. For sales aggregates and supplier order tracking at a wholesale retailer, role hierarchy records show the database role is not granted through an account role with supported activation. Instead, grant the database role to an appropriate account role and grant that account role to approved users.

B.

Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants. Snowflake role authorization must cover both referenced data and chosen execution warehouse. For sales aggregates and supplier order tracking at a wholesale retailer, role hierarchy records show the database role is not granted through an account role with supported activation. Instead, grant the database role to an appropriate account role and grant that account role to approved users.

C.

Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Dynamic masking can enforce column-value protection according to access context. For sales aggregates and supplier order tracking at a wholesale retailer, role hierarchy records show the database role is not granted through an account role with supported activation. Instead, grant the database role to an appropriate account role and grant that account role to approved users.

D.

Grant the database role to an appropriate account role and grant that account role to approved users. For sales aggregates and supplier order tracking at a wholesale retailer, 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. A confirming result should show that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

Question 781

For application case metrics and protected citizen records at a benefits agency, an engineer diagnoses: A dashboard experiences long compilation times but engineers keep increasing its warehouse size without changing query planning. The observation is: Query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The response is: Inspect query planning, object statistics, metadata and query shape before changing compute sizing. Which principle best explains the decision?

  1. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.
  2. Independent virtual warehouses support workload isolation over shared centralized data.
  3. Compute-credit consumption and managed storage usage are distinct cost drivers.
  4. Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity.

Correct Answer: A

Explanation

A.

Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. For application case metrics and protected citizen records at a benefits agency, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The corresponding fix is to inspect query planning, object statistics, metadata and query shape before changing compute sizing. A successful test shows a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.

B.

Independent virtual warehouses support workload isolation over shared centralized data. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The controlling principle is that Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.

C.

Compute-credit consumption and managed storage usage are distinct cost drivers. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The controlling principle is that Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.

D.

Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The controlling principle is that Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.

Question 782

A Snowflake analyst supporting cross-border shipment data and clearance events at a customs broker intends: Set and audit approved client connection role, warehouse and namespace parameters with least privilege. The reported condition is: A customer application authenticates through a JDBC driver but queries fail only after deploying a new connection pool. Identify the most decisive diagnostic record.

  1. Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal.
  2. Integration inventory shows an allowed destination list much wider than the program's documented business requirement.
  3. Service traces show time spent creating and notifying object-storage files rather than processing incoming rows.
  4. New sessions use a different default role and warehouse from the earlier connector configuration.

Correct Answer: D

Explanation

A.

Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. The better-matched action is to set and audit approved client connection role, warehouse and namespace parameters with least privilege.

B.

Integration inventory shows an allowed destination list much wider than the program's documented business requirement. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. The better-matched action is to set and audit approved client connection role, warehouse and namespace parameters with least privilege.

C.

Service traces show time spent creating and notifying object-storage files rather than processing incoming rows. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. The better-matched action is to set and audit approved client connection role, warehouse and namespace parameters with least privilege.

D.

New sessions use a different default role and warehouse from the earlier connector configuration. Snowflake drivers inherit or specify security and execution context separately from successful transport authentication. The documented change is to set and audit approved client connection role, warehouse and namespace parameters with least privilege. The acceptance check is whether a test client reads the sanctioned table and remains unable to query a restricted table; the reported setting is: a snowflake analyst supporting cross-border shipment data and clearance events at a customs broker intends: set and audit approved client connection role, warehouse and namespace parameters with least priv.

Question 783

For cross-border shipment data and clearance events at a customs broker, Snowflake administrators supporting cross-border shipment data and clearance events report: A customer application authenticates through a JDBC driver but queries fail only after deploying a new connection pool. Their diagnostic record states: New sessions use a different default role and warehouse from the earlier connector configuration. Which corrective action is best supported by the evidence?

  1. Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access.
  2. Set and audit approved client connection role, warehouse and namespace parameters with least privilege.
  3. Define a scoped supported API integration with reviewed network rules and controlled invocation privileges.
  4. Evaluate supported Snowpipe Streaming ingestion for the event stream with approved connector identity and latency testing.

Correct Answer: B

Explanation

A.

Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. Snowflake connectivity spans internal roles and external provider identity policy. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. For this incident, set and audit approved client connection role, warehouse and namespace parameters with least privilege.

B.

Set and audit approved client connection role, warehouse and namespace parameters with least privilege. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. Snowflake drivers inherit or specify security and execution context separately from successful transport authentication. Verify that a test client reads the sanctioned table and remains unable to query a restricted table.

C.

Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. External network and API integrations should constrain egress destinations and execution privileges. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. For this incident, set and audit approved client connection role, warehouse and namespace parameters with least privilege.

D.

Evaluate supported Snowpipe Streaming ingestion for the event stream with approved connector identity and latency testing. Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. For cross-border shipment data and clearance events at a customs broker, new sessions use a different default role and warehouse from the earlier connector configuration. For this incident, set and audit approved client connection role, warehouse and namespace parameters with least privilege.

Question 784

During a change review for supplier pricing and regional inventory models at a food distribution cooperative, the team finds: A deployment pipeline runs Snowflake SQL from a repository but pulls an unreviewed experimental branch in production. Investigation shows: Resolved Git repository stage or branch reference differs from the approved tagged release. What is the most appropriate next Snowflake action?

  1. Define a scoped supported API integration with reviewed network rules and controlled invocation privileges.
  2. Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access.
  3. Model a supported task graph with appropriate predecessor relationships and observable completion states.
  4. Pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

Correct Answer: D

Explanation

A.

Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. External network and API integrations should constrain egress destinations and execution privileges. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. Instead, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

B.

Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. Snowflake connectivity spans internal roles and external provider identity policy. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. Instead, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

C.

Model a supported task graph with appropriate predecessor relationships and observable completion states. Task orchestration must represent data dependencies rather than assuming independent schedules stay aligned. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. Instead, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

D.

Pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. Source integration needs version control and approval just like any other production schema deployment. A confirming result should show that a controlled release executes only reviewed SQL and rejects unapproved branch changes.

Question 785

The return history and customer lifetime models team at an online retail chain records: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. Logs confirm: UNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The recommended action is: Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. What underlying Snowflake solution principle applies?

  1. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.
  2. Time Travel provides configurable historical recovery only within supported object retention limits.
  3. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.
  4. Snowflake functions and procedures have different execution contracts and appropriate use cases.

Correct Answer: A

Explanation

A.

Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. For return history and customer lifetime models at an online retail chain, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The corresponding fix is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. A successful test shows the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

B.

Time Travel provides configurable historical recovery only within supported object retention limits. This choice does not explain the observed failure mechanism. For return history and customer lifetime models at an online retail chain, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

C.

Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. This choice does not explain the observed failure mechanism. For return history and customer lifetime models at an online retail chain, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

D.

Snowflake functions and procedures have different execution contracts and appropriate use cases. This choice does not explain the observed failure mechanism. For return history and customer lifetime models at an online retail chain, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

Question 786

To correct this issue at a logistics operator involving shipment events and distribution forecast tables: A team reviews only warehouse metering when investigating higher account charges caused by serverless features. The team applies: Combine relevant account usage and serverless cost views with warehouse metrics for a complete workload accounting. What outcome should close the incident?

  1. A controlled cost report reconciles key service charges and supports assigned service ownership.
  2. A controlled spend threshold creates the expected notification for the targeted production warehouse.
  3. After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully.
  4. The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

Correct Answer: A

Explanation

A.

A controlled cost report reconciles key service charges and supports assigned service ownership. For shipment events and distribution forecast tables at a logistics operator, account usage records attribute substantial credits to non-warehouse services absent from warehouse-metering-only reports. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. The documented change is to combine relevant account usage and serverless cost views with warehouse metrics for a complete workload accounting.

B.

A controlled spend threshold creates the expected notification for the targeted production warehouse. Resource monitors act on associated virtual-warehouse credit usage rather than any unrelated account cost automatically. For shipment events and distribution forecast tables at a logistics operator, account usage records attribute substantial credits to non-warehouse services absent from warehouse-metering-only reports. The outcome should establish that a controlled cost report reconciles key service charges and supports assigned service ownership.

C.

After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully. Warehouse credit costs can accrue during idle running time separately from actual query work. For shipment events and distribution forecast tables at a logistics operator, account usage records attribute substantial credits to non-warehouse services absent from warehouse-metering-only reports. The outcome should establish that a controlled cost report reconciles key service charges and supports assigned service ownership.

D.

The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access. Database roles scope database privileges and are activated through account-role inheritance. For shipment events and distribution forecast tables at a logistics operator, account usage records attribute substantial credits to non-warehouse services absent from warehouse-metering-only reports. The outcome should establish that a controlled cost report reconciles key service charges and supports assigned service ownership.

Question 787

Administrators at an e-commerce marketplace plan: Use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy. They are addressing the following problem in shopping funnel events and merchant sales reporting: An integration replaces a controlled OAuth client with a long-lived shared user password to connect to Snowflake. Which test demonstrates resolution?

  1. A query runs on the specified warehouse without granting access to unrelated compute resources.
  2. The integration authenticates successfully without a human password and logs tie actions to the approved service identity.
  3. The user loses unauthorized read access in all permitted role combinations while approved data remains accessible.
  4. Positive and negative tenant tests return only authorized records for each role.

Correct Answer: B

Explanation

A.

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 shopping funnel events and merchant sales reporting at an e-commerce marketplace, credential inventory shows shared secret reuse and missing application-scoped access auditing. A confirming test shows that the integration authenticates successfully without a human password and logs tie actions to the approved service identity.

B.

The integration authenticates successfully without a human password and logs tie actions to the approved service identity. For shopping funnel events and merchant sales reporting at an e-commerce marketplace, credential inventory shows shared secret reuse and missing application-scoped access auditing. Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. To correct it, use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy.

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 shopping funnel events and merchant sales reporting at an e-commerce marketplace, credential inventory shows shared secret reuse and missing application-scoped access auditing. A confirming test shows that the integration authenticates successfully without a human password and logs tie actions to the approved service identity.

D.

Positive and negative tenant tests return only authorized records for each role. Row-level security requires correct identity-to-row entitlement logic. For shopping funnel events and merchant sales reporting at an e-commerce marketplace, credential inventory shows shared secret reuse and missing application-scoped access auditing. A confirming test shows that the integration authenticates successfully without a human password and logs tie actions to the approved service identity.

Question 788

In project time-series and contract expenditure models at an engineering design firm, a validated correction is proposed: Apply supported sensitive-data classification and governed object tags with review and ownership of findings. It responds to: An audit team adds generic sensitivity tags to tables but fails to identify columns actually containing new personal identifiers. Choose the best measurable success criterion.

  1. Restricted roles receive redacted test values and a specifically authorized role receives only approved detail.
  2. An auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.
  3. An approved user gains needed read access while an unauthorized analyst cannot grant it onward.
  4. A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.

Correct Answer: D

Explanation

A.

Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, data profiling finds untagged sensitive fields and a generic table tag provides no reliable column inventory. Verify that a seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.

B.

An auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, data profiling finds untagged sensitive fields and a generic table tag provides no reliable column inventory. Verify that a seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.

C.

An approved user gains needed read access while an unauthorized analyst cannot grant it onward. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, data profiling finds untagged sensitive fields and a generic table tag provides no reliable column inventory. Verify that a seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.

D.

A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. For project time-series and contract expenditure models at an engineering design firm, 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. To address this, apply supported sensitive-data classification and governed object tags with review and ownership of findings.

Question 789

To correct this issue at an insurance company involving claims actuarial datasets and policy renewal models: A scheduled Snowflake CLI task applies a schema migration to staging instead of the intended development account. The team applies: Use explicit vetted CLI connection profiles, validate active account and role, and add preflight context assertions to deployment. What outcome should close the incident?

  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. Fresh client sessions observe the approved effective setting and no unexpected behavior persists.
  4. A dry run targets the approved development account and refuses to modify unrelated environments.

Correct Answer: D

Explanation

A.

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 claims actuarial datasets and policy renewal models at an insurance company, cLI connection profile and resolved account locator do not match the change request despite successful authentication. A meaningful check confirms that a dry run targets the approved development account and refuses to modify unrelated environments.

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 claims actuarial datasets and policy renewal models at an insurance company, cLI connection profile and resolved account locator do not match the change request despite successful authentication. A meaningful check confirms that a dry run targets the approved development account and refuses to modify unrelated environments.

C.

Fresh client sessions observe the approved effective setting and no unexpected behavior persists. Snowflake parameters can be overridden at narrower scopes according to documented precedence. For claims actuarial datasets and policy renewal models at an insurance company, cLI connection profile and resolved account locator do not match the change request despite successful authentication. A meaningful check confirms that a dry run targets the approved development account and refuses to modify unrelated environments.

D.

A dry run targets the approved development account and refuses to modify unrelated environments. For claims actuarial datasets and policy renewal models at an insurance company, 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.

Question 790

For factory telemetry and supplier quality dashboards at a manufacturing group, an engineer diagnoses: A warehouse imports a supplier CSV file but amounts appear under the wrong columns while row counts look plausible. The observation is: Stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The response is: Correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO. Which principle best explains the decision?

  1. Snowflake load parsing depends on the staged file format matching the actual source encoding.
  2. Directory metadata can require refresh or event configuration independent of files stored externally.
  3. Bulk ingestion correctness requires explicit handling of changing file schema and COPY options.
  4. Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe.

Correct Answer: A

Explanation

A.

Snowflake load parsing depends on the staged file format matching the actual source encoding. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The documented change is to correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO. A successful test shows a test batch loads the intended amounts and customer IDs into their correct columns without silent shift.

B.

Directory metadata can require refresh or event configuration independent of files stored externally. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The controlling principle is that Snowflake load parsing depends on the staged file format matching the actual source encoding.

C.

Bulk ingestion correctness requires explicit handling of changing file schema and COPY options. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The controlling principle is that Snowflake load parsing depends on the staged file format matching the actual source encoding.

D.

Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The controlling principle is that Snowflake load parsing depends on the staged file format matching the actual source encoding.

SnowPro Core COF-C03 Practice Tests