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

Question 310

During a change review for booking data marts and occupancy forecasts at a hospitality chain, the team finds: A shared case table returns records for customers in unrelated business units under a narrowly scoped analyst role. Investigation shows: A controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. What is the most appropriate next Snowflake action?

  1. Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.
  2. Apply supported sensitive-data classification and governed object tags with review and ownership of findings.
  3. Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles.
  4. Correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

Correct Answer: D

Explanation

A.

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 booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

B.

Apply supported sensitive-data classification and governed object tags with review and ownership of findings. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

C.

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 booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The better-matched action is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception.

D.

Correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. For booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. Row-level security requires correct identity-to-row entitlement logic. A suitable check should show that positive and negative tenant tests return only authorized records for each role.

Question 311

The instrument results and governed case metadata team at a medical testing laboratory records: A partner refuses a data collaboration because it assumes a Snowflake direct share must physically copy the entire source table. Logs confirm: Collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. The recommended action is: Configure a supported secure data share with least privilege and document relevant region/account constraints. What underlying Snowflake solution principle applies?

  1. Reader accounts enable supported consumption without requiring a separate self-managed Snowflake account, but scope still matters.
  2. Clean rooms can support collaboration on sensitive data under controlled computations and output rules.
  3. Native Apps distribute governed in-platform logic, but installation privileges and lifecycle must still be reviewed.
  4. Snowflake secure sharing can provide governed access without traditional physical data copying.

Correct Answer: D

Explanation

A.

Reader accounts enable supported consumption without requiring a separate self-managed Snowflake account, but scope still matters. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. The controlling principle is that Snowflake secure sharing can provide governed access without traditional physical data copying.

B.

Clean rooms can support collaboration on sensitive data under controlled computations and output rules. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. The controlling principle is that Snowflake secure sharing can provide governed access without traditional physical data copying.

C.

Native Apps distribute governed in-platform logic, but installation privileges and lifecycle must still be reviewed. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. The controlling principle is that Snowflake secure sharing can provide governed access without traditional physical data copying.

D.

Snowflake secure sharing can provide governed access without traditional physical data copying. For instrument results and governed case metadata at a medical testing laboratory, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. To correct it, configure a supported secure data share with least privilege and document relevant region/account constraints. A successful test shows an authorized consumer queries the shared object while no unmanaged full dataset export is required.

Question 312

To correct this issue at a healthcare distributor involving regulated batch tracking and delivery datasets: An ingestion view casts a missing JSON attribute as a required numeric value and aborts a transformation batch. The team applies: Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. What outcome should close the incident?

  1. A three-element test array produces three authorized item rows with correct parent identifiers.
  2. Each test customer has the expected independent ranking without unexpected cross-customer influence.
  3. The revised approach meets report SLA at lower combined query and maintenance cost.
  4. Valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

Correct Answer: D

Explanation

A.

A three-element test array produces three authorized item rows with correct parent identifiers. Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. For regulated batch tracking and delivery datasets at a healthcare distributor, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. Verify that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

B.

Each test customer has the expected independent ranking without unexpected cross-customer influence. Window functions depend on the declared partition and ordering semantics. For regulated batch tracking and delivery datasets at a healthcare distributor, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. Verify that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

C.

The revised approach meets report SLA at lower combined query and maintenance cost. Materialized views trade faster repeated reads for storage and refresh maintenance. For regulated batch tracking and delivery datasets at a healthcare distributor, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. Verify that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

D.

Valid numeric fields transform correctly and missing values are flagged without silently inventing numbers. For regulated batch tracking and delivery datasets at a healthcare distributor, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior. To address this, use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT.

Question 313

At an online retail chain, a Snowflake analyst supporting return history and customer lifetime models finds: An app lists documents from an external stage but new files do not appear in its file inventory. They confirm: Directory table metadata is stale relative to the cloud object listing after an external upload. Select the action and acceptance-test pair best matched to these facts.

  1. 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.
  2. Validate supported stage directory table refresh or notification configuration with file access privileges. — verification: A controlled new document appears in the governed directory inventory and is retrievable by approved users.
  3. Correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO. — verification: A test batch loads the intended amounts and customer IDs into their correct columns without silent shift.
  4. 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.

Correct Answer: B

Explanation

A.

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 return history and customer lifetime models at an online retail chain, directory table metadata is stale relative to the cloud object listing after an external upload. The appropriate correction is to validate supported stage directory table refresh or notification configuration with file access privileges. Confirm that a controlled new document appears in the governed directory inventory and is retrievable by approved users.

B.

Validate supported stage directory table refresh or notification configuration with file access privileges. Verify that a controlled new document appears in the governed directory inventory and is retrievable by approved users. For return history and customer lifetime models at an online retail chain, directory table metadata is stale relative to the cloud object listing after an external upload. Directory metadata can require refresh or event configuration independent of files stored externally.

C.

Correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO. Verify that a test batch loads the intended amounts and customer IDs into their correct columns without silent shift. Snowflake load parsing depends on the staged file format matching the actual source encoding. For return history and customer lifetime models at an online retail chain, directory table metadata is stale relative to the cloud object listing after an external upload. The appropriate correction is to validate supported stage directory table refresh or notification configuration with file access privileges. Confirm that a controlled new document appears in the governed directory inventory and is retrievable by approved users.

D.

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 return history and customer lifetime models at an online retail chain, directory table metadata is stale relative to the cloud object listing after an external upload. The appropriate correction is to validate supported stage directory table refresh or notification configuration with file access privileges. Confirm that a controlled new document appears in the governed directory inventory and is retrievable by approved users.

Question 314

An operations review of fleet schedules and passenger ridership datasets at a regional transit agency reports: A FinOps team sees high daily query spend but cannot attribute it to the dashboard or scheduled transform responsible. The differentiating observation is: Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. Which proposed fix and test pair most directly addresses the failure?

  1. Introduce governed query tags and accountable job identity mapping with account usage reporting. — verification: A seeded expensive query is assigned to the correct operational owner in cost reporting.
  2. Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. — verification: Peak reports complete within queue wait targets while isolated query execution time stays stable.
  3. Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. — verification: A representative query reduces spill while preserving results and stays within cost limits.
  4. Restore a selective supported date-range predicate and compare query profile pruning under reproducible data. — verification: Same expected rows return with fewer partitions scanned and lower measured query cost.

Correct Answer: A

Explanation

A.

Introduce governed query tags and accountable job identity mapping with account usage reporting. Verify that a seeded expensive query is assigned to the correct operational owner in cost reporting. For fleet schedules and passenger ridership datasets at a regional transit agency, 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.

B.

Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. Verify that Peak reports complete within queue wait targets while isolated query execution time stays stable. This action and its verification do not address the identified failure together. For fleet schedules and passenger ridership datasets at a regional transit agency, query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. The appropriate correction is to introduce governed query tags and accountable job identity mapping with account usage reporting. Confirm that a seeded expensive query is assigned to the correct operational owner in cost reporting.

C.

Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. Verify that a representative query reduces spill while preserving results and stays within cost limits. This action and its verification do not address the identified failure together. For fleet schedules and passenger ridership datasets at a regional transit agency, query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. The appropriate correction is to introduce governed query tags and accountable job identity mapping with account usage reporting. Confirm that a seeded expensive query is assigned to the correct operational owner in cost reporting.

D.

Restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Verify that Same expected rows return with fewer partitions scanned and lower measured query cost. This action and its verification do not address the identified failure together. For fleet schedules and passenger ridership datasets at a regional transit agency, query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. The appropriate correction is to introduce governed query tags and accountable job identity mapping with account usage reporting. Confirm that a seeded expensive query is assigned to the correct operational owner in cost reporting.

Question 315

The Snowflake data engineering case at a medical testing laboratory concerns instrument results and governed case metadata. Problem: A team publishes a sensitive metric without being able to show which raw tables and transformations contributed to it. Evidence: The dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. Which paired corrective action and verification is best?

  1. Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. — verification: An auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.
  2. Apply supported sensitive-data classification and governed object tags with review and ownership of findings. — verification: A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.
  3. Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. — verification: Restricted roles receive redacted test values and a specifically authorized role receives only approved detail.
  4. Update approved alert and notification destinations and verify escalation through the current security ownership process. — verification: A synthetic policy finding reaches an accountable security queue with evidence and response tracking.

Correct Answer: A

Explanation

A.

Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. Verify that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. Data lineage supports governed interpretation and change impact beyond final result values.

B.

Apply supported sensitive-data classification and governed object tags with review and ownership of findings. Verify that a seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The appropriate correction is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership. Confirm that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

C.

Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Verify that Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. Dynamic masking can enforce column-value protection according to access context. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The appropriate correction is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership. Confirm that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

D.

Update approved alert and notification destinations and verify escalation through the current security ownership process. Verify that a synthetic policy finding reaches an accountable security queue with evidence and response tracking. Security monitoring requires actionable ownership and alert delivery, not just a healthy detection engine. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The appropriate correction is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership. Confirm that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

Question 316

Administrators at an engineering design firm plan: Inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness. They are addressing the following problem in project time-series and contract expenditure models: An internal document assistant retrieves old policy text after new documents were ingested into its source table. 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 representative transformation completes without bulk workstation export and produces matching approved results.
  4. Fresh client sessions observe the approved effective setting and no unexpected behavior persists.

Correct Answer: A

Explanation

A.

A controlled search locates the approved updated policy while respecting source access constraints. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. A retrieval service needs its own indexed-data freshness and authorization controls. To address this, inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness.

B.

The seeded net-revenue query matches a reviewed SQL baseline across sample periods. Natural language analytics accuracy depends on governed metric definitions and source semantics. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. Verify that a controlled search locates the approved updated policy while respecting source access constraints.

C.

A representative transformation completes without bulk workstation export and produces matching approved results. Snowpark enables supported programming-language computations within the Snowflake processing environment. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. Verify that a controlled search locates the approved updated policy while respecting source access constraints.

D.

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 project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. Verify that a controlled search locates the approved updated policy while respecting source access constraints.

Question 317

In tenant repair requests and funding reporting at a nonprofit housing network, a validated correction is proposed: Use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy. It responds to: An integration replaces a controlled OAuth client with a long-lived shared user password to connect to Snowflake. Choose the best measurable success criterion.

  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. A permitted service connection works from its approved egress address while an unauthorized source remains denied.

Correct Answer: B

Explanation

A.

A query runs on the specified warehouse without granting access to unrelated compute resources. This choice does not explain the observed failure mechanism. For tenant repair requests and funding reporting at a nonprofit housing network, credential inventory shows shared secret reuse and missing application-scoped access auditing. A meaningful check confirms 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 tenant repair requests and funding reporting at a nonprofit housing network, credential inventory shows shared secret reuse and missing application-scoped access auditing. Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. The corresponding fix is to 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. This choice does not explain the observed failure mechanism. For tenant repair requests and funding reporting at a nonprofit housing network, credential inventory shows shared secret reuse and missing application-scoped access auditing. A meaningful check confirms that the integration authenticates successfully without a human password and logs tie actions to the approved service identity.

D.

A permitted service connection works from its approved egress address while an unauthorized source remains denied. This choice does not explain the observed failure mechanism. For tenant repair requests and funding reporting at a nonprofit housing network, credential inventory shows shared secret reuse and missing application-scoped access auditing. A meaningful check confirms that the integration authenticates successfully without a human password and logs tie actions to the approved service identity.

Question 318

The Snowflake data engineering team at a hospital network investigating care utilization metrics and de-identified clinical reporting notes: 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. Evidence: Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. They plan: Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. Which technical principle justifies the correction?

  1. Snowsight executes SQL within the selected session role, database, schema and warehouse context.
  2. Snowflake session context and object qualification determine how SQL names are resolved.
  3. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.
  4. Interactive development tools still require supported execution compute and role context.

Correct Answer: D

Explanation

A.

Snowsight executes SQL within the selected session role, database, schema and warehouse context. 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 controlling principle is that interactive development tools still require supported execution compute and role context.

B.

Snowflake session context and object qualification determine how SQL names are resolved. 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 controlling principle is that interactive development tools still require supported execution compute and role context.

C.

Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. 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 controlling principle is that interactive development tools still require supported execution compute and role context.

D.

Interactive development tools still require supported execution compute and role context. 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 documented change is to configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. A successful test shows a sanctioned notebook cell completes using its documented compute environment with no extra account privileges.

Question 319

For application case metrics and protected citizen records at a benefits agency, engineers propose: Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. Their incident states: A ranking query assigns the same top order to multiple customers because the window partition uses a shared region code. What evidence should be verified before implementing the change?

  1. Source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior.
  2. A seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks.
  3. A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count.
  4. Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers.

Correct Answer: B

Explanation

A.

Source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. MERGE correctness requires an unambiguous source-to-target matching strategy. For application case metrics and protected citizen records at a benefits agency, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. For this incident, use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.

B.

A seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. Window functions depend on the declared partition and ordering semantics. To correct it, use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. Verification should establish that each test customer has the expected independent ranking without unexpected cross-customer influence; the reported setting is: for application case metrics and protected citizen records at a benefits agency, engineers propose: use the correct business key in partition by with explicit deterministic order by where needed.

C.

A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. For application case metrics and protected citizen records at a benefits agency, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. For this incident, use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.

D.

Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Join cardinality affects both query cost and semantic result correctness. For application case metrics and protected citizen records at a benefits agency, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. For this incident, use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.

Question 320

An operations review of loan servicing analytics and audit trails at a cooperative credit union reports: An analyst who can read a sensitive table tries to grant another team permission without owning the object or having grant authority. The differentiating observation is: SHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Which proposed fix and test pair most directly addresses the failure?

  1. 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.
  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. Route the access change through a documented object owner or authorized security role with approval and minimal privileges. — verification: An approved user gains needed read access while an unauthorized analyst cannot grant it onward.
  4. Use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy. — verification: The integration authenticates successfully without a human password and logs tie actions to the approved service identity.

Correct Answer: C

Explanation

A.

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. This action and its verification do not address the identified failure together. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The appropriate correction is to Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Confirm that an approved user gains needed read access while an unauthorized analyst cannot grant it onward.

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. This action and its verification do not address the identified failure together. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The appropriate correction is to Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Confirm that an approved user gains needed read access while an unauthorized analyst cannot grant it onward.

C.

Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Verify that an approved user gains needed read access while an unauthorized analyst cannot grant it onward. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.

D.

Use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy. Verify that the integration authenticates successfully without a human password and logs tie actions to the approved service identity. This action and its verification do not address the identified failure together. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The appropriate correction is to Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Confirm that an approved user gains needed read access while an unauthorized analyst cannot grant it onward.

SnowPro Core COF-C03 Practice Tests