Snowflake SnowPro Core COF-C03 Practice Test 22
Question 210
[Post-rollout service review] The team proposes: Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
Explanation
Correct Answer
B:Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome test of the specified warehouse auto-suspend economics action under the post-rollout service review conditions. Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
Incorrect Answers
A:In this post-rollout service review context, A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY. This is an outcome for a different requirement: Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
C:In this post-rollout service review context, Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. This is an outcome for a different requirement: A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
D:Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. This is an outcome for a different requirement: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It cannot by itself validate the proposed warehouse auto-suspend economics action; the appropriate test is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
Question 211
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort.
- 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.
- Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
Explanation
Correct Answer
C:Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window. In this architecture planning workshop 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 production permanent table was dropped within its configured retention period, and an operator needs a self-service recovery plan rather than a support escalation. It is not the primary action for the stated enterprise edition feature selection need.
B:That action is relevant when An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It is not the primary action for the stated enterprise edition feature selection need.
D: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. It is not the primary action for the stated enterprise edition feature selection need.
Question 212
[Architecture planning workshop] The team proposes: Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection. Its actual requirement is: An internal platform architecture group is assessing the initial design. An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
- Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
Explanation
Correct Answer
D:Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. This is an outcome test of the specified permanent table recovery choice action under the architecture planning workshop conditions. Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
Incorrect Answers
A:A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. This is an outcome for a different requirement: A production permanent table was dropped within its configured retention period, and an operator needs a self-service recovery plan rather than a support escalation. It cannot by itself validate the proposed permanent table recovery choice action; the appropriate test is: Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
B:In this architecture planning workshop context, Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. This is an outcome for a different requirement: A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. It cannot by itself validate the proposed permanent table recovery choice action; the appropriate test is: Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
C:In this architecture planning workshop context, Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome for a different requirement: A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It cannot by itself validate the proposed permanent table recovery choice action; the appropriate test is: Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
Question 213
[Production migration readiness] A reviewer recommends: Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
- A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
- Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
- VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
Explanation
Correct Answer
A:In this production migration readiness 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
B:That option concerns cortex generative text operation, not the requirement in this case. A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
C:That option concerns business critical private connectivity, 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 variant semi-structured access, not the requirement in this case. VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
Question 214
[Optimization regression test] A reviewer recommends: Open the query's profile and compare execution operators, partitions scanned, bytes processed, and spill indicators before tuning. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. 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. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
- Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause.
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
Explanation
Correct Answer
B:In this optimization regression test context, Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause. The recommendation is linked to observable evidence for this exact case: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns warehouse sizing performance experiment, not the requirement in this case. It does not justify the specific query profile bottleneck localization action or its validation path: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
C:That option concerns warehouse scale-up for complex query, not the requirement in this case. It does not justify the specific query profile bottleneck localization action or its validation path: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
D:That option concerns query queueing load analysis, not the requirement in this case. It does not justify the specific query profile bottleneck localization action or its validation path: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
Question 215
[Ingestion design acceptance] A reviewer recommends: Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role. The requirement remains: A data engineering team is checking the design before promoting a pipeline. A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
- Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
Explanation
Correct Answer
C:In this ingestion design acceptance context, Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory. The recommendation is linked to observable evidence for this exact case: A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns streamlit app inside snowflake, not the requirement in this case. Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
B:Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
D:That option concerns external stage cloud identity integration, not the requirement in this case. Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
Question 216
[Security control assessment] A reviewer recommends: Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers. The requirement remains: A quarterly access-control audit requires an evidence-backed answer. A sandbox warehouse is used for unpredictable experiments and a manager needs credit alerts and a suspension threshold for that warehouse. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Managed access centralizes grant management and changes who can authorize privileges on contained objects.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges.
Explanation
Correct Answer
D:In this security control assessment context, Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges. The recommendation is linked to observable evidence for this exact case: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns managed access schema grants, not the requirement in this case. It does not justify the specific resource monitor warehouse budgeting action or its validation path: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
B:That option concerns durable database storage separation, not the requirement in this case. The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
C:A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
Question 217
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
- Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
- Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
Explanation
Correct Answer
A:Cortex Search is designed for low-latency hybrid document/text retrieval, which differs from semantic text-to-SQL analytics. In this architecture planning workshop setting, the intended validation is: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
Incorrect Answers
B:That action is relevant when A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It is not the primary action for the stated cortex search document retrieval need.
C: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 cortex search document retrieval need.
D:That action is relevant when Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It is not the primary action for the stated cortex search document retrieval need.
Question 218
[Production cutover rehearsal] 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 Snowflake action best meets this specific requirement?
- Use the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings.
- Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
- Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role.
Explanation
Correct Answer
B:The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings. In this production cutover rehearsal setting, the intended validation is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Incorrect Answers
A:That action is relevant when A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. It is not the primary action for the stated kafka connector topic ingestion need.
C:That action is relevant when A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It is not the primary action for the stated kafka connector topic ingestion need.
D:That action is relevant when A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. It is not the primary action for the stated kafka connector topic ingestion need.
Question 219
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
- Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
- Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics.
Explanation
Correct Answer
C:Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster. In this peak traffic performance incident setting, the intended validation is: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
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 multi-cluster scale out versus scale up need.
B:That action is relevant when A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It is not the primary action for the stated multi-cluster scale out versus scale up need.
D:That action is relevant when An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. It is not the primary action for the stated multi-cluster scale out versus scale up need.
Question 220
[Ingestion design acceptance] The team proposes: Enable or refresh an appropriate directory table on a supported stage and query its file metadata. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- Load history and target counts confirm expected files were not ingested twice after simulated network retry.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Explanation
Correct Answer
D:Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh. This is an outcome test of the specified directory table unstructured metadata action under the ingestion design acceptance conditions. Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves.
Incorrect Answers
A:A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome for a different requirement: One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
B:In this ingestion design acceptance context, SELECT against the external table returns staged records after location metadata has been refreshed appropriately. This is an outcome for a different requirement: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
C:In this ingestion design acceptance context, Load history and target counts confirm expected files were not ingested twice after simulated network retry. This is an outcome for a different requirement: A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.