Snowflake SnowPro Core COF-C03 Practice Test 72
Question 710
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
- Start a destructive truncation and full reload without inspecting parsing failures in the incoming files.
- Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
Explanation
Correct Answer
B:The discriminating technical reason is: Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files. This directly undermines copy into location for unload in the specified context.
Incorrect Answers
A:That is a mistake for a different zero-copy clone for sandbox task, where A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. Under ingestion design acceptance conditions, Export the entire database to CSV and reload it as the only supported cloning approach.
C:Under ingestion design acceptance conditions, Start a destructive truncation and full reload without inspecting parsing failures in the incoming files.
D:Under ingestion design acceptance conditions, Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
Question 711
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Explanation
Correct Answer
C:The discriminating technical reason is: Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies. The supportable direction is: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query.
Incorrect Answers
A:Under ingestion design acceptance conditions, Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
B:That is a mistake for a different dynamic data masking policy task, where A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. Under ingestion design acceptance conditions, Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
D:Under ingestion design acceptance conditions, Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files. That is a mistake for a different copy into location for unload task, where A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. It does not directly defeat the present dynamic table downstream freshness requirement, whose proper treatment is: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query.
Question 712
[Peak traffic performance incident] The team proposes: Evaluate a supported materialized view for the recurring aggregation and quantify maintenance and query benefit. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- A validated report has one region row and expected quarter columns with reconciled totals.
- Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Explanation
Correct Answer
D:The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome test of the specified materialized view precomputation action under the peak traffic performance incident conditions. Materialized views persist eligible precomputed results, reducing repeated calculation at the expense of refresh storage and compute.
Incorrect Answers
A:A validated report has one region row and expected quarter columns with reconciled totals. This is an outcome for a different requirement: A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. It cannot by itself validate the proposed materialized view precomputation action; the appropriate test is: The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
B:In this peak traffic performance incident context, Clustering information and workload-wide latency improve enough to justify the observed maintenance credits. This is an outcome for a different requirement: A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. It cannot by itself validate the proposed materialized view precomputation action; the appropriate test is: The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
C:In this peak traffic performance incident context, After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint. This is an outcome for a different requirement: An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. It cannot by itself validate the proposed materialized view precomputation action; the appropriate test is: The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Question 713
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Configure appropriate future grants for the required schema scope while preserving narrowly defined access roles.
Explanation
Correct Answer
A:Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable. In this production compliance review setting, the intended validation is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Incorrect Answers
B:That action is relevant when A user has an approved reporting role and a separate engineering role but a worksheet unexpectedly lacks SELECT even though the second role has the grant. Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
C:That action is relevant when A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It is not the primary action for the stated inherited functional role grants need.
D:That action is relevant when Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
Question 714
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Create a stream and expect it to wake up hourly and execute the cleanup procedure without a task or consumer.
- Create a serverless ingestion pipe and expect it to act as a row-level scalar SQL function in every SELECT.
- Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
- Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
Explanation
Correct Answer
B:The discriminating technical reason is: A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row. Create a serverless ingestion pipe and expect it to act as a row-level scalar SQL function in every SELECT.
Incorrect Answers
A:That is a mistake for a different task scheduled orchestration task, where A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. It does not directly defeat the present sql udf reusable expression requirement, whose proper treatment is: Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles.
C:Under optimization regression test conditions, Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing. That is a mistake for a different query profile bottleneck localization task, where A 70-second analytics query has become slow after a schema change, and the team wants to find whether scanning, joining, or spilling dominates its runtime. It does not directly defeat the present sql udf reusable expression requirement, whose proper treatment is: Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles.
D:That is a mistake for a different stored procedure multi-step operation task, where An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. Under optimization regression test conditions, Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
Question 715
[Production compliance review] The team proposes: Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. An organization must restrict logins to approved corporate egress ranges even when credentials are correct. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
- An approved corporate source can connect while a test connection from an excluded source is rejected.
- Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
Explanation
Correct Answer
C:An approved corporate source can connect while a test connection from an excluded source is rejected. This is an outcome test of the specified network policy address restrictions action under the production compliance review conditions. Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
Incorrect Answers
A:Separate user-role tests return only the authorized region's row keys while total source data remains unchanged. This is an outcome for a different requirement: Regional managers share a table but must see only the geographic rows permitted by their assigned region. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
B:In this production compliance review context, SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome for a different requirement: A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
D:In this production compliance review context, Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection. This is an outcome for a different requirement: A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
Question 716
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
- Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
- Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection.
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
Explanation
Correct Answer
D:Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window. In this production migration readiness setting, the intended validation is: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
A:That action is relevant when A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It is not the primary action for the stated enterprise edition feature selection need.
B:That action is relevant when A table contains several rows per customer and an analyst wants exactly the latest row for each customer after computing ROW_NUMBER. Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
C:That action is relevant when An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
Question 717
[Architecture planning workshop] A reviewer recommends: Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model. The requirement remains: An internal platform architecture group is assessing the initial design. A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model.
- Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
- Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
Explanation
Correct Answer
A:In this architecture planning workshop context, Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model. The recommendation is linked to observable evidence for this exact case: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns dynamic table declarative refresh, not the requirement in this case. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
C:That option concerns micro-partition pruning metadata, not the requirement in this case. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
D:That option concerns transient staging table lifecycle, not the requirement in this case. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
Question 718
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
- Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
- Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
Explanation
Correct Answer
B:The discriminating technical reason is: Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies. Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
Incorrect Answers
A:That is a mistake for a different directory table unstructured metadata task, where A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. Under production cutover rehearsal conditions, Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
C:Under production cutover rehearsal conditions, Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files. That is a mistake for a different copy into location for unload task, where A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. It does not directly defeat the present dynamic table downstream freshness requirement, whose proper treatment is: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query.
D:That is a mistake for a different dynamic table declarative refresh task, where A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. Under production cutover rehearsal conditions, Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
Question 719
[Query performance review] The team proposes: Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload. Its actual requirement is: A performance engineer is benchmarking representative queries before accepting changes. Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
- A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
Explanation
Correct Answer
C:Query Acceleration Service can offload eligible query components to shared compute; it does not replace base warehouse execution for every operation. This is an outcome test of the specified query acceleration service suitability action under the query performance review conditions.
Incorrect Answers
A:In this query performance review context, Remote spill bytes and elapsed time decrease on a representative workload after the targeted change. This is an outcome for a different requirement: A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. It cannot by itself validate the proposed query acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
B:In this query performance review context, Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. This is an outcome for a different requirement: A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. It cannot by itself validate the proposed query acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
D:A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data. This is an outcome for a different requirement: A 70-second analytics query has become slow after a schema change, and the team wants to find whether scanning, joining, or spilling dominates its runtime. It cannot by itself validate the proposed query acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
Question 720
[Production cutover rehearsal] A reviewer recommends: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication. The requirement remains: A data integration group runs a controlled replay with representative files or events. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown.
- Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
Explanation
Correct Answer
D:In this production cutover rehearsal context, The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings. The recommendation is linked to observable evidence for this exact case: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns spark connector distributed read, not the requirement in this case. The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown.
B:That option concerns external stage cloud identity integration, not the requirement in this case. It does not justify the specific kafka connector topic ingestion action or its validation path: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
C:That option concerns load idempotence and history, not the requirement in this case. It does not justify the specific kafka connector topic ingestion action or its validation path: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.