Snowflake SnowPro Core COF-C03 Practice Test 93
Question 920
[Ingestion design acceptance] The team proposes: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
- A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
- Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Explanation
Correct Answer
D:Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart. This is an outcome test of the specified kafka connector topic ingestion action under the ingestion design acceptance conditions. The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
Incorrect Answers
A:End-to-end event timestamps show data arriving within the required streaming latency under peak event load. This is an outcome for a different requirement: An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
B:In this ingestion design acceptance context, A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials. This is an outcome for a different requirement: 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 cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
C:In this ingestion design acceptance context, A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions. This is an outcome for a different requirement: A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It cannot by itself validate the proposed kafka connector topic ingestion action; the appropriate test is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Question 921
[Production migration readiness] A reviewer recommends: Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting. The requirement remains: 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 explanation best justifies this recommendation?
- Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies.
- Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
Explanation
Correct Answer
A:In this production migration readiness context, Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage. The recommendation is linked to observable evidence for this exact case: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:It does not justify the specific dynamic table declarative refresh action or its validation path: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
C:That option concerns dynamic table downstream freshness, not the requirement in this case. It does not justify the specific dynamic table declarative refresh action or its validation path: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
D:That option concerns stream object change tracking, not the requirement in this case. It does not justify the specific dynamic table declarative refresh action or its validation path: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
Question 922
[Production migration readiness] A reviewer recommends: Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period. The requirement remains: 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 explanation best justifies this recommendation?
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
- Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
- Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
- QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection.
Explanation
Correct Answer
B:In this production migration readiness context, Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window. The recommendation is linked to observable evidence for this exact case: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns time travel historical query, not the requirement in this case. It does not justify the specific enterprise edition feature selection action or its validation path: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
C:That option concerns time travel versus fail-safe recoverability, not the requirement in this case. It does not justify the specific enterprise edition feature selection action or its validation path: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
D:It does not justify the specific enterprise edition feature selection action or its validation path: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
Question 923
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
- Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
- Increase one warehouse cluster's size exclusively while leaving the configured concurrency cluster limit at one.
- Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
Explanation
Correct Answer
C:The supportable direction is: Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency. Increase one warehouse cluster's size exclusively while leaving the configured concurrency cluster limit at one.
Incorrect Answers
A: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 post-rollout service review conditions, Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
B:That is a mistake for a different warehouse scale-up for complex query task, where A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It does not directly defeat the present multi-cluster concurrency scaling requirement, whose proper treatment is: Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
D:That is a mistake for a different search optimization selective lookup task, where An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. Under post-rollout service review conditions, Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
Question 924
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Keep data in managed database storage and resume compute only when processing is needed.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
Explanation
Correct Answer
D:External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table. In this production migration readiness setting, the intended validation is: SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
Incorrect Answers
A:That action is relevant when An analyst must stage a small support file used only to load one existing target table, with no need for a shared named-stage contract. Use the table's built-in stage where suitable and load into the target using supported commands.
B:That action is relevant when An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
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. External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Question 925
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. 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. 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?
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
Explanation
Correct Answer
A:The supportable direction is: Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement. Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
Incorrect Answers
B:Under identity and governance change request conditions, Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
C:Under identity and governance change request conditions, Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected. That is a mistake for a different inherited functional role grants task, where 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 does not directly defeat the present primary and secondary role session requirement, whose proper treatment is: Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
D:Under identity and governance change request conditions, Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
Question 926
[Post-rollout service review] A reviewer recommends: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
- Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
Explanation
Correct Answer
B:In this post-rollout service review context, Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant. The recommendation is linked to observable evidence for this exact case: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the post-rollout service review 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 streamlit app inside snowflake action or its validation path: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
C:For the post-rollout service review conditions, Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model. That explanation applies to a different native app distribution to consumers problem: A software vendor needs to package governed application logic with Snowflake-integrated deployment instead of sending a collection of ad hoc scripts. It does not justify the specific streamlit app inside snowflake action or its validation path: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
D:For the post-rollout service review conditions, Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. That explanation applies to a different time travel historical query problem: 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 justify the specific streamlit app inside snowflake action or its validation path: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
Question 927
[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 Snowflake action best meets this specific requirement?
- Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
- Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics.
- Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles.
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
Explanation
Correct Answer
C:A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row. In this optimization regression test setting, the intended validation is: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
Incorrect Answers
A: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 sql udf reusable expression need.
B:That action is relevant when An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
D:That action is relevant when 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 is not the primary action for the stated sql udf reusable expression need.
Question 928
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
- Account for local warehouse data-cache loss across suspension, and test steady-state cost/performance without assuming persistence.
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
Explanation
Correct Answer
D:Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse. In this optimization regression test setting, the intended validation is: Two eligible unchanged executions show a reuse indicator, while changed data causes fresh evaluation under documented conditions.
Incorrect Answers
A:That action is relevant when A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
B: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 persisted result reuse conditions need.
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. Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
Question 929
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. 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?
- Assume every Standard edition account automatically gains a customer-managed key simply by creating a masking policy.
- Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
Explanation
Correct Answer
A:The discriminating technical reason is: Tri-Secret Secure combines Snowflake-managed key protection with an eligible customer-managed key model, but it is not enabled just by a SQL grant. The supportable direction is: Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
Incorrect Answers
B:That is a mistake for a different merge keyed upsert task, where A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. Under security control assessment conditions, Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
C:That is a mistake for a different oauth delegated client access task, where A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It does not directly defeat the present customer-managed encryption key option requirement, whose proper treatment is: Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
D:That is a mistake for a different managed access schema grants task, where A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. It does not directly defeat the present customer-managed encryption key option requirement, whose proper treatment is: Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
Question 930
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. 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?
- Copy raw database files from Snowflake's managed storage bucket directly into Spark as the standard connector protocol.
- Create a SQL file format object alone and assume it becomes a running Kafka consumer.
- Write one object-storage CSV per row and assume ordinary hourly COPY INTO is a direct streaming interface.
- Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
Explanation
Correct Answer
B:The supportable direction is: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication. The discriminating technical reason is: The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
Incorrect Answers
A:That is a mistake for a different spark connector distributed read task, where A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. Under ingestion design acceptance conditions, Copy raw database files from Snowflake's managed storage bucket directly into Spark as the standard connector protocol.
C:That is a mistake for a different snowpipe streaming low latency task, where An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It does not directly defeat the present kafka connector topic ingestion requirement, whose proper treatment is: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.
D:That is a mistake for a different external function api integration task, where A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It does not directly defeat the present kafka connector topic ingestion requirement, whose proper treatment is: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.