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 74
Question 730
For sales aggregates and supplier order tracking at a wholesale retailer, an engineer diagnoses: A large sort query takes longer as datasets grow and analysts blame partition pruning without checking memory pressure. The observation is: Query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The response is: Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. Which principle best explains the decision?
Correct Answer: D
Explanation
Pruning efficiency depends on how filter predicates interact with micro-partition metadata. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The controlling principle is that query Profile distinguishes memory spill from excessive table scans and pruning inefficiency.
Query optimization governance needs observable workload attribution, not only raw credits. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The controlling principle is that query Profile distinguishes memory spill from excessive table scans and pruning inefficiency.
Metadata-derived results cannot bypass filters needed for correct authorized query semantics. This choice does not explain the observed failure mechanism. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The controlling principle is that query Profile distinguishes memory spill from excessive table scans and pruning inefficiency.
Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For sales aggregates and supplier order tracking at a wholesale retailer, query Profile shows high local and remote spill even though the scan filters relevant partitions correctly. The documented change is to review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. A successful test shows a representative query reduces spill while preserving results and stays within cost limits.
Question 731
The verification logs and service risk scoring team at an identity verification firm records: A team creates a pipe with a valid COPY statement but new cloud files never load automatically. Logs confirm: The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The recommended action is: Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. What underlying Snowflake solution principle applies?
Correct Answer: B
Explanation
Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The controlling principle is that snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition.
Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. To correct it, configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. A successful test shows a newly uploaded sample file appears in the target table once without a manual COPY command.
Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The controlling principle is that snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition.
Snowflake connectivity spans internal roles and external provider identity policy. This choice does not explain the observed failure mechanism. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The controlling principle is that snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition.
Question 732
To correct this issue at a renewable energy utility involving meter ingestion and maintenance trend analysis: A batch load rejects new partner files after the upstream supplier adds a column not reflected in the target mapping. The team applies: Review compatible schema-evolution or explicit column-mapping behavior and add preflight validation rather than blindly skipping errors. What outcome should close the incident?
Correct Answer: D
Explanation
A test batch loads the intended amounts and customer IDs into their correct columns without silent shift. Snowflake load parsing depends on the staged file format matching the actual source encoding. For meter ingestion and maintenance trend analysis at a renewable energy utility, cOPY history shows parsing or column-matching errors on the newer file while older files load successfully. Verify that representative old and new files load into correct columns and invalid fields raise reviewed exceptions.
A controlled new document appears in the governed directory inventory and is retrievable by approved users. Directory metadata can require refresh or event configuration independent of files stored externally. For meter ingestion and maintenance trend analysis at a renewable energy utility, cOPY history shows parsing or column-matching errors on the newer file while older files load successfully. Verify that representative old and new files load into correct columns and invalid fields raise reviewed exceptions.
A newly uploaded sample file appears in the target table once without a manual COPY command. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. For meter ingestion and maintenance trend analysis at a renewable energy utility, cOPY history shows parsing or column-matching errors on the newer file while older files load successfully. Verify that representative old and new files load into correct columns and invalid fields raise reviewed exceptions.
Representative old and new files load into correct columns and invalid fields raise reviewed exceptions. For meter ingestion and maintenance trend analysis at a renewable energy utility, 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. To address this, review compatible schema-evolution or explicit column-mapping behavior and add preflight validation rather than blindly skipping errors.
Question 733
For passenger demand and ground service metrics at an airport authority, an engineer diagnoses: An ingestion view casts a missing JSON attribute as a required numeric value and aborts a transformation batch. The observation is: Sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The response is: Use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. Which principle best explains the decision?
Correct Answer: A
Explanation
Semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior. For passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The corresponding fix is to use a supported tolerant conversion and explicit data-quality exception handling while retaining the original VARIANT. A successful test shows valid numeric fields transform correctly and missing values are flagged without silently inventing numbers.
Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The controlling principle is that semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior.
Window functions depend on the declared partition and ordering semantics. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The controlling principle is that semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior.
Virtual warehouse local data cache behavior differs from the persisted query result cache. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, sample VARIANT objects omit the field for one partner and strict conversion raises a data-type error. The controlling principle is that semi-structured data can contain absent or variant-typed attributes requiring explicit conversion behavior.
Question 734
A Snowflake analyst supporting care utilization metrics and de-identified clinical reporting at a hospital network intends: Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. The reported condition is: A team stores financial audit records in a transient table while its policy expects Fail-safe-based disaster recovery behavior. Identify the most decisive diagnostic record.
Correct Answer: B
Explanation
Governance review finds external catalog or metadata ownership assumptions do not match the configured Iceberg management mode. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The better-matched action is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences.
Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. Permanent, transient and temporary tables have different lifecycle and data protection characteristics. The documented change is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. The acceptance check is whether a documented recovery rehearsal covers the approved retention window without assuming transient Fail-safe; the reported setting is: a snowflake analyst supporting care utilization metrics and de-identified clinical reporting at a hospital network intends: select a suitable permanent-table retention and disaster-recovery design after re.
The second session cannot resolve the temporary object although the creator session could query it earlier. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The better-matched action is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences.
Source table query includes the new policy but the search service's index freshness and source configuration do not reflect it. This choice does not explain the observed failure mechanism. For care utilization metrics and de-identified clinical reporting at a hospital network, object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. The better-matched action is to select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences.
Question 735
For claims actuarial datasets and policy renewal models at an insurance company, Snowflake administrators supporting claims actuarial datasets and policy renewal models report: A partner refuses a data collaboration because it assumes a Snowflake direct share must physically copy the entire source table. Their diagnostic record states: Collaboration design includes a same-region direct share and governed consumer read access without a bulk export request. Which corrective action is best supported by the evidence?
Correct Answer: C
Explanation
Create a supported reader-account collaboration path with scoped shared objects and approved consumer roles. 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. For this incident, configure a supported secure data share with least privilege and document relevant region/account constraints.
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 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. For this incident, configure a supported secure data share with least privilege and document relevant region/account constraints.
Configure a supported secure data share with least privilege and document relevant region/account constraints. 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. Verify that an authorized consumer queries the shared object while no unmanaged full dataset export is required.
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 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. For this incident, configure a supported secure data share with least privilege and document relevant region/account constraints.
Question 736
At a hospitality chain, a Snowflake analyst supporting booking data marts and occupancy forecasts finds: A shared case table returns records for customers in unrelated business units under a narrowly scoped analyst role. They confirm: A controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. Select the action and acceptance-test pair best matched to these facts.
Correct Answer: A
Explanation
Correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. Verify that Positive and negative tenant tests return only authorized records for each role. For booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. Row-level security requires correct identity-to-row entitlement logic.
Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Verify that Restricted roles receive redacted test values and a specifically authorized role receives only approved detail. Dynamic masking can enforce column-value protection according to access context. For booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The appropriate correction is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. Confirm that positive and negative tenant tests return only authorized records for each role.
Apply supported sensitive-data classification and governed object tags with review and ownership of findings. Verify that a seeded new sensitive column is detected, labeled appropriately and included in the audit inventory. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The appropriate correction is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. Confirm that positive and negative tenant tests return only authorized records for each role.
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 booking data marts and occupancy forecasts at a hospitality chain, a controlled session can query another unit's case rows because row access policy predicates do not use the correct tenant mapping. The appropriate correction is to correct and test a documented row access policy driven by authoritative entitlement mapping without using a broad global exception. Confirm that positive and negative tenant tests return only authorized records for each role.
Question 737
A Snowflake analyst supporting instrument results and governed case metadata at a medical testing laboratory intends: Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. The reported condition is: A team publishes a sensitive metric without being able to show which raw tables and transformations contributed to it. Identify the most decisive diagnostic record.
Correct Answer: B
Explanation
Data profiling finds untagged sensitive fields and a generic table tag provides no reliable column 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. To address this, enable appropriate supported lineage collection and document governed source-to-target transformation ownership.
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. The corresponding fix is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership. A successful test should show that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access; the reported setting is: a snowflake analyst supporting instrument results and governed case metadata at a medical testing laboratory intends: enable appropriate supported lineage collection and document governed source-to-target .
A low-privilege test session selects cleartext identifiers because no applicable masking policy protects the column. 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. To address this, enable appropriate supported lineage collection and document governed source-to-target transformation ownership.
GRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. 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. To address this, enable appropriate supported lineage collection and document governed source-to-target transformation ownership.
Question 738
The Snowflake data engineering case at a publishing group concerns subscription events and finance reporting. Problem: A transformation query spills heavily on a small warehouse while designers propose multi-cluster scale-out to shorten that one query. Evidence: Query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. Which paired corrective action and verification is best?
Correct Answer: B
Explanation
Assess supported multi-cluster warehouse configuration, scaling policy and workload partitioning under realistic concurrency. Verify that Peak multiuser queries complete within agreed wait times without unnecessary idle warehouse clusters. Multi-cluster warehouses address concurrency pressure differently from single-query compute capacity. For subscription events and finance reporting at a publishing group, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The appropriate correction is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Confirm that the same query meets its resource target with less spill while total cost remains within budget.
Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Verify that the same query meets its resource target with less spill while total cost remains within budget. For subscription events and finance reporting at a publishing group, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. Warehouse scale-up and multi-cluster scale-out address different performance bottlenecks.
Review warehouse auto-resume and approved execution role settings without disabling cost-saving auto-suspend entirely. Verify that a scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity. Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads. For subscription events and finance reporting at a publishing group, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The appropriate correction is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Confirm that the same query meets its resource target with less spill while total cost remains within budget.
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. Interactive development tools still require supported execution compute and role context. For subscription events and finance reporting at a publishing group, query Profile shows the single execution spends substantial time spilling and has no queue from concurrent sessions. The appropriate correction is to benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. Confirm that the same query meets its resource target with less spill while total cost remains within budget.
Question 739
Administrators at an online retail chain plan: Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. They are addressing the following problem in return history and customer lifetime models: A data engineer executes a destructive administrative statement from a worksheet without noticing it inherited an elevated role. Which test demonstrates resolution?
Correct Answer: D
Explanation
A sanctioned notebook cell completes using its documented compute environment with no extra account privileges. Interactive development tools still require supported execution compute and role context. For return history and customer lifetime models at an online retail chain, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. A confirming test shows that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.
Both approved client sessions resolve the same intended table without using elevated roles. Snowflake session context and object qualification determine how SQL names are resolved. For return history and customer lifetime models at an online retail chain, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. A confirming test shows that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.
A scheduled test query resumes the warehouse, succeeds and the warehouse later suspends again after inactivity. Warehouse auto-suspend and auto-resume must be configured together for intermittent workloads. For return history and customer lifetime models at an online retail chain, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. A confirming test shows that the permitted operation succeeds under the correct role and an unrelated privileged action is denied.
The permitted operation succeeds under the correct role and an unrelated privileged action is denied. For return history and customer lifetime models at an online retail chain, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. Snowsight executes SQL within the selected session role, database, schema and warehouse context. To correct it, change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL.
Question 740
An operations review of reservation changes and partner analytics at a travel booking platform reports: A team grants usage on a database but expects that grant to permit a reporting role to read all tables inside a schema. The differentiating observation is: The role can resolve the database name but lacks schema usage and SELECT privileges on the required table. Which proposed fix and test pair most directly addresses the failure?
Correct Answer: C
Explanation
Apply documented minimum required pipe ownership or operating privileges while retaining separate target-table grants. Verify that the service role performs the intended pipe operation but remains unable to administer unrelated objects. This action and its verification do not address the identified failure together. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. The appropriate correction is to grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. Confirm that an authorized report reads the target table and cannot access an unrelated schema.
Choose an appropriate stored procedure or orchestrated task for procedural work and reserve UDFs for supported computation. Verify that a test execution completes the controlled multi-step process with an auditable outcome and no unsupported UDF side effects. This action and its verification do not address the identified failure together. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. The appropriate correction is to grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. Confirm that an authorized report reads the target table and cannot access an unrelated schema.
Grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. Verify that an authorized report reads the target table and cannot access an unrelated schema. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. Object visibility and data access depend on privileges at multiple securable-object hierarchy levels.
Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. Verify that the permitted operation succeeds under the correct role and an unrelated privileged action is denied. This action and its verification do not address the identified failure together. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. The appropriate correction is to grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. Confirm that an authorized report reads the target table and cannot access an unrelated schema.
SnowPro Core COF-C03 Practice Tests
- Snowflake SnowPro Core COF-C03 Practice Test 72 - 10 Questions (Last Reviewed 02-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 73 - 10 Questions (Last Reviewed 01-Nov-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 74 - 10 Questions (Last Reviewed 31-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 75 - 10 Questions (Last Reviewed 30-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 76 - 10 Questions (Last Reviewed 29-Oct-2026)
