Snowflake SnowPro Core COF-C03 Practice Test 82
Question 810
[Query performance review] 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 Snowflake action best meets this specific requirement?
- Evaluate a supported materialized view for the recurring aggregation and quantify maintenance and query benefit.
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
Explanation
Correct Answer
B:Query Acceleration Service can offload eligible query components to shared compute; it does not replace base warehouse execution for every operation. In this query performance review setting, the intended validation is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
Incorrect Answers
A:That action is relevant when A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. Query Acceleration Service can offload eligible query components to shared compute; it does not replace base warehouse execution for every operation.
C:That action is relevant when A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
D: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 query acceleration service suitability need.
Question 811
[Architecture planning workshop] A reviewer recommends: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials. The requirement remains: An internal platform architecture group is assessing the initial design. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
- Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
Explanation
Correct Answer
C:In this architecture planning workshop context, Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles. The recommendation is linked to observable evidence for this exact case: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns cross-region snowflake account planning, not the requirement in this case. It does not justify the specific snowflake cli reproducible developer work action or its validation path: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
B:It does not justify the specific snowflake cli reproducible developer work action or its validation path: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
D:That option concerns streamlit app inside snowflake, not the requirement in this case. It does not justify the specific snowflake cli reproducible developer work action or its validation path: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
Question 812
[Collaboration operating audit] A reviewer recommends: Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort. The requirement remains: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. 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. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
- Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
Explanation
Correct Answer
D:In this collaboration operating audit context, Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store. The recommendation is linked to observable evidence for this exact case: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the collaboration operating audit conditions, System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority. That explanation applies to a different custom roles versus system roles problem: A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It does not justify the specific time travel versus fail-safe recoverability action or its validation path: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
B:For the collaboration operating audit conditions, Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. That explanation applies to a different transient staging table lifecycle problem: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It does not justify the specific time travel versus fail-safe recoverability action or its validation path: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
C:That explanation applies to a different permanent table recovery choice problem: An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat.
Question 813
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges.
Explanation
Correct Answer
A:Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value. In this security control assessment setting, the intended validation is: The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
Incorrect Answers
B:It is not the primary action for the stated dynamic data masking policy need.
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 dynamic data masking policy need.
D:That action is relevant when An organization must restrict logins to approved corporate egress ranges even when credentials are correct. Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
Question 814
[Production migration readiness] The team proposes: Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period. Its actual requirement is: 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 observation most directly validates success?
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
- The account's edition and configured private endpoint show a private connection path, and network tests reject unintended access.
- A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
Explanation
Correct Answer
B:Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. This is an outcome test of the specified enterprise edition feature selection action under the production migration readiness conditions. Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
Incorrect Answers
A:In this production migration readiness 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 enterprise edition feature selection action; the appropriate test is: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
C:The account's edition and configured private endpoint show a private connection path, and network tests reject unintended access. This is an outcome for a different requirement: A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. It cannot by itself validate the proposed enterprise edition feature selection action; the appropriate test is: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
D: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 enterprise edition feature selection action; the appropriate test is: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
Question 815
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort.
- Use Snowflake Time Travel AT or BEFORE syntax with a valid historical reference for the affected table.
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
Explanation
Correct Answer
C:Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. In this post-rollout service review setting, the intended validation is: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
Incorrect Answers
A:That action is relevant when A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It is not the primary action for the stated time travel historical query need.
B: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 time travel historical query need.
D:It is not the primary action for the stated time travel historical query need.
Question 816
[Production compliance review] The team proposes: Configure a supported federated SSO security integration and verify identity, certificates, and account routing. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Identity logs and a controlled sign-in test show the required second factor before an authorized session starts.
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
- Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
- A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
Explanation
Correct Answer
D:A test user signs in through the approved identity provider and receives only the expected Snowflake role access. This is an outcome test of the specified federated single sign-on action under the production compliance review conditions. Federated authentication delegates sign-in to the organization's identity provider while object access still depends on Snowflake roles.
Incorrect Answers
A:Identity logs and a controlled sign-in test show the required second factor before an authorized session starts. This is an outcome for a different requirement: A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. It cannot by itself validate the proposed federated single sign-on action; the appropriate test is: A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
B:In this production compliance review context, The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider. This is an outcome for a different requirement: A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It cannot by itself validate the proposed federated single sign-on action; the appropriate test is: A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
C:In this production compliance review context, Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied. This is an outcome for a different requirement: A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It cannot by itself validate the proposed federated single sign-on action; the appropriate test is: A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
Question 817
[Post-rollout service review] A reviewer recommends: Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations.
- The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown.
- Snowpark-optimized warehouses provide a higher memory profile that can help memory-intensive Snowpark computations, subject to the workload's actual bottleneck.
- Snowpark can execute supported transformations near governed data; eager client collection changes scale and exposure risks.
Explanation
Correct Answer
A:In this post-rollout service review context, Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations. The recommendation is linked to observable evidence for this exact case: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns spark connector distributed read, not the requirement in this case. It does not justify the specific snowpark python pushdown action or its validation path: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
C:It does not justify the specific snowpark python pushdown action or its validation path: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
D:That option concerns snowpark transformation pushdown verification, not the requirement in this case. It does not justify the specific snowpark python pushdown action or its validation path: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
Question 818
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles.
- Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
- Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow.
Explanation
Correct Answer
B:Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently. In this ingestion design acceptance setting, the intended validation is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
Incorrect Answers
A:That action is relevant when Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
C:That action is relevant when A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It is not the primary action for the stated task scheduled orchestration need.
D:That action is relevant when An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. It is not the primary action for the stated task scheduled orchestration need.
Question 819
[Architecture planning workshop] 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 Snowflake action best meets this specific requirement?
- Evaluate the Business Critical or otherwise eligible edition and configure a supported private connectivity option for its cloud.
- Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
- Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
Explanation
Correct Answer
C:Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. In this architecture planning workshop setting, the intended validation is: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
Incorrect Answers
A:That action is relevant when A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
B:That action is relevant when An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
D:That action is relevant when A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It is not the primary action for the stated cortex analyst structured nl-to-sql need.
Question 820
[Post-rollout service review] The team proposes: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A retailer's nightly ELT job saturates compute while an unrelated dashboard must keep predictable query latency; both workloads read the same sales tables. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
Explanation
Correct Answer
D:Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse. This is an outcome test of the specified independent compute for bi and elt action under the post-rollout service review conditions.
Incorrect Answers
A:In this post-rollout service review context, 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 independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
B:In this post-rollout service review context, Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable. This is an outcome for a different requirement: During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It cannot by itself validate the proposed independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
C:In this post-rollout service review context, Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome for a different requirement: A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It cannot by itself validate the proposed independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.