Snowflake SnowPro Core COF-C03 Practice Test 86
Question 850
[Query performance review] A performance engineer is benchmarking representative queries before accepting changes. A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
- Assess clustering depth and query frequency before assigning a clustering key with ongoing maintenance cost.
- Inspect partition pruning and clustering characteristics before choosing a supported data-organizing strategy.
- Account for local warehouse data-cache loss across suspension, and test steady-state cost/performance without assuming persistence.
Explanation
Correct Answer
B:Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table. In this query performance review setting, the intended validation is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
Incorrect Answers
A:That action is relevant when An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It is not the primary action for the stated automatic clustering cost tradeoff need.
C:That action is relevant when A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table.
D:That action is relevant when A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It is not the primary action for the stated automatic clustering cost tradeoff need.
Question 851
[Post-rollout service review] A reviewer recommends: Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
- A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
- Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Explanation
Correct Answer
C:In this post-rollout service review context, Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. The recommendation is linked to observable evidence for this exact case: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
B:That option concerns cortex generative text operation, not the requirement in this case. It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
D:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
Question 852
[Architecture planning workshop] A reviewer recommends: Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data. The requirement remains: An internal platform architecture group is assessing the initial design. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
- Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
Explanation
Correct Answer
D:In this architecture planning workshop context, Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. The recommendation is linked to observable evidence for this exact case: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns variant semi-structured access, not the requirement in this case. It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
B:That option concerns snowsight analyst interface, not the requirement in this case. It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
C:For the architecture planning workshop conditions, External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table. That explanation applies to a different external table over data lake problem: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not justify the specific cortex analyst structured nl-to-sql action or its validation path: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
Question 853
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
Explanation
Correct Answer
A:The discriminating technical reason is: Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage. The supportable direction is: Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
Incorrect Answers
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 production migration readiness conditions, Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
C:That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not directly defeat the present dynamic table declarative refresh requirement, whose proper treatment is: Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
D:That is a mistake for a different stream object change tracking task, where A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. It does not directly defeat the present dynamic table declarative refresh requirement, whose proper treatment is: Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
Question 854
[Pipeline incident investigation] The team proposes: Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files. Its actual requirement is: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- Load history and target counts confirm expected files were not ingested twice after simulated network retry.
- Validation output identifies the same malformed records that can be corrected before the final committed load.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Explanation
Correct Answer
B:Load history and target counts confirm expected files were not ingested twice after simulated network retry. This is an outcome test of the specified load idempotence and history action under the pipeline incident investigation conditions. Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
Incorrect Answers
A: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 load idempotence and history action; the appropriate test is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
C:In this pipeline incident investigation context, Validation output identifies the same malformed records that can be corrected before the final committed load. This is an outcome for a different requirement: A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. It cannot by itself validate the proposed load idempotence and history action; the appropriate test is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
D:In this pipeline incident investigation context, Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh. This is an outcome for a different requirement: A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It cannot by itself validate the proposed load idempotence and history action; the appropriate test is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
Question 855
[Production compliance review] A reviewer recommends: Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges. The requirement remains: 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 explanation best justifies this recommendation?
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
- Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
- Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
- Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
Explanation
Correct Answer
C:In this production compliance review context, Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy. The recommendation is linked to observable evidence for this exact case: An approved corporate source can connect while a test connection from an excluded source is rejected. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns dynamic data masking policy, not the requirement in this case. It does not justify the specific network policy address restrictions action or its validation path: An approved corporate source can connect while a test connection from an excluded source is rejected.
B:That option concerns private network endpoint verification, not the requirement in this case. It does not justify the specific network policy address restrictions action or its validation path: An approved corporate source can connect while a test connection from an excluded source is rejected.
D:That option concerns automated sensitive-data classification, not the requirement in this case. It does not justify the specific network policy address restrictions action or its validation path: An approved corporate source can connect while a test connection from an excluded source is rejected.
Question 856
[Query performance review] A reviewer recommends: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity. The requirement remains: A performance engineer is benchmarking representative queries before accepting changes. A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time.
- A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
Explanation
Correct Answer
D:In this query performance review context, A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query. The recommendation is linked to observable evidence for this exact case: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the query performance review conditions, Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause. That explanation applies to a different query profile bottleneck localization problem: 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 justify the specific query queueing load analysis action or its validation path: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
B:For the query performance review conditions, Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. That explanation applies to a different load idempotence and history problem: A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It does not justify the specific query queueing load analysis action or its validation path: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
C:Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time.
Question 857
[Post-rollout service review] The team proposes: Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
- Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
Explanation
Correct Answer
A:The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight. This is an outcome test of the specified snowsight analyst interface action under the post-rollout service review conditions. Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
Incorrect Answers
B:In this post-rollout service review context, Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows. This is an outcome for a different requirement: Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
C:In this post-rollout service review context, Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions. This is an outcome for a different requirement: A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
D:A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys. This is an outcome for a different requirement: An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
Question 858
[Query performance review] The team proposes: Evaluate a supported materialized view for the recurring aggregation and quantify maintenance and query benefit. Its actual requirement is: A performance engineer is benchmarking representative queries before accepting changes. A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- 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.
- Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
- Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
Explanation
Correct Answer
B: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 query performance review conditions. Materialized views persist eligible precomputed results, reducing repeated calculation at the expense of refresh storage and compute.
Incorrect Answers
A:In this query performance review 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.
C:In this query performance review 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.
D:Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost. This is an outcome for a different requirement: Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. 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 859
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. 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?
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
- Assume attaching a SQL comment to a shared table automatically creates a deployable Native App package.
Explanation
Correct Answer
C:The supportable direction is: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities. Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
Incorrect Answers
A:Under architecture planning workshop conditions, Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference. That is a mistake for a different time travel historical query task, where An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. It does not directly defeat the present streamlit app inside snowflake requirement, whose proper treatment is: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities.
B:Under architecture planning workshop conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support. That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not directly defeat the present streamlit app inside snowflake requirement, whose proper treatment is: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities.
D:That is a mistake for a different native app distribution to consumers task, where A software vendor needs to package governed application logic with Snowflake-integrated deployment instead of sending a collection of ad hoc scripts. Under architecture planning workshop conditions, Assume attaching a SQL comment to a shared table automatically creates a deployable Native App package.
Question 860
[Architecture planning workshop] The team proposes: Create an appropriate stream on the table and consume its change records transactionally through a downstream process. Its actual requirement is: An internal platform architecture group is assessing the initial design. A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Explanation
Correct Answer
D:A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome test of the specified stream object change tracking action under the architecture planning workshop conditions. Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
Incorrect Answers
A: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 stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
B:In this architecture planning workshop context, Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. This is an outcome for a different requirement: An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
C:A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys. This is an outcome for a different requirement: An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.