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!
Snowflake SnowPro Core COF-C03 Practice Test 5
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.
Correct Answer: A
Explanation
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.
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.
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.
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.
Question 41
A Snowflake analyst supporting project time-series and contract expenditure models at an engineering design firm intends: Inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness. The reported condition is: An internal document assistant retrieves old policy text after new documents were ingested into its source table. Identify the most decisive diagnostic record.
Correct Answer: B
Explanation
Generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. To address this, inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness.
Source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. A retrieval service needs its own indexed-data freshness and authorization controls. The corresponding fix is to inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness. A successful test should show that a controlled search locates the approved updated policy while respecting source access constraints.
Network egress and local memory limits dominate processing while Snowflake compute is underutilized. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. To address this, inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness.
A restricted test viewer can retrieve sensitive rows through the application that should not be in their authorized scope. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. To address this, inspect Cortex Search service ingestion, refresh and source selection, then validate indexed content access and freshness.
Question 42
For building event streams and supplier invoices at a facilities management group, Snowflake administrators supporting building event streams and supplier invoices report: A web analytics team doubles warehouse size repeatedly but interactive users still queue during simultaneous peak requests. Their diagnostic record states: Query history reports queuing across many concurrent sessions rather than individual query resource starvation. Which corrective action is best supported by the evidence?
Correct Answer: B
Explanation
Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Warehouse scale-up and multi-cluster scale-out address different performance bottlenecks. 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. The better-matched action is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.
Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. 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. Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity. A suitable check should show that peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters.
Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads. 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. The better-matched action is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.
Compare standard and specialized warehouse configurations against representative workload profiles and approved availability. Warehouse type should be chosen from actual supported workload requirements, not marketing terminology. 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. The better-matched action is to assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency.
Question 43
Administrators at an insurance company plan: Configure a supported secure data share with least privilege and document relevant region/account constraints. They are addressing the following problem in claims actuarial datasets and policy renewal models: A partner refuses a data collaboration because it assumes a Snowflake direct share must physically copy the entire source table. Which test demonstrates resolution?
Correct Answer: D
Explanation
The partner reads the intended report but cannot enumerate unrelated provider data. Reader accounts enable supported consumption without requiring a separate self-managed Snowflake account, but scope still matters. For claims actuarial datasets and policy renewal models at an insurance company, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. A confirming test shows that an authorized consumer queries the shared object while no unmanaged full dataset export is required.
The approved overlap statistic is available while individual participant records cannot be exported. Clean rooms can support collaboration on sensitive data under controlled computations and output rules. For claims actuarial datasets and policy renewal models at an insurance company, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. A confirming test shows that an authorized consumer queries the shared object while no unmanaged full dataset export is required.
A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. For claims actuarial datasets and policy renewal models at an insurance company, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. A confirming test shows that an authorized consumer queries the shared object while no unmanaged full dataset export is required.
An authorized consumer queries the shared object while no unmanaged full dataset export is required. For claims actuarial datasets and policy renewal models at an insurance company, collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. Snowflake secure sharing can provide governed access without traditional physical data copying. To correct it, configure a supported secure data share with least privilege and document relevant region/account constraints.
Question 44
The project time-series and contract expenditure models environment at an engineering design firm has an incident: A product team deletes a table and discovers the configured retention window is shorter than the approved rollback requirement. The difference-making observation is: Table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Choose the most defensible corrective response.
Correct Answer: D
Explanation
Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Instead, review supported table type, edition, retention settings and backup strategy against the required recovery objective.
Assess supported zero-copy cloning lifecycle and privilege controls instead of treating initial clone as a full physical duplicate. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Instead, review supported table type, edition, retention settings and backup strategy against the required recovery objective.
Create a supported reader-account collaboration path with scoped shared objects and approved consumer roles. This choice does not explain the observed failure mechanism. For project time-series and contract expenditure models at an engineering design firm, table metadata reports limited Time Travel retention and the requested point in history lies outside that window. Instead, review supported table type, edition, retention settings and backup strategy against the required recovery objective.
Review supported table type, edition, retention settings and backup strategy against the required recovery objective. For project time-series and contract expenditure models at an engineering design firm, 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. A confirming result should show that an allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated.
Question 45
The Snowflake data engineering case at a healthcare distributor concerns regulated batch tracking and delivery datasets. Problem: A compliance team discovers unusual data access after its short-lived dashboard has rolled off the required audit interval. Evidence: A dashboard retains fewer days than the agreed investigation window even though account-level usage/access views can support longer analysis. Which paired corrective action and verification is best?
Correct Answer: D
Explanation
Combine relevant account usage and serverless cost views with warehouse metrics for a complete workload accounting. Verify that a controlled cost report reconciles key service charges and supports assigned service ownership. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. 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 appropriate correction is to configure supported account usage reporting, collection and retention suitable for the approved audit period. Confirm that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.
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. Warehouse credit costs can accrue during idle running time separately from actual query work. 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 appropriate correction is to configure supported account usage reporting, collection and retention suitable for the approved audit period. Confirm that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.
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. Cost governance thresholds must account for workload criticality and the different effects of monitor actions. 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 appropriate correction is to configure supported account usage reporting, collection and retention suitable for the approved audit period. Confirm that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied.
Configure supported account usage reporting, collection and retention suitable for the approved audit period. Verify that an authorized reviewer retrieves a seeded access event within the retention window and unauthorized reviewers are denied. 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. Operational dashboards and governed audit history have different retention and access requirements.
Question 46
For cargo scans and berth utilization reports at a container port operator, engineers propose: Use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. Their incident states: A ranking query assigns the same top order to multiple customers because the window partition uses a shared region code. What evidence should be verified before implementing the change?
Correct Answer: C
Explanation
Source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. MERGE correctness requires an unambiguous source-to-target matching strategy. For cargo scans and berth utilization reports at a container port operator, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. The better-matched action is to use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.
A sample event contains multiple nested elements and the output row count stays one per parent regardless of item count. Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. For cargo scans and berth utilization reports at a container port operator, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. The better-matched action is to use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.
A seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. Window functions depend on the declared partition and ordering semantics. The documented change is to use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed. The acceptance check is whether each test customer has the expected independent ranking without unexpected cross-customer influence.
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. For cargo scans and berth utilization reports at a container port operator, a seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. The better-matched action is to use the correct business key in PARTITION BY with explicit deterministic ORDER BY where needed.
Question 47
The program attendance and donor outcome reports team at an education charity records: A team turns on query acceleration for a workload whose results are incorrect because of a many-to-many join explosion. Logs confirm: Execution profile shows large row fan-out and the correctness test fails even when extra compute is available. The recommended action is: Fix join semantics first and evaluate supported acceleration only after the query returns correct results. What underlying Snowflake solution principle applies?
Correct Answer: D
Explanation
Search optimization is designed for selective access patterns, not all-table analytic scans. This choice does not explain the observed failure mechanism. For program attendance and donor outcome reports at an education charity, execution profile shows large row fan-out and the correctness test fails even when extra compute is available. The controlling principle is that extra query compute cannot correct incorrect SQL semantics.
Materialized views trade faster repeated reads for storage and refresh maintenance. This choice does not explain the observed failure mechanism. For program attendance and donor outcome reports at an education charity, execution profile shows large row fan-out and the correctness test fails even when extra compute is available. The controlling principle is that extra query compute cannot correct incorrect SQL semantics.
Clustering keys are workload-specific optimizations and are not universally beneficial. This choice does not explain the observed failure mechanism. For program attendance and donor outcome reports at an education charity, execution profile shows large row fan-out and the correctness test fails even when extra compute is available. The controlling principle is that extra query compute cannot correct incorrect SQL semantics.
Extra query compute cannot correct incorrect SQL semantics. For program attendance and donor outcome reports at an education charity, execution profile shows large row fan-out and the correctness test fails even when extra compute is available. To correct it, fix join semantics first and evaluate supported acceleration only after the query returns correct results. A successful test shows a validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime.
Question 48
For loan servicing analytics and audit trails at a cooperative credit union, Snowflake administrators supporting loan servicing analytics and audit trails report: An analyst who can read a sensitive table tries to grant another team permission without owning the object or having grant authority. Their diagnostic record states: SHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Which corrective action is best supported by the evidence?
Correct Answer: C
Explanation
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 loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Instead, route the access change through a documented object owner or authorized security role with approval and minimal privileges.
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 loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Instead, route the access change through a documented object owner or authorized security role with approval and minimal privileges.
Route the access change through a documented object owner or authorized security role with approval and minimal privileges. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC. A confirming result should show that an approved user gains needed read access while an unauthorized analyst cannot grant it onward.
Use a supported governed OAuth or workload-identity integration with narrowly scoped role privileges and rotation policy. Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. For loan servicing analytics and audit trails at a cooperative credit union, sHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. Instead, route the access change through a documented object owner or authorized security role with approval and minimal privileges.
Question 49
During a change review for service ticket history and contracted usage billing at a managed service provider, the team finds: An analyst runs a Snowflake Notebook that accesses a table successfully in one session but fails in another because no valid execution warehouse is assigned. Investigation shows: Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. What is the most appropriate next Snowflake action?
Correct Answer: B
Explanation
Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Snowsight executes SQL within the selected session role, database, schema and warehouse context. For service ticket history and contracted usage billing at a managed service provider, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. To address this, configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.
Configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights. For service ticket history and contracted usage billing at a managed service provider, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. Interactive development tools still require supported execution compute and role context. The expected outcome is that a sanctioned notebook cell completes using its documented compute environment with no extra account privileges.
Set explicit intended database and schema context or fully qualify production-sensitive object references. Snowflake session context and object qualification determine how SQL names are resolved. For service ticket history and contracted usage billing at a managed service provider, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. To address this, configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.
Inspect query planning, object statistics, metadata and query shape before changing compute sizing. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. For service ticket history and contracted usage billing at a managed service provider, notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. To address this, configure an appropriate supported notebook execution environment and approved warehouse access rather than granting broad table rights.
Question 50
A Snowflake analyst supporting legal matter metrics and billing data marts at a regional law practice intends: Deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE. The reported condition is: An incremental MERGE processes several incoming updates for one target key without deduplicating the source and produces unstable outcomes. Identify the most decisive diagnostic record.
Correct Answer: A
Explanation
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. The acceptance check is whether a synthetic repeated key resolves to one correct target state and replay remains consistent.
A seeded dataset with two customers in the same region produces a shared rank sequence rather than customer-specific ranks. This choice does not explain the observed failure mechanism. For legal matter metrics and billing data marts at a regional law practice, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The better-matched action is to deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.
Sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. This choice does not explain the observed failure mechanism. For legal matter metrics and billing data marts at a regional law practice, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The better-matched action is to deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.
Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. This choice does not explain the observed failure mechanism. For legal matter metrics and billing data marts at a regional law practice, source validation shows duplicate business keys and the MERGE either errors or produces ambiguous update behavior. The better-matched action is to deduplicate or deterministically stage source changes at the intended target grain before the approved MERGE.
SnowPro Core COF-C03 Practice Tests
- Snowflake SnowPro Core COF-C03 Practice Test 3 - 10 Questions (Last Reviewed 14-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 4 - 10 Questions (Last Reviewed 13-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 5 - 10 Questions (Last Reviewed 12-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 6 - 10 Questions (Last Reviewed 11-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 7 - 10 Questions (Last Reviewed 10-Nov-2026)
