Snowflake SnowPro Core COF-C03 Practice Test 96
Question 950
[Provider and consumer workshop] The team proposes: Evaluate a Snowflake Data Clean Room with approved collaboration templates and privacy controls for the intended aggregate analysis. Its actual requirement is: A data collaboration team is defining the permitted provider and consumer relationship. Two advertisers want to calculate joint audience overlap while preventing either company from freely inspecting the other's raw person-level records. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
- The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
- The consumer creates a database from the share and can SELECT only granted objects, with provider revocation reflected in access.
- The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
Explanation
Correct Answer
B:The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures. This is an outcome test of the specified privacy-preserving data clean room action under the provider and consumer workshop conditions. Data Clean Rooms enable governed joint analytics with protections around raw participant data and supported query results.
Incorrect Answers
A: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 privacy-preserving data clean room action; the appropriate test is: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
C:In this provider and consumer workshop context, The consumer creates a database from the share and can SELECT only granted objects, with provider revocation reflected in access. This is an outcome for a different requirement: A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. It cannot by itself validate the proposed privacy-preserving data clean room action; the appropriate test is: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
D:In this provider and consumer workshop context, The recipient discovers the listing in its region and can read the expected version after fulfillment completes. This is an outcome for a different requirement: A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. It cannot by itself validate the proposed privacy-preserving data clean room action; the appropriate test is: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
Question 951
[Production migration readiness] A reviewer recommends: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
- Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
- Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
Explanation
Correct Answer
C:In this production migration readiness 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:For the production migration readiness conditions, Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration. That explanation applies to a different cross-region snowflake account planning problem: 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 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:That option concerns snowsight analyst interface, 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.
D:For the production migration readiness conditions, Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog. That explanation applies to a different account and schema object hierarchy problem: A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. 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 952
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Select a strict COPY INTO error policy such as ABORT_STATEMENT and reconcile source counts before releasing downstream results.
- Create a supported zero-copy clone of the database or selected schema and track later divergence.
- Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
- Use zero-copy cloning for an authorized internal copy and distinguish it from a cross-account secure share.
Explanation
Correct Answer
D:Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption. In this partner onboarding review setting, the intended validation is: After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
Incorrect Answers
A:That action is relevant when A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. It is not the primary action for the stated zero-copy clone lifecycle in collaboration need.
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. Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
C:That action is relevant when Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. It is not the primary action for the stated zero-copy clone lifecycle in collaboration need.
Question 953
[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 specific design mistake would most directly defeat the intended result?
- Use Cortex Search as though it alone provides a certified semantic definition of revenue aggregations in every structured table.
- Strip all JSON structure to a single concatenated string and assume nested numeric comparisons work without parsing.
- Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
- Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Explanation
Correct Answer
A:The discriminating technical reason is: Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. Use Cortex Search as though it alone provides a certified semantic definition of revenue aggregations in every structured table.
Incorrect Answers
B:That is a mistake for a different variant semi-structured access task, where A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. Under architecture planning workshop conditions, Strip all JSON structure to a single concatenated string and assume nested numeric comparisons work without parsing.
C:That is a mistake for a different cortex search document retrieval task, where A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It does not directly defeat the present cortex analyst structured nl-to-sql requirement, whose proper treatment is: Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
D:Under architecture planning workshop conditions, Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Question 954
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. 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?
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- Treat ACCOUNT_USAGE as a zero-latency feed and conclude recent events never occurred when rows are delayed.
- Resize compute warehouses to hide a missing authentication policy finding from the security dashboard.
- Write one object-storage CSV per row and assume ordinary hourly COPY INTO is a direct streaming interface.
Explanation
Correct Answer
B:The discriminating technical reason is: Account usage views support historical auditing but can lag live activity; they are distinct from instant session state. This directly undermines account_usage audit latency in the specified context.
Incorrect Answers
A: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 account_usage audit latency requirement, whose proper treatment is: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges.
C:That is a mistake for a different trust center posture findings task, where A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. It does not directly defeat the present account_usage audit latency requirement, whose proper treatment is: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges.
D: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 account_usage audit latency requirement, whose proper treatment is: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges.
Question 955
[Ingestion design acceptance] 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 engineering team is checking the design before promoting a pipeline. An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
- TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
- 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.
Explanation
Correct Answer
C: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 ingestion design acceptance conditions. A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
Incorrect Answers
A:In this ingestion design acceptance context, A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome for a different requirement: A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. 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.
B:In this ingestion design acceptance context, TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. This is an outcome for a different requirement: A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. 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 ingestion design acceptance 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.
Question 956
[Post-rollout service review] The team proposes: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
- The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
- Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
Explanation
Correct Answer
D:Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers. This is an outcome test of the specified cortex search document retrieval action under the post-rollout service review conditions. Cortex Search is designed for low-latency hybrid document/text retrieval, which differs from semantic text-to-SQL analytics.
Incorrect Answers
A:In this post-rollout service review context, Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows. This is an outcome for a different requirement: Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It cannot by itself validate the proposed cortex search document retrieval action; the appropriate test is: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
B:Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome for a different requirement: A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It cannot by itself validate the proposed cortex search document retrieval action; the appropriate test is: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
C:In this post-rollout service review context, The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model. This is an outcome for a different requirement: An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. It cannot by itself validate the proposed cortex search document retrieval action; the appropriate test is: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
Question 957
[Query performance review] A reviewer recommends: Use Snowflake PIVOT on the supported aggregation and quarter categories or an equivalent conditional aggregate. The requirement remains: A performance engineer is benchmarking representative queries before accepting changes. A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
- MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
- Partition metadata lets Snowflake skip micro-partitions whose ranges cannot satisfy the filter, but scattered values limit effective pruning.
- Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
Explanation
Correct Answer
A:In this query performance review context, PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records. The recommendation is linked to observable evidence for this exact case: A validated report has one region row and expected quarter columns with reconciled totals. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns merge keyed upsert, not the requirement in this case. It does not justify the specific pivot aggregate into columns action or its validation path: A validated report has one region row and expected quarter columns with reconciled totals.
C:That option concerns selective filter micro-partition pruning, not the requirement in this case. It does not justify the specific pivot aggregate into columns action or its validation path: A validated report has one region row and expected quarter columns with reconciled totals.
D:For the query performance review conditions, Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration. That explanation applies to a different cross-region snowflake account planning problem: 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 does not justify the specific pivot aggregate into columns action or its validation path: A validated report has one region row and expected quarter columns with reconciled totals.
Question 958
[Production migration readiness] A reviewer recommends: Inspect partition pruning and clustering characteristics before choosing a supported data-organizing strategy. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table.
- Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows.
- Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Explanation
Correct Answer
B:In this production migration readiness context, Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows. The recommendation is linked to observable evidence for this exact case: Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns automatic clustering cost tradeoff, not the requirement in this case. It does not justify the specific micro-partition pruning metadata action or its validation path: Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change.
C:It does not justify the specific micro-partition pruning metadata action or its validation path: Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change.
D:For the production migration readiness 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 micro-partition pruning metadata action or its validation path: Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change.
Question 959
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
- Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT.
- Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
- Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
Explanation
Correct Answer
C:The supportable direction is: Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches. This directly undermines merge keyed upsert in the specified context.
Incorrect Answers
A:That is a mistake for a different stream cdc consumption task, where An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. Under optimization regression test conditions, Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
B:Under optimization regression test conditions, Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT.
D:That is a mistake for a different window-function deterministic ranking task, where A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. Under optimization regression test conditions, Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
Question 960
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design.
- Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges.
Explanation
Correct Answer
D:Account usage views support historical auditing but can lag live activity; they are distinct from instant session state. In this production compliance review setting, the intended validation is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
A:That action is relevant when A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. Account usage views support historical auditing but can lag live activity; they are distinct from instant session state.
B:That action is relevant when 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. Account usage views support historical auditing but can lag live activity; they are distinct from instant session state.
C:That action is relevant when An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It is not the primary action for the stated account_usage audit latency need.