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 23
Question 220
During a change review for case document metadata and restricted reporting at a legal services organization, the team finds: A sales dashboard duplicates order totals after adding an event table with several events per order. Investigation shows: Query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. What is the most appropriate next Snowflake action?
Correct Answer: C
Explanation
Restore a selective supported date-range predicate and compare query profile pruning under reproducible data. Pruning efficiency depends on how filter predicates interact with micro-partition metadata. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.
Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.
Correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Join cardinality affects both query cost and semantic result correctness. A confirming result should show that a seeded order contributes its intended total once and query row expansion returns to expected levels.
Introduce governed query tags and accountable job identity mapping with account usage reporting. Query optimization governance needs observable workload attribution, not only raw credits. For case document metadata and restricted reporting at a legal services organization, query Profile shows a sharp row explosion at a join and validation counts exceed known unique order identifiers. Instead, correct join cardinality or pre-aggregate event data at the required grain before publishing financial metrics.
Question 221
The case document metadata and restricted reporting team at a legal services organization records: A data engineer executes a destructive administrative statement from a worksheet without noticing it inherited an elevated role. Logs confirm: Worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The recommended action is: Change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. What underlying Snowflake solution principle applies?
Correct Answer: D
Explanation
Interactive development tools still require supported execution compute and role context. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The controlling principle is that snowsight executes SQL within the selected session role, database, schema and warehouse context.
Snowflake session context and object qualification determine how SQL names are resolved. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The controlling principle is that snowsight executes SQL within the selected session role, database, schema and warehouse context.
A successful client connection does not establish that the selected account context is correct. This choice does not explain the observed failure mechanism. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The controlling principle is that snowsight executes SQL within the selected session role, database, schema and warehouse context.
Snowsight executes SQL within the selected session role, database, schema and warehouse context. For case document metadata and restricted reporting at a legal services organization, worksheet context displays ACCOUNTADMIN while the approved task requires a narrower functional role and the same SQL works with that role. The corresponding fix is to change the active worksheet role to a least-privilege approved role and validate session context before executing administrative SQL. A successful test shows the permitted operation succeeds under the correct role and an unrelated privileged action is denied.
Question 222
The Snowflake data engineering team at a regional bank investigating customer risk analytics and branch transaction reports notes: An analyst enables search optimization on a huge table to speed a report that aggregates most records every night. Evidence: Query Profile shows broad scans with few selective equality or point lookup predicates. They plan: Choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. Which technical principle justifies the correction?
Correct Answer: C
Explanation
Clustering keys are workload-specific optimizations and are not universally beneficial. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.
Extra query compute cannot correct incorrect SQL semantics. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.
Search optimization is designed for selective access patterns, not all-table analytic scans. For customer risk analytics and branch transaction reports at a regional bank, query Profile shows broad scans with few selective equality or point lookup predicates. The documented change is to choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. A successful test shows the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.
Metadata-derived results cannot bypass filters needed for correct authorized query semantics. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, query Profile shows broad scans with few selective equality or point lookup predicates. The controlling principle is that search optimization is designed for selective access patterns, not all-table analytic scans.
Question 223
Administrators at a payments processor plan: Grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants. They are addressing the following problem in settlement reconciliation and fraud-monitoring datasets: A reporting analyst receives SELECT on a table but cannot run an authorized query using the team's warehouse. Which test demonstrates resolution?
Correct Answer: B
Explanation
The user loses unauthorized read access in all permitted role combinations while approved data remains accessible. Snowflake authorization can aggregate primary and enabled secondary role privileges. For settlement reconciliation and fraud-monitoring datasets at a payments processor, gRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. A confirming test shows that a query runs on the specified warehouse without granting access to unrelated compute resources.
A query runs on the specified warehouse without granting access to unrelated compute resources. For settlement reconciliation and fraud-monitoring datasets at a payments processor, gRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. Snowflake role authorization must cover both referenced data and chosen execution warehouse. To correct it, grant the minimal warehouse usage privilege to the approved functional role while preserving object-level data grants.
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 settlement reconciliation and fraud-monitoring datasets at a payments processor, gRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. A confirming test shows that a query runs on the specified warehouse without granting access to unrelated compute resources.
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 settlement reconciliation and fraud-monitoring datasets at a payments processor, gRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. A confirming test shows that a query runs on the specified warehouse without granting access to unrelated compute resources.
Question 224
The customer risk analytics and branch transaction reports team at a regional bank records: A dynamically refreshed reporting dataset is consistently older than the declared freshness target even though source tables update. Logs confirm: Refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. The recommended action is: Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. What underlying Snowflake solution principle applies?
Correct Answer: B
Explanation
Task orchestration must represent data dependencies rather than assuming independent schedules stay aligned. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. The controlling principle is that dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute.
Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. To address this, inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. A successful test shows a seeded data change appears in the published table within the approved achievable freshness window.
Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. The controlling principle is that dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute.
Bulk ingestion correctness requires explicit handling of changing file schema and COPY options. This choice does not explain the observed failure mechanism. For customer risk analytics and branch transaction reports at a regional bank, refresh history reports lag or scheduling constraints and downstream refresh dependencies exceed the configured target. The controlling principle is that dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute.
Question 225
The Snowflake data engineering team at a cooperative credit union investigating loan servicing analytics and audit trails notes: An analyst who can read a sensitive table tries to grant another team permission without owning the object or having grant authority. Evidence: SHOW GRANTS shows SELECT and USAGE but neither OWNERSHIP nor an appropriate MANAGE GRANTS authorization. They plan: Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Which technical principle justifies the correction?
Correct Answer: D
Explanation
Snowflake role authorization must cover both referenced data and chosen execution warehouse. This choice does not explain the observed failure mechanism. 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. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.
Snowflake authorization can aggregate primary and enabled secondary role privileges. This choice does not explain the observed failure mechanism. 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. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.
Snowflake authentication mechanisms should match workload identity and credential lifecycle needs. This choice does not explain the observed failure mechanism. 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. The controlling principle is that reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC.
Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC. 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. The corresponding fix is to route the access change through a documented object owner or authorized security role with approval and minimal privileges. A successful test shows an approved user gains needed read access while an unauthorized analyst cannot grant it onward.
Question 226
Administrators at a pension administrator plan: Review the Native App package, application roles, permission requests and version lifecycle with the consumer. They are addressing the following problem in member analytics and long-term audit records: A provider distributes a Snowflake Native App requiring broad privileges that have not been justified for its analytics function. Which test demonstrates resolution?
Correct Answer: C
Explanation
Only authorized pilot consumers can discover and access the test listing while other accounts cannot. Marketplace listing audience and share-grant design are independent governance controls. For member analytics and long-term audit records at a pension administrator, application manifest and permission review show requested access outside the stated data-processing use case. The outcome should establish that a staged app installs under approved necessary privileges and cannot query unrelated protected objects.
An authorized consumer queries the shared object while no unmanaged full dataset export is required. Snowflake secure sharing can provide governed access without traditional physical data copying. For member analytics and long-term audit records at a pension administrator, application manifest and permission review show requested access outside the stated data-processing use case. The outcome should establish that a staged app installs under approved necessary privileges and cannot query unrelated protected objects.
A staged app installs under approved necessary privileges and cannot query unrelated protected objects. For member analytics and long-term audit records at a pension administrator, application manifest and permission review show requested access outside the stated data-processing use case. Native Apps distribute governed in-platform logic, but installation privileges and lifecycle must still be reviewed. The documented change is to review the Native App package, application roles, permission requests and version lifecycle with the consumer.
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 member analytics and long-term audit records at a pension administrator, application manifest and permission review show requested access outside the stated data-processing use case. The outcome should establish that a staged app installs under approved necessary privileges and cannot query unrelated protected objects.
Question 227
In factory telemetry and supplier quality dashboards at a manufacturing group, a validated correction is proposed: Define a scoped supported API integration with reviewed network rules and controlled invocation privileges. It responds to: An engineer grants a service external API integration unrestricted access when its stored procedure only requires one approved endpoint. Choose the best measurable success criterion.
Correct Answer: B
Explanation
A controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. A confirming test shows that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.
A permitted endpoint call works while an unrelated destination cannot be contacted through the integration. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. External network and API integrations should constrain egress destinations and execution privileges. To correct it, define a scoped supported API integration with reviewed network rules and controlled invocation privileges.
A controlled release executes only reviewed SQL and rejects unapproved branch changes. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. A confirming test shows that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.
A seeded export appears only in the authorized destination and a test unauthorized prefix is denied. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, integration inventory shows an allowed destination list much wider than the program's documented business requirement. A confirming test shows that a permitted endpoint call works while an unrelated destination cannot be contacted through the integration.
Question 228
The Snowflake data engineering team at a municipal authority plans to: Enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs. The issue affecting citizen service reporting and licensed contractor data is: A virtual warehouse consumes credits overnight despite no queries and the finance team assumes every query has become expensive. Which finding best distinguishes this cause from other Snowflake failures?
Correct Answer: D
Explanation
Metering history shows spikes attributed to a warehouse outside the monitor's assignment. Resource monitors act on associated virtual-warehouse credit usage rather than any unrelated account cost automatically. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Instead, enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.
Account usage records attribute substantial credits to non-warehouse services absent from warehouse-metering-only reports. Snowflake total compute cost includes serverless services and is not always visible in warehouse metering. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Instead, enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.
GRANTS inventory shows table SELECT is present but warehouse USAGE is missing from active role hierarchy. Snowflake role authorization must cover both referenced data and chosen execution warehouse. For citizen service reporting and licensed contractor data at a municipal authority, metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Instead, enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.
Metering shows running warehouse time during idle intervals and the warehouse auto-suspend setting is disabled. Warehouse credit costs can accrue during idle running time separately from actual query work. To address this, enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs. Confirm that after an idle test, warehouse usage credits stop accruing and the next approved job resumes successfully; the reported setting is: the snowflake data engineering team at a municipal authority plans to: enable an approved auto-suspend threshold and appropriate auto-resume while checking effects on intermittent jobs.
Question 229
For cross-border shipment data and clearance events at a customs broker, engineers propose: Separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. Their incident states: An operations team assumes suspending its only virtual warehouse will erase permanent customer data and keeps compute running all night. What evidence should be verified before implementing the change?
Correct Answer: D
Explanation
Consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. Compute-credit consumption and managed storage usage are distinct cost drivers. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. To address this, separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test.
Query history shows overlapping workloads and queuing despite healthy underlying cloud storage availability. Independent virtual warehouses support workload isolation over shared centralized data. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. To address this, separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test.
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. For cross-border shipment data and clearance events at a customs broker, billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. To address this, separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test.
Billing history shows uninterrupted warehouse credits during idle hours while table storage remains intact through prior controlled suspension. Snowflake separates independently scalable query compute from persistent managed table storage. The corresponding fix is to separate warehouse compute lifecycle from durable database storage and enable supported auto-suspend with a safe restart test. A successful test should show that an idle warehouse suspends, compute charges stop for idle time, and an authorized new query resumes access to unchanged table rows.
Question 230
In network event logs and account churn models at a telecommunications provider, a validated correction is proposed: Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. It responds to: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. Choose the best measurable success criterion.
Correct Answer: A
Explanation
The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. The documented change is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.
An allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.
A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.
A staged app installs under approved necessary privileges and cannot query unrelated protected objects. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.
SnowPro Core COF-C03 Practice Tests
- Snowflake SnowPro Core COF-C03 Practice Test 21 - 10 Questions (Last Reviewed 27-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 22 - 10 Questions (Last Reviewed 26-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 23 - 10 Questions (Last Reviewed 25-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 24 - 10 Questions (Last Reviewed 24-Oct-2026)
- Snowflake SnowPro Core COF-C03 Practice Test 25 - 10 Questions (Last Reviewed 23-Oct-2026)
