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

Question 30

The Snowflake data engineering case at a renewable energy utility concerns meter ingestion and maintenance trend analysis. Problem: An account team promises an edition-dependent governance control to auditors without checking the account's subscribed Snowflake edition. Evidence: Feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. Which paired corrective action and verification is best?

  1. Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. — verification: An idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.
  2. Inspect query planning, object statistics, metadata and query shape before changing compute sizing. — verification: A representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.
  3. Verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. — verification: A controlled account check demonstrates that the chosen production configuration actually enforces the documented control.
  4. Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. — verification: Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies.

Correct Answer: C

Explanation

A.

Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Verify that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows. Snowflake separates independently scalable query compute from persistent managed table storage. For meter ingestion and maintenance trend analysis at a renewable energy utility, feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. The appropriate correction is to verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. Confirm that a controlled account check demonstrates that the chosen production configuration actually enforces the documented control.

B.

Inspect query planning, object statistics, metadata and query shape before changing compute sizing. Verify that a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. For meter ingestion and maintenance trend analysis at a renewable energy utility, feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. The appropriate correction is to verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. Confirm that a controlled account check demonstrates that the chosen production configuration actually enforces the documented control.

C.

Verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. Verify that a controlled account check demonstrates that the chosen production configuration actually enforces the documented control. For meter ingestion and maintenance trend analysis at a renewable energy utility, feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. Snowflake editions differ in available advanced security and resilience capabilities.

D.

Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. Verify that Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies. Independent virtual warehouses support workload isolation over shared centralized data. For meter ingestion and maintenance trend analysis at a renewable energy utility, feature evaluation indicates the required control is not available at the current account edition and its trial behavior differs from production. The appropriate correction is to verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. Confirm that a controlled account check demonstrates that the chosen production configuration actually enforces the documented control.

Question 31

Administrators at a regional transit agency plan: Introduce governed query tags and accountable job identity mapping with account usage reporting. They are addressing the following problem in fleet schedules and passenger ridership datasets: A FinOps team sees high daily query spend but cannot attribute it to the dashboard or scheduled transform responsible. Which test demonstrates resolution?

  1. Peak reports complete within queue wait targets while isolated query execution time stays stable.
  2. A representative query reduces spill while preserving results and stays within cost limits.
  3. A seeded expensive query is assigned to the correct operational owner in cost reporting.
  4. A seeded order contributes its intended total once and query row expansion returns to expected levels.

Correct Answer: C

Explanation

A.

Peak reports complete within queue wait targets while isolated query execution time stays stable. Total query latency includes queue time as well as execution and compilation. 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. A confirming test shows that a seeded expensive query is assigned to the correct operational owner in cost reporting.

B.

A representative query reduces spill while preserving results and stays within cost limits. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. 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. A confirming test shows that a seeded expensive query is assigned to the correct operational owner in cost reporting.

C.

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. To correct it, introduce governed query tags and accountable job identity mapping with account usage reporting.

D.

A seeded order contributes its intended total once and query row expansion returns to expected levels. Join cardinality affects both query cost and semantic result correctness. 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. A confirming test shows that a seeded expensive query is assigned to the correct operational owner in cost reporting.

Question 32

The fleet schedules and passenger ridership datasets environment at a regional transit agency has an incident: An application creates an intermediate dataset as a temporary table then expects another session to retrieve it the following morning. The difference-making observation is: The second session cannot resolve the temporary object although the creator session could query it earlier. Choose the most defensible corrective response.

  1. Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production.
  2. Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences.
  3. Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.
  4. Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

Correct Answer: D

Explanation

A.

Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production. This choice does not explain the observed failure mechanism. For fleet schedules and passenger ridership datasets at a regional transit agency, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

B.

Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. This choice does not explain the observed failure mechanism. For fleet schedules and passenger ridership datasets at a regional transit agency, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

C.

Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. This choice does not explain the observed failure mechanism. For fleet schedules and passenger ridership datasets at a regional transit agency, the second session cannot resolve the temporary object although the creator session could query it earlier. Instead, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

D.

Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. For fleet schedules and passenger ridership datasets at a regional transit agency, the second session cannot resolve the temporary object although the creator session could query it earlier. Temporary tables are scoped to sessions and should not be treated as persistent shared datasets. A confirming result should show that a new authorized session retrieves the intended prepared dataset after the original session ends.

Question 33

For tenant repair requests and funding reporting at a nonprofit housing network, Snowflake administrators supporting tenant repair requests and funding reporting report: A marketing dataset stores several item entries in a VARIANT array but a report treats the entire array as one item. Their diagnostic record states: A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. Which corrective action is best supported by the evidence?

  1. Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT.
  2. Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.
  3. Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies.
  4. Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements.

Correct Answer: D

Explanation

A.

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 tenant repair requests and funding reporting at a nonprofit housing network, a sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. To address this, use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements.

B.

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 tenant repair requests and funding reporting at a nonprofit housing network, a sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. To address this, use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements.

C.

Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. For tenant repair requests and funding reporting at a nonprofit housing network, a sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. To address this, use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements.

D.

Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements. For tenant repair requests and funding reporting at a nonprofit housing network, 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. The expected outcome is that a three-element test array produces three authorized item rows with correct parent identifiers.

Question 34

For asset maintenance logs and quality assurance reports at a water supplier, engineers propose: Use a reviewed external stage and scoped storage integration, then test approved unload output permissions. Their incident states: An analyst exports a filtered customer dataset with COPY INTO location but the chosen stage points at an unauthorized storage prefix. What evidence should be verified before implementing the change?

  1. Configuration review finds a plaintext storage secret stored in a copied deployment script.
  2. Resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary.
  3. Directory table metadata is stale relative to the cloud object listing after an external upload.
  4. COPY history shows parsing or column-matching errors on the newer file while older files load successfully.

Correct Answer: B

Explanation

A.

Configuration review finds a plaintext storage secret stored in a copied deployment script. Storage integrations provide a governed trust boundary for external staged data. For asset maintenance logs and quality assurance reports at a water supplier, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. The better-matched action is to use a reviewed external stage and scoped storage integration, then test approved unload output permissions.

B.

Resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. Unloading data creates an outbound data-governance boundary that requires destination authorization. The documented change is to use a reviewed external stage and scoped storage integration, then test approved unload output permissions. The acceptance check is whether a seeded export appears only in the authorized destination and a test unauthorized prefix is denied.

C.

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. For asset maintenance logs and quality assurance reports at a water supplier, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. The better-matched action is to use a reviewed external stage and scoped storage integration, then test approved unload output permissions.

D.

COPY history shows parsing or column-matching errors on the newer file while older files load successfully. Bulk ingestion correctness requires explicit handling of changing file schema and COPY options. For asset maintenance logs and quality assurance reports at a water supplier, resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. The better-matched action is to use a reviewed external stage and scoped storage integration, then test approved unload output permissions.

Question 35

In instrument results and governed case metadata at a medical testing laboratory, a validated correction is proposed: Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. It responds to: A team publishes a sensitive metric without being able to show which raw tables and transformations contributed to it. Choose the best measurable success criterion.

  1. A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory.
  2. An auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.
  3. Restricted roles receive redacted test values and a specifically authorized role receives only approved detail.
  4. Positive and negative tenant tests return only authorized records for each role.

Correct Answer: B

Explanation

A.

A seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. This choice does not explain the observed failure mechanism. 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. A confirming test shows that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

B.

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. To correct it, enable appropriate supported lineage collection and document governed source-to-target transformation ownership.

C.

Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. This choice does not explain the observed failure mechanism. For 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. A confirming test shows that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

D.

Positive and negative tenant tests return only authorized records for each role. This choice does not explain the observed failure mechanism. 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. A confirming test shows that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

Question 36

To correct this issue at an airport authority involving passenger demand and ground service metrics: A query runs quickly in isolation but takes minutes during the busiest hour, and engineers rewrite SQL unnecessarily. The team applies: Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. What outcome should close the incident?

  1. A seeded expensive query is assigned to the correct operational owner in cost reporting.
  2. A representative query reduces spill while preserving results and stays within cost limits.
  3. Peak reports complete within queue wait targets while isolated query execution time stays stable.
  4. Same expected rows return with fewer partitions scanned and lower measured query cost.

Correct Answer: C

Explanation

A.

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 passenger demand and ground service metrics at an airport authority, query History separates long queued time from short actual execution and shows many simultaneous sessions. Verify that peak reports complete within queue wait targets while isolated query execution time stays stable.

B.

A representative query reduces spill while preserving results and stays within cost limits. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For passenger demand and ground service metrics at an airport authority, query History separates long queued time from short actual execution and shows many simultaneous sessions. Verify that peak reports complete within queue wait targets while isolated query execution time stays stable.

C.

Peak reports complete within queue wait targets while isolated query execution time stays stable. For passenger demand and ground service metrics at an airport authority, query History separates long queued time from short actual execution and shows many simultaneous sessions. Total query latency includes queue time as well as execution and compilation. To address this, tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL.

D.

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 passenger demand and ground service metrics at an airport authority, query History separates long queued time from short actual execution and shows many simultaneous sessions. Verify that peak reports complete within queue wait targets while isolated query execution time stays stable.

Question 37

At a pharmaceutical wholesaler, a Snowflake analyst supporting inventory traceability and shipping records finds: A developer adds a clustering key to a tiny lookup table that is already fully scanned quickly and increases maintenance cost. They confirm: Before/after tests show no material performance improvement while reclustering overhead appears in metering. Select the action and acceptance-test pair best matched to these facts.

  1. 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.
  2. Choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. — verification: The aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.
  3. Fix join semantics first and evaluate supported acceleration only after the query returns correct results. — verification: A validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime.
  4. Remove unnecessary clustering optimization and focus only on evidence-backed large-table access patterns. — verification: The lookup remains within SLA and extraneous clustering maintenance costs disappear.

Correct Answer: D

Explanation

A.

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 inventory traceability and shipping records at a pharmaceutical wholesaler, before/after tests show no material performance improvement while reclustering overhead appears in metering. The appropriate correction is to remove unnecessary clustering optimization and focus only on evidence-backed large-table access patterns. Confirm that the lookup remains within SLA and extraneous clustering maintenance costs disappear.

B.

Choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. Verify that the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense. Search optimization is designed for selective access patterns, not all-table analytic scans. For inventory traceability and shipping records at a pharmaceutical wholesaler, before/after tests show no material performance improvement while reclustering overhead appears in metering. The appropriate correction is to remove unnecessary clustering optimization and focus only on evidence-backed large-table access patterns. Confirm that the lookup remains within SLA and extraneous clustering maintenance costs disappear.

C.

Fix join semantics first and evaluate supported acceleration only after the query returns correct results. Verify that a validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime. Extra query compute cannot correct incorrect SQL semantics. For inventory traceability and shipping records at a pharmaceutical wholesaler, before/after tests show no material performance improvement while reclustering overhead appears in metering. The appropriate correction is to remove unnecessary clustering optimization and focus only on evidence-backed large-table access patterns. Confirm that the lookup remains within SLA and extraneous clustering maintenance costs disappear.

D.

Remove unnecessary clustering optimization and focus only on evidence-backed large-table access patterns. Verify that the lookup remains within SLA and extraneous clustering maintenance costs disappear. For inventory traceability and shipping records at a pharmaceutical wholesaler, before/after tests show no material performance improvement while reclustering overhead appears in metering. Clustering keys are workload-specific optimizations and are not universally beneficial.

Question 38

The factory telemetry and supplier quality dashboards environment at a manufacturing group has an incident: A dashboard experiences long compilation times but engineers keep increasing its warehouse size without changing query planning. The difference-making observation is: Query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Choose the most defensible corrective response.

  1. Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries.
  2. Inspect query planning, object statistics, metadata and query shape before changing compute sizing.
  3. Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely.
  4. Verify official feature and edition availability and select an approved edition or alternative control before making compliance claims.

Correct Answer: B

Explanation

A.

Partition workload compute into appropriately governed warehouses and compare execution and cost before routing critical queries. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The better-matched action is to inspect query planning, object statistics, metadata and query shape before changing compute sizing.

B.

Inspect query planning, object statistics, metadata and query shape before changing compute sizing. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. A suitable check should show that a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.

C.

Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The better-matched action is to inspect query planning, object statistics, metadata and query shape before changing compute sizing.

D.

Verify official feature and edition availability and select an approved edition or alternative control before making compliance claims. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. The better-matched action is to inspect query planning, object statistics, metadata and query shape before changing compute sizing.

Question 39

The Snowflake data engineering team at a pharmaceutical wholesaler investigating inventory traceability and shipping records notes: A reporting view exposes full national identifiers to a broad analyst role despite a requirement to show only redacted values. Evidence: A low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. They plan: Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Which technical principle justifies the correction?

  1. Row-level security requires correct identity-to-row entitlement logic.
  2. Metadata tags provide governance value only when classification and lifecycle controls are reliable.
  3. Data lineage supports governed interpretation and change impact beyond final result values.
  4. Dynamic masking can enforce column-value protection according to access context.

Correct Answer: D

Explanation

A.

Row-level security requires correct identity-to-row entitlement logic. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. The controlling principle is that dynamic masking can enforce column-value protection according to access context.

B.

Metadata tags provide governance value only when classification and lifecycle controls are reliable. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. The controlling principle is that dynamic masking can enforce column-value protection according to access context.

C.

Data lineage supports governed interpretation and change impact beyond final result values. This choice does not explain the observed failure mechanism. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. The controlling principle is that dynamic masking can enforce column-value protection according to access context.

D.

Dynamic masking can enforce column-value protection according to access context. For inventory traceability and shipping records at a pharmaceutical wholesaler, a low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. To correct it, attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. A successful test shows restricted roles receive redacted test values and a specifically authorized role receives only approved detail.

Question 40

At an airport authority, a Snowflake analyst supporting passenger demand and ground service metrics finds: An administrator tightens allowed client network ranges and unintentionally blocks the production ingestion service. They confirm: Login history contains a network-policy denial for the service's documented egress address after the change. Select the action and acceptance-test pair best matched to these facts.

  1. Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. — verification: A permitted service connection works from its approved egress address while an unauthorized source remains denied.
  2. 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.
  3. 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.
  4. Grant the database role to an appropriate account role and grant that account role to approved users. — verification: The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

Correct Answer: A

Explanation

A.

Reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Verify that a permitted service connection works from its approved egress address while an unauthorized source remains denied. For passenger demand and ground service metrics at an airport authority, login history contains a network-policy denial for the service's documented egress address after the change. Network policies add source-network restrictions independent of SQL role grants.

B.

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. Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. For passenger demand and ground service metrics at an airport authority, login history contains a network-policy denial for the service's documented egress address after the change. The appropriate correction is to reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Confirm that a permitted service connection works from its approved egress address while an unauthorized source remains denied.

C.

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. Snowflake role authorization must cover both referenced data and chosen execution warehouse. For passenger demand and ground service metrics at an airport authority, login history contains a network-policy denial for the service's documented egress address after the change. The appropriate correction is to reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Confirm that a permitted service connection works from its approved egress address while an unauthorized source remains denied.

D.

Grant the database role to an appropriate account role and grant that account role to approved users. Verify that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access. Database roles scope database privileges and are activated through account-role inheritance. For passenger demand and ground service metrics at an airport authority, login history contains a network-policy denial for the service's documented egress address after the change. The appropriate correction is to reconcile supported account or user network policies with verified service egress networks and stage a least-privilege rollout. Confirm that a permitted service connection works from its approved egress address while an unauthorized source remains denied.

SnowPro Core COF-C03 Practice Tests