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

Question 700

During a change review for return history and customer lifetime models at an online retail chain, the team finds: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. Investigation shows: UNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. What is the most appropriate next Snowflake action?

  1. Review supported table type, edition, retention settings and backup strategy against the required recovery objective.
  2. Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.
  3. Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.
  4. Configure a supported secure data share with least privilege and document relevant region/account constraints.

Correct Answer: B

Explanation

A.

Review supported table type, edition, retention settings and backup strategy against the required recovery objective. Time Travel provides configurable historical recovery only within supported object retention limits. 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. Instead, document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.

B.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. 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. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. A confirming result should show that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

C.

Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. 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. Instead, document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.

D.

Configure a supported secure data share with least privilege and document relevant region/account constraints. Snowflake secure sharing can provide governed access without traditional physical data copying. 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. Instead, document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.

Question 701

A Snowflake analyst supporting building event streams and supplier invoices at a facilities management group intends: Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. The reported condition is: A web analytics team doubles warehouse size repeatedly but interactive users still queue during simultaneous peak requests. Identify the most decisive diagnostic record.

  1. Query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions.
  2. Query history reports queuing across many concurrent sessions rather than individual query resource starvation.
  3. Warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse.
  4. Billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension.

Correct Answer: B

Explanation

A.

Query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. This choice does not explain the observed failure mechanism. 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. To address this, assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.

B.

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. The corresponding fix is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. A successful test should show that peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters; the reported setting is: a snowflake analyst supporting building event streams and supplier invoices at a facilities management group intends: assess supported multi-cluster warehouse configuration, scaling policy and workload par.

C.

Warehouse state is suspended, the scheduling role has usage permissions, and auto-resume is disabled for the chosen warehouse. This choice does not explain the observed failure mechanism. 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. To address this, assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.

D.

Billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. This choice does not explain the observed failure mechanism. 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. To address this, assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.

Question 702

The Snowflake data engineering team at a wholesale retailer plans to: Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. The issue affecting sales aggregates and supplier order tracking is: A large sort query takes longer as datasets grow and analysts blame partition pruning without checking memory pressure. Which finding best distinguishes this cause from other Snowflake failures?

  1. Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly.
  2. Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent.
  3. Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads.
  4. Execution profile shows large row fan-out and the correctness test fails even when extra compute is available.

Correct Answer: A

Explanation

A.

Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. The documented change is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. The acceptance check is whether a representative query reduces spill while preserving results and stays within cost limits; the reported setting is: the snowflake data engineering team at a wholesale retailer plans to: review join/sort memory needs, sql shape and approved warehouse capacity before changing clustering keys.

B.

Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Pruning efficiency depends on how filter predicates interact with micro-partition metadata. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

C.

Query history contains query IDs but service account and tagging conventions do not map runs to owning workloads. Query optimization governance needs observable workload attribution, not only raw credits. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

D.

Execution profile shows large row fan-out and the correctness test fails even when extra compute is available. Extra query compute cannot correct incorrect SQL semantics. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The better-matched action is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

Question 703

For assembly sensor events and warranty reports at an automotive parts manufacturer, an engineer diagnoses: An analyst who can read a sensitive table tries to grant another team permission without owning the object or having grant authority. The observation is: SHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The response is: Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Which principle best explains the decision?

  1. Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.
  2. Snowflake role authorization must cover both referenced data and chosen execution warehouse.
  3. Snowflake authorization can aggregate primary and enabled secondary role privileges.
  4. Network policies add source-network restrictions independent of SQL role grants.

Correct Answer: A

Explanation

A.

Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC. For assembly sensor events and warranty reports at an automotive parts manufacturer, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. To correct it, route the access change through a documented object owner or authorized security role with approval and minimal privileges. A successful test shows an approved user gains needed read access while an unauthorized analyst cannot grant it onward.

B.

Snowflake role authorization must cover both referenced data and chosen execution warehouse. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.

C.

Snowflake authorization can aggregate primary and enabled secondary role privileges. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.

D.

Network policies add source-network restrictions independent of SQL role grants. This choice does not explain the observed failure mechanism. For assembly sensor events and warranty reports at an automotive parts manufacturer, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.

Question 704

An operations review of cross-border shipment data and clearance events at a customs broker reports: A resource monitor suspends a production warehouse before a peak billing batch because the monitor threshold is lower than an agreed budget. The differentiating observation is: Resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. Which proposed fix and test pair most directly addresses the failure?

  1. Assign supported resource monitor coverage and alert thresholds to the intended warehouse resources and owners. — verification: A controlled spend threshold creates the expected notification for the targeted production warehouse.
  2. Enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs. — verification: After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully.
  3. Review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. — verification: A controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.
  4. 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.

Correct Answer: C

Explanation

A.

Assign supported resource monitor coverage and alert thresholds to the intended warehouse resources and owners. Verify that a controlled spend threshold creates the expected notification for the targeted production warehouse. This action and its verification do not address the identified failure together. For cross-border shipment data and clearance events at a customs broker, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The appropriate correction is to review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. Confirm that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

B.

Enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs. Verify that After an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully. This action and its verification do not address the identified failure together. For cross-border shipment data and clearance events at a customs broker, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The appropriate correction is to review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. Confirm that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

C.

Review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. Verify that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity. For cross-border shipment data and clearance events at a customs broker, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. Cost governance thresholds must account for workload criticality and the different effects of monitor actions.

D.

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 cross-border shipment data and clearance events at a customs broker, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The appropriate correction is to review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. Confirm that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

Question 705

The Snowflake data engineering case at an airport authority concerns passenger demand and ground service metrics. Problem: An ingestion view casts a missing JSON attribute as a required numeric value and aborts a transformation batch. Evidence: Sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. Which paired corrective action and verification is best?

  1. Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements. — verification: A three-element test array produces three authorized item rows with correct parent identifiers.
  2. Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. — verification: Each test customer has the expected independent ranking without unexpected cross-customer influence.
  3. Evaluate materialized view usage, maintenance and alternatives before retaining the precomputation. — verification: The revised approach meets report SLA at lower combined query and maintenance cost.
  4. Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. — verification: Valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

Correct Answer: D

Explanation

A.

Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements. Verify that 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 passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The appropriate correction is to use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Confirm that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

B.

Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. Verify that Each test customer has the expected independent ranking without unexpected cross-customer influence. Window functions depend on the declared partition and ordering semantics. For passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The appropriate correction is to use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Confirm that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

C.

Evaluate materialized view usage, maintenance and alternatives before retaining the precomputation. Verify that 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 passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The appropriate correction is to use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Confirm that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.

D.

Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Verify that valid numeric fields transform correctly and missing values are flagged without silently inventing numbers. For passenger demand and ground service metrics at an airport authority, 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.

Question 706

For application case metrics and protected citizen records at a benefits agency, an engineer diagnoses: A role investigation finds a user can access a table even after the primary active role lost its SELECT privilege. The observation is: Session diagnostics show an enabled secondary role still grants access to the table. The response is: Review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. Which principle best explains the decision?

  1. Database roles scope database privileges and are activated through account-role inheritance.
  2. Snowflake role authorization must cover both referenced data and chosen execution warehouse.
  3. Snowflake authorization can aggregate primary and enabled secondary role privileges.
  4. Row-level security requires correct identity-to-row entitlement logic.

Correct Answer: C

Explanation

A.

Database roles scope database privileges and are activated through account-role inheritance. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

B.

Snowflake role authorization must cover both referenced data and chosen execution warehouse. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

C.

Snowflake authorization can aggregate primary and enabled secondary role privileges. For application case metrics and protected citizen records at a benefits agency, session diagnostics show an enabled secondary role still grants access to the table. The documented change is to review primary and secondary active-role authorization and remove excess grants from the underlying responsible roles. A successful test shows the user loses unauthorized read access in all permitted role combinations while approved data remains accessible.

D.

Row-level security requires correct identity-to-row entitlement logic. This choice does not explain the observed failure mechanism. For application case metrics and protected citizen records at a benefits agency, session diagnostics show an enabled secondary role still grants access to the table. The controlling principle is that Snowflake authorization can aggregate primary and enabled secondary role privileges.

Question 707

In population program aggregates and access reviews at a public health agency, a validated correction is proposed: Create a supported reader-account collaboration path with scoped shared objects and approved consumer roles. It responds to: An external small business lacks a Snowflake account, and an operator proposes a reader account with broad internal table visibility. Choose the best measurable success criterion.

  1. An authorized consumer queries the shared object while no unmanaged full dataset export is required.
  2. The approved overlap statistic is available while individual participant records cannot be exported.
  3. The partner reads the intended report but cannot enumerate unrelated provider data.
  4. A staged app installs under approved necessary privileges and cannot query unrelated protected objects.

Correct Answer: C

Explanation

A.

An authorized consumer queries the shared object while no unmanaged full dataset export is required. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, reader-account role grants include schemas unrelated to the explicit shared reporting requirement. A confirming test shows that the partner reads the intended report but cannot enumerate unrelated provider data.

B.

The approved overlap statistic is available while individual participant records cannot be exported. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, reader-account role grants include schemas unrelated to the explicit shared reporting requirement. A confirming test shows that the partner reads the intended report but cannot enumerate unrelated provider data.

C.

The partner reads the intended report but cannot enumerate unrelated provider data. For population program aggregates and access reviews at a public health agency, reader-account role grants include schemas unrelated to the explicit shared reporting requirement. Reader accounts enable supported consumption without requiring a separate self-managed Snowflake account, but scope still matters. To correct it, create a supported reader-account collaboration path with scoped shared objects and approved consumer roles.

D.

A staged app installs under approved necessary privileges and cannot query unrelated protected objects. This choice does not explain the observed failure mechanism. For population program aggregates and access reviews at a public health agency, reader-account role grants include schemas unrelated to the explicit shared reporting requirement. A confirming test shows that the partner reads the intended report but cannot enumerate unrelated provider data.

Question 708

For content consumption analytics and rights reporting at a media publisher, Snowflake administrators supporting content consumption analytics and rights reporting 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. Use a reviewed external stage and scoped storage integration, then test approved unload output permissions.

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 content consumption analytics and rights reporting at a media publisher, new sessions use a different default role and warehouse from the earlier connector configuration. Instead, 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 content consumption analytics and rights reporting at a media publisher, 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. A confirming result should show 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 content consumption analytics and rights reporting at a media publisher, new sessions use a different default role and warehouse from the earlier connector configuration. Instead, set and audit approved client connection role, warehouse and namespace parameters with least privilege.

D.

Use a reviewed external stage and scoped storage integration, then test approved unload output permissions. Unloading data creates an outbound data-governance boundary that requires destination authorization. For content consumption analytics and rights reporting at a media publisher, new sessions use a different default role and warehouse from the earlier connector configuration. Instead, set and audit approved client connection role, warehouse and namespace parameters with least privilege.

Question 709

For factory telemetry and supplier quality dashboards at a manufacturing group, engineers propose: Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. Their incident states: An engineer grants a service external API integration unrestricted access when its stored procedure only requires one approved endpoint. What evidence should be verified before implementing the change?

  1. Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal.
  2. Resolved Git repository stage or branch reference differs from the approved tagged release.
  3. Integration inventory shows an allowed destination list much wider than the program's documented business requirement.
  4. The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing.

Correct Answer: C

Explanation

A.

Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. Snowflake connectivity spans internal roles and external provider identity policy. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. To address this, define a scoped supported API integration with reviewed network rules and controlled invocation privileges.

B.

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. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. To address this, define a scoped supported API integration with reviewed network rules and controlled invocation privileges.

C.

Integration inventory shows an allowed destination list much wider than the program's documented business requirement. External network and API integrations should constrain egress destinations and execution privileges. The corresponding fix is to define a scoped supported API integration with reviewed network rules and controlled invocation privileges. A successful test should show that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration; the reported setting is: for factory telemetry and supplier quality dashboards at a manufacturing group, engineers propose: define a scoped supported api integration with reviewed network rules and controlled invocation privileges.

D.

The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. To address this, define a scoped supported API integration with reviewed network rules and controlled invocation privileges.

Question 710

The meter ingestion and maintenance trend analysis team at a renewable energy utility records: A shared case table returns records for customers in unrelated business units under a narrowly scoped analyst role. Logs confirm: A controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The recommended action is: Correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. What underlying Snowflake solution principle applies?

  1. Row-level security requires correct identity-to-row entitlement logic.
  2. Dynamic masking can enforce column-value protection according to access context.
  3. Metadata tags provide governance value only when classification and lifecycle controls are reliable.
  4. Snowflake authentication mechanisms should match workload identity and credential lifecycle needs.

Correct Answer: A

Explanation

A.

Row-level security requires correct identity-to-row entitlement logic. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The documented change is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. A successful test shows positive and negative tenant tests return only authorized records for each role.

B.

Dynamic masking can enforce column-value protection according to access context. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The controlling principle is that row-level security requires correct identity-to-row entitlement logic.

C.

Metadata tags provide governance value only when classification and lifecycle controls are reliable. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The controlling principle is that row-level security requires correct identity-to-row entitlement logic.

D.

Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. This choice does not explain the observed failure mechanism. For meter ingestion and maintenance trend analysis at a renewable energy utility, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The controlling principle is that row-level security requires correct identity-to-row entitlement logic.

SnowPro Core COF-C03 Practice Tests