Snowflake SnowPro Core COF-C03 Practice Test 89
Question 880
[Production cutover rehearsal] The team proposes: Select a strict COPY INTO error policy such as ABORT_STATEMENT and reconcile source counts before releasing downstream results. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
- After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
- The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
Explanation
Correct Answer
D:The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows. This is an outcome test of the specified copy into error-handling choice action under the production cutover rehearsal conditions. COPY error behavior determines whether load execution aborts or continues past bad rows; strict policy fits completeness-sensitive feeds.
Incorrect Answers
A:In this production cutover rehearsal 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 copy into error-handling choice action; the appropriate test is: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
B:In this production cutover rehearsal context, The test clone is independently writable and initial storage growth is small compared with a full reload of every source table. This is an outcome for a different requirement: A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. It cannot by itself validate the proposed copy into error-handling choice action; the appropriate test is: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
C:After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions. This is an outcome for a different requirement: A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. It cannot by itself validate the proposed copy into error-handling choice action; the appropriate test is: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
Question 881
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
- Assume users can run SELECT AT against arbitrary Fail-safe snapshots after Time Travel expires.
- Replace the protected production table with transient storage merely to avoid Fail-safe storage expense.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
Explanation
Correct Answer
A:The discriminating technical reason is: Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
Incorrect Answers
B:Under post-rollout service review conditions, Assume users can run SELECT AT against arbitrary Fail-safe snapshots after Time Travel expires. That is a mistake for a different time travel versus fail-safe recoverability task, where 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 does not directly defeat the present transient staging table lifecycle requirement, whose proper treatment is: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
C:That is a mistake for a different permanent table recovery choice task, where An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It does not directly defeat the present transient staging table lifecycle requirement, whose proper treatment is: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
D:Under post-rollout service review 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 transient staging table lifecycle requirement, whose proper treatment is: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
Question 882
[Security control assessment] A reviewer recommends: Run supported Snowflake data-classification capabilities and review resulting tags or classification metadata before policy assignment. The requirement remains: A quarterly access-control audit requires an evidence-backed answer. A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. 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.
- Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
- Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows.
Explanation
Correct Answer
B:In this security control assessment context, Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping. The recommendation is linked to observable evidence for this exact case: Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific automated sensitive-data classification action or its validation path: Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
C:That option concerns dynamic data masking policy, not the requirement in this case. It does not justify the specific automated sensitive-data classification action or its validation path: Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
D:That option concerns row access policy filtering, not the requirement in this case. It does not justify the specific automated sensitive-data classification action or its validation path: Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
Question 883
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
- Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics.
Explanation
Correct Answer
C:Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently. In this production cutover rehearsal setting, the intended validation is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
A:That action is relevant when Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
B: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. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
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 task scheduled orchestration need.
Question 884
[Production migration readiness] A reviewer recommends: Create an appropriate stream on the table and consume its change records transactionally through a downstream process. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
- Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
Explanation
Correct Answer
D:In this production migration readiness context, Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves. The recommendation is linked to observable evidence for this exact case: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns permanent table recovery choice, not the requirement in this case. It does not justify the specific stream object change tracking action or its validation path: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
B:That option concerns dynamic table declarative refresh, not the requirement in this case. It does not justify the specific stream object change tracking action or its validation path: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
C:It does not justify the specific stream object change tracking action or its validation path: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Question 885
[Production cutover rehearsal] The team proposes: Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Explanation
Correct Answer
A:After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint. This is an outcome test of the specified stream cdc consumption action under the production cutover rehearsal conditions. A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
Incorrect Answers
B:In this production cutover rehearsal context, A staged file is visible through the table-stage reference and a controlled COPY loads the intended table. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
C:Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load. This is an outcome for a different requirement: A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
D:In this production cutover rehearsal context, The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome for a different requirement: A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
Question 886
[Architecture planning workshop] The team proposes: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities. Its actual requirement is: 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 observation most directly validates success?
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
- Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
Explanation
Correct Answer
B:Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant. This is an outcome test of the specified streamlit app inside snowflake action under the architecture planning workshop conditions.
Incorrect Answers
A:In this architecture planning workshop 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 streamlit app inside snowflake action; the appropriate test is: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
C:In this architecture planning workshop context, Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured. This is an outcome for a different requirement: A company operates accounts on two clouds and wants to access a dataset from the second account without assuming storage instantly appears in both regions. It cannot by itself validate the proposed streamlit app inside snowflake action; the appropriate test is: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
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 streamlit app inside snowflake action; the appropriate test is: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
Question 887
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
- Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence.
- Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
- Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources.
Explanation
Correct Answer
C:Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count. In this production migration readiness setting, the intended validation is: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
Incorrect Answers
A:That action is relevant when Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
B:That action is relevant when A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It is not the primary action for the stated multi-cluster concurrency scaling need.
D:That action is relevant when A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
Question 888
[Post-rollout service review] 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 Snowflake action best meets this specific requirement?
- Keep supported DataFrame operations in Snowflake and inspect query execution before invoking local collect operations.
- Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations.
Explanation
Correct Answer
D:Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations. In this post-rollout service review setting, the intended validation is: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
Incorrect Answers
A:That action is relevant when Python engineers built Snowpark DataFrame transformations and want to avoid accidental collection of millions of protected records to a laptop. Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations.
B:That action is relevant when A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration.
C:That action is relevant when A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations.
Question 889
[Identity and governance change request] The team proposes: Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. An organization must restrict logins to approved corporate egress ranges even when credentials are correct. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- An approved corporate source can connect while a test connection from an excluded source is rejected.
- Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
- Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Explanation
Correct Answer
A:An approved corporate source can connect while a test connection from an excluded source is rejected. This is an outcome test of the specified network policy address restrictions action under the identity and governance change request conditions. Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
Incorrect Answers
B:In this identity and governance change request context, Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection. This is an outcome for a different requirement: A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
C:Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used. This is an outcome for a different requirement: A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
D:In this identity and governance change request context, SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome for a different requirement: A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. It cannot by itself validate the proposed network policy address restrictions action; the appropriate test is: An approved corporate source can connect while a test connection from an excluded source is rejected.
Question 890
[Optimization regression test] A reviewer recommends: Load the payload into a VARIANT column and use supported path extraction and casts for downstream typed calculations. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
- VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
- Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
- 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, VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data. The recommendation is linked to observable evidence for this exact case: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the optimization regression test conditions, PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records. That explanation applies to a different pivot aggregate into columns problem: A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. It does not justify the specific variant semi-structured access action or its validation path: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic.
C:That explanation applies to a different cortex analyst structured nl-to-sql problem: Business users want to ask plain-language questions against governed structured metrics with defined business terminology.
D:That explanation applies to a different query queueing load analysis problem: A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start.