Snowflake SnowPro Core COF-C03 Practice Test 48
Question 470
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
Explanation
Correct Answer
B:Named internal stages support managed file staging and reusable load references across authorized sessions. In this pipeline incident investigation setting, the intended validation is: LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
A: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 named internal stage for file reuse need.
C:That action is relevant when A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. It is not the primary action for the stated named internal stage for file reuse need.
D:That action is relevant when A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. It is not the primary action for the stated named internal stage for file reuse need.
Question 471
[Production cutover rehearsal] 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 specific design mistake would most directly defeat the intended result?
- Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
- Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
- Create a stream and expect it to wake up hourly and execute the cleanup procedure without a task or consumer.
Explanation
Correct Answer
C:The discriminating technical reason is: A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized. This directly undermines stream cdc consumption in the specified context.
Incorrect Answers
A:That is a mistake for a different dynamic table downstream freshness task, where A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. Under production cutover rehearsal conditions, Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
B:That is a mistake for a different stream object change tracking task, where A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. Under production cutover rehearsal conditions, Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
D:That is a mistake for a different task scheduled orchestration task, where A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. Under production cutover rehearsal conditions, Create a stream and expect it to wake up hourly and execute the cleanup procedure without a task or consumer.
Question 472
[Optimization regression test] A reviewer recommends: Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
- Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
- Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
Explanation
Correct Answer
D:In this optimization regression test context, Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster. The recommendation is linked to observable evidence for this exact case: The cluster count rises during bursts and query queue duration falls in matched concurrency tests. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns warehouse scale-up for complex query, not the requirement in this case. It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
B:That option concerns search optimization selective lookup, not the requirement in this case. It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
C:That option concerns stored procedure multi-step operation, not the requirement in this case. It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
Question 473
[Pipeline incident investigation] A reviewer recommends: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
Explanation
Correct Answer
A:In this pipeline incident investigation context, Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies. The recommendation is linked to observable evidence for this exact case: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns table stage file landing, not the requirement in this case. It does not justify the specific dynamic table downstream freshness action or its validation path: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
C:That option concerns stream cdc consumption, not the requirement in this case. It does not justify the specific dynamic table downstream freshness action or its validation path: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
D:That option concerns dynamic data masking policy, not the requirement in this case. It does not justify the specific dynamic table downstream freshness action or its validation path: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
Question 474
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
- Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
- Evaluate the Business Critical or otherwise eligible edition and configure a supported private connectivity option for its cloud.
Explanation
Correct Answer
B:Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. In this post-rollout service review 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 data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
C: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. Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
D: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. It is not the primary action for the stated cortex analyst structured nl-to-sql need.
Question 475
[Identity and governance change request] A reviewer recommends: Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement. The requirement remains: 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 explanation best justifies this recommendation?
- Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
- Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
- Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles.
- OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
Explanation
Correct Answer
C:In this identity and governance change request context, Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles. The recommendation is linked to observable evidence for this exact case: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the identity and governance change request conditions, Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable. That explanation applies to a different inherited functional role grants problem: 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 justify the specific primary and secondary role session action or its validation path: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
B:For the identity and governance change request conditions, Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading. That explanation applies to a different least-privilege read role problem: A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It does not justify the specific primary and secondary role session action or its validation path: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
D:OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
Question 476
[Production compliance review] The team proposes: Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
- A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
- SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
Explanation
Correct Answer
D:SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations. This is an outcome test of the specified ownership transfer safety action under the production compliance review conditions. Ownership is a distinct powerful privilege; transferring it can affect existing grants and operational control.
Incorrect Answers
A:SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied. This is an outcome for a different requirement: A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It cannot by itself validate the proposed ownership transfer safety action; the appropriate test is: SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
B:In this production compliance review context, A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership. This is an outcome for a different requirement: Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. It cannot by itself validate the proposed ownership transfer safety action; the appropriate test is: SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
C:In this production compliance review context, A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed ownership transfer safety action; the appropriate test is: SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
Question 477
[Identity and governance change request] A reviewer recommends: Configure the available private connectivity option for the eligible edition and cloud, then validate DNS and routing. The requirement remains: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
- Private collaboration environments govern which organizations can discover and share listings beyond simple public marketplace exposure.
- 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.
- Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
Explanation
Correct Answer
A:In this identity and governance change request context, Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions. The recommendation is linked to observable evidence for this exact case: Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns private data exchange collaboration, not the requirement in this case. It does not justify the specific private network endpoint verification action or its validation path: Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
C:That option concerns customer-managed encryption key option, not the requirement in this case. That explanation applies to a different customer-managed encryption key option problem: A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process.
D:That option concerns network policy address restrictions, not the requirement in this case. It does not justify the specific private network endpoint verification action or its validation path: Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
Question 478
[Production migration readiness] The team proposes: Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. 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. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
- Replication status and a controlled secondary-account query confirm the expected dataset and documented lag.
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
Explanation
Correct Answer
B:Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured. This is an outcome test of the specified cross-region snowflake account planning action under the production migration readiness conditions. Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
Incorrect Answers
A:In this production migration readiness context, SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name. This is an outcome for a different requirement: A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It cannot by itself validate the proposed cross-region snowflake account planning action; the appropriate test is: Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
C:In this production migration readiness context, Replication status and a controlled secondary-account query confirm the expected dataset and documented lag. This is an outcome for a different requirement: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It cannot by itself validate the proposed cross-region snowflake account planning action; the appropriate test is: Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
D: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 cross-region snowflake account planning action; the appropriate test is: Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
Question 479
[Pipeline incident investigation] A reviewer recommends: Use the table's built-in stage where suitable and load into the target using supported commands. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. 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. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Named internal stages support managed file staging and reusable load references across authorized sessions.
- Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Explanation
Correct Answer
C:In this pipeline incident investigation context, A table stage gives a convenient table-associated internal landing location without creating a separate named stage. The recommendation is linked to observable evidence for this exact case: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns named internal stage for file reuse, not the requirement in this case. It does not justify the specific table stage file landing action or its validation path: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
B:That option concerns directory table unstructured metadata, not the requirement in this case. That explanation applies to a different directory table unstructured metadata problem: A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction.
D:That option concerns reusable csv file format, not the requirement in this case. It does not justify the specific table stage file landing action or its validation path: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
Question 480
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use zero-copy cloning for an authorized internal copy and distinguish it from a cross-account secure share.
- Create a supported zero-copy clone of the database or selected schema and track later divergence.
- Evaluate and provision a Snowflake reader account with authorized shares and documented provider billing responsibilities.
- Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
Explanation
Correct Answer
D:Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone. In this partner onboarding review setting, the intended validation is: Replication status and a controlled secondary-account query confirm the expected dataset and documented lag.
Incorrect Answers
A:That action is relevant when A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone.
B:That action is relevant when A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. It is not the primary action for the stated replication across regions for availability need.
C:That action is relevant when A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It is not the primary action for the stated replication across regions for availability need.