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

Question 770

An operations review of meter ingestion and maintenance trend analysis at a renewable energy utility reports: A team assumes every zero-copy clone immediately duplicates all source storage bytes and cancels a development test environment. The differentiating observation is: Storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. Which proposed fix and test pair most directly addresses the failure?

  1. Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. — verification: A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.
  2. Review supported table type, edition, retention settings and backup strategy against the required recovery objective. — verification: An allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated.
  3. Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. — verification: The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.
  4. Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. — verification: A sanctioned notebook cell completes using its documented compute environment with no extra account privileges.

Correct Answer: A

Explanation

A.

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

B.

Review supported table type, edition, retention settings and backup strategy against the required recovery objective. Verify that an allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated. This action and its verification do not address the identified failure together. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The appropriate correction is to assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Confirm that a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.

C.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Verify that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore. This action and its verification do not address the identified failure together. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The appropriate correction is to assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Confirm that a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.

D.

Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. Verify that a sanctioned notebook cell completes using its documented compute environment with no extra account privileges. This action and its verification do not address the identified failure together. For meter ingestion and maintenance trend analysis at a renewable energy utility, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. The appropriate correction is to assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. Confirm that a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.

Question 771

For asset maintenance logs and quality assurance reports at a water supplier, Snowflake administrators supporting asset maintenance logs and quality assurance reports report: A product team deletes a table and discovers the configured retention window is shorter than the approved rollback requirement. Their diagnostic record states: Table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Which corrective action is best supported by the evidence?

  1. Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.
  2. Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.
  3. Use supported clean room constraints and approved collaboration templates to restrict outputs and data access.
  4. Review supported table type, edition, retention settings and backup strategy against the required recovery objective.

Correct Answer: D

Explanation

A.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. For asset maintenance logs and quality assurance reports at a water supplier, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. For this incident, review supported table type, edition, retention settings and backup strategy against the required recovery objective.

B.

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 asset maintenance logs and quality assurance reports at a water supplier, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. For this incident, review supported table type, edition, retention settings and backup strategy against the required recovery objective.

C.

Use supported clean room constraints and approved collaboration templates to restrict outputs and data access. Clean rooms can support collaboration on sensitive data under controlled computations and output rules. For asset maintenance logs and quality assurance reports at a water supplier, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. For this incident, review supported table type, edition, retention settings and backup strategy against the required recovery objective.

D.

Review supported table type, edition, retention settings and backup strategy against the required recovery objective. For asset maintenance logs and quality assurance reports at a water supplier, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Time Travel provides configurable historical recovery only within supported object retention limits. Verify that an allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated.

Question 772

During a change review for booking data marts and occupancy forecasts at a hospitality chain, the team finds: A team assumes every zero-copy clone immediately duplicates all source storage bytes and cancels a development test environment. Investigation shows: Storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. 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. Choose an appropriate private listing and governed access workflow before publishing the data product.
  4. Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.

Correct Answer: D

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 booking data marts and occupancy forecasts at a hospitality chain, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. Instead, assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.

B.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. For booking data marts and occupancy forecasts at a hospitality chain, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. Instead, assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.

C.

Choose an appropriate private listing and governed access workflow before publishing the data product. Marketplace listing audience and share-grant design are independent governance controls. For booking data marts and occupancy forecasts at a hospitality chain, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. Instead, assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate.

D.

Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. For booking data marts and occupancy forecasts at a hospitality chain, storage reports show metadata-based cloned objects and shared micro-partitions before downstream changes. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. A confirming result should show that a governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.

Question 773

In cross-border shipment data and clearance events at a customs broker, a validated correction is proposed: Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. It responds to: An operations team assumes suspending its only virtual warehouse will erase permanent customer data and keeps compute running all night. Choose the best measurable success criterion.

  1. Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes.
  2. An idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.
  3. Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies.
  4. A controlled create, query and snapshot lifecycle test follows the documented ownership model without orphaned files.

Correct Answer: B

Explanation

A.

Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. A meaningful check confirms that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

B.

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

C.

Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. A meaningful check confirms that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

D.

A controlled create, query and snapshot lifecycle test follows the documented ownership model without orphaned files. This choice does not explain the observed failure mechanism. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. A meaningful check confirms that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.

Question 774

To correct this issue at an e-commerce marketplace involving shopping funnel events and merchant sales reporting: A resource monitor suspends a production warehouse before a peak billing batch because the monitor threshold is lower than an agreed budget. The team applies: Review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations. What outcome should close the incident?

  1. A controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.
  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. A query runs on the specified warehouse without granting access to unrelated compute resources.

Correct Answer: A

Explanation

A.

A controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity. For shopping funnel events and merchant sales reporting at an e-commerce marketplace, 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. The documented change is to review monitored credit quotas, notification versus suspension actions and critical workload windows with finance and operations.

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 shopping funnel events and merchant sales reporting at an e-commerce marketplace, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The outcome should establish that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

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 shopping funnel events and merchant sales reporting at an e-commerce marketplace, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The outcome should establish that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

D.

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, resource-monitor status shows an enforced suspend threshold reached during valid planned workload execution. The outcome should establish that a controlled budget test raises timely warnings while approved peak jobs retain documented operational continuity.

Question 775

During a change review for inventory traceability and shipping records at a pharmaceutical wholesaler, the team finds: An incremental MERGE processes several incoming updates for one target key without deduplicating the source and produces unstable outcomes. Investigation shows: Source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. What is the most appropriate next Snowflake action?

  1. Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.
  2. Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT.
  3. Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.
  4. Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

Correct Answer: D

Explanation

A.

Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. Window functions depend on the declared partition and ordering semantics. For inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. For this incident, deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

B.

Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior. For inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. For this incident, deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

C.

Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Snowflake persisted query results are reused only when the required consistency and context conditions are met. For inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. For this incident, deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

D.

Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE. For inventory traceability and shipping records at a pharmaceutical wholesaler, 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. Verify that a synthetic repeated key resolves to one correct target state and replay remains consistent.

Question 776

An operations review of care utilization metrics and de-identified clinical reporting at a hospital network reports: A monthly report scans the full sales history after its date predicate was rewritten as a formatted string expression. The differentiating observation is: Query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. Which proposed fix and test pair most directly addresses the failure?

  1. 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.
  2. 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.
  3. Correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics. — verification: A seeded order contributes its intended total once and query row expansion returns to expected levels.
  4. Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. — verification: The count respects row-level security and meets the approved performance target.

Correct Answer: B

Explanation

A.

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 care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. The appropriate correction is to restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Confirm that same expected rows return with fewer partitions scanned and lower measured query cost.

B.

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. For care utilization metrics and de-identified clinical reporting at a hospital network, 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.

C.

Correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics. Verify that a seeded order contributes its intended total once and query row expansion returns to expected levels. This action and its verification do not address the identified failure together. For care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. The appropriate correction is to restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Confirm that same expected rows return with fewer partitions scanned and lower measured query cost.

D.

Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Verify that the count respects row-level security and meets the approved performance target. This action and its verification do not address the identified failure together. For care utilization metrics and de-identified clinical reporting at a hospital network, query Profile shows much higher scanned micro-partition counts after the change with identical date filter intent. The appropriate correction is to restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Confirm that same expected rows return with fewer partitions scanned and lower measured query cost.

Question 777

To correct this issue at a public university involving student analytics and research-grant reporting: A large sort query takes longer as datasets grow and analysts blame partition pruning without checking memory pressure. The team applies: Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. What outcome should close the incident?

  1. A representative query reduces spill while preserving results and stays within cost limits.
  2. Same expected rows return with fewer partitions scanned and lower measured query cost.
  3. A seeded expensive query is assigned to the correct operational owner in cost reporting.
  4. A validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime.

Correct Answer: A

Explanation

A.

A representative query reduces spill while preserving results and stays within cost limits. For student analytics and research-grant reporting at a public university, 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 corresponding fix is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.

B.

Same expected rows return with fewer partitions scanned and lower measured query cost. Pruning efficiency depends on how filter predicates interact with micro-partition metadata. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. A meaningful check confirms that a representative query reduces spill while preserving results and stays within cost limits.

C.

A seeded expensive query is assigned to the correct operational owner in cost reporting. Query optimization governance needs observable workload attribution, not only raw credits. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. A meaningful check confirms that a representative query reduces spill while preserving results and stays within cost limits.

D.

A validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime. Extra query compute cannot correct incorrect SQL semantics. For student analytics and research-grant reporting at a public university, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. A meaningful check confirms that a representative query reduces spill while preserving results and stays within cost limits.

Question 778

Administrators at a pharmaceutical wholesaler plan: Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE. They are addressing the following problem in inventory traceability and shipping records: An incremental MERGE processes several incoming updates for one target key without deduplicating the source and produces unstable outcomes. Which test demonstrates resolution?

  1. A synthetic repeated key resolves to one correct target state and replay remains consistent.
  2. Each test customer has the expected independent ranking without unexpected cross-customer influence.
  3. Valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.
  4. An unchanged eligible repeated query demonstrates the expected cache behavior without stale results.

Correct Answer: A

Explanation

A.

A synthetic repeated key resolves to one correct target state and replay remains consistent. For inventory traceability and shipping records at a pharmaceutical wholesaler, 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. The documented change is to deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.

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 inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The outcome should establish that a synthetic repeated key resolves to one correct target state and replay remains consistent.

C.

Valid numeric fields transform correctly and missing values are flagged without silently inventing numbers. Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior. For inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The outcome should establish that a synthetic repeated key resolves to one correct target state and replay remains consistent.

D.

An unchanged eligible repeated query demonstrates the expected cache behavior without stale results. Snowflake persisted query results are reused only when the required consistency and context conditions are met. For inventory traceability and shipping records at a pharmaceutical wholesaler, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The outcome should establish that a synthetic repeated key resolves to one correct target state and replay remains consistent.

Question 779

The regulated batch tracking and delivery datasets team at a healthcare distributor records: A compliance team discovers unusual data access after its short-lived dashboard has rolled off the required audit interval. Logs confirm: A dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The recommended action is: Configure supported account usage reporting, collection and retention suitable for the approved audit period. What underlying Snowflake solution principle applies?

  1. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering.
  2. Operational dashboards and governed audit history have different retention and access requirements.
  3. Warehouse credit costs can accrue during idle running time separately from actual query work.
  4. Snowflake authorization can aggregate primary and enabled secondary role privileges.

Correct Answer: B

Explanation

A.

Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

B.

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

C.

Warehouse credit costs can accrue during idle running time separately from actual query work. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

D.

Snowflake authorization can aggregate primary and enabled secondary role privileges. This choice does not explain the observed failure mechanism. For regulated batch tracking and delivery datasets at a healthcare distributor, a dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. The controlling principle is that operational dashboards and governed audit history have different retention and access requirements.

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.

SnowPro Core COF-C03 Practice Tests