Snowflake SnowPro Core COF-C03 Practice Test 25
Question 240
[Production compliance review] The team proposes: Inspect Snowflake Trust Center findings and follow documented remediation and review workflow for the supported account. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
- A relevant finding changes state after the corrective configuration and a refreshed review or scan.
Explanation
Correct Answer
D:A relevant finding changes state after the corrective configuration and a refreshed review or scan. This is an outcome test of the specified trust center posture findings action under the production compliance review conditions. Trust Center helps surface account security posture risks; it does not independently grant access or repair every issue automatically.
Incorrect Answers
A:In this production compliance review context, A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can. This is an outcome for a different requirement: 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 cannot by itself validate the proposed trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
B:In this production compliance review context, 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 trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
C:In this production compliance review context, Historical usage matches billed and recorded account activity after the documented latency window has elapsed. This is an outcome for a different requirement: Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. It cannot by itself validate the proposed trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
Question 241
[Pipeline incident investigation] 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 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.
- Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
- Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
Explanation
Correct Answer
A:The discriminating technical reason is: Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies. This directly undermines dynamic table downstream freshness in the specified context.
Incorrect Answers
B:That is a mistake for a different dynamic table declarative refresh task, where A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. Under pipeline incident investigation conditions, Assume a dynamic table is updated instantly on every source write regardless of its refresh behavior and target lag.
C:That is a mistake for a different table stage file landing task, where 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. Under pipeline incident investigation conditions, Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
D:Under pipeline incident investigation conditions, Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
Question 242
[Pipeline incident investigation] A reviewer recommends: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
- Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
- Named internal stages support managed file staging and reusable load references across authorized sessions.
- A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
Explanation
Correct Answer
B:In this pipeline incident investigation context, Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently. The recommendation is linked to observable evidence for this exact case: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns snowpipe file event auto ingest, not the requirement in this case. It does not justify the specific task scheduled orchestration action or its validation path: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
C:That option concerns named internal stage for file reuse, not the requirement in this case. Named internal stages support managed file staging and reusable load references across authorized sessions.
D:That option concerns sql udf reusable expression, not the requirement in this case. A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
Question 243
[Pipeline incident investigation] The team proposes: Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files. Its actual requirement is: 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 observation most directly validates success?
- The exported object files have the expected schema, row counts, and authorized destination path.
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
Explanation
Correct Answer
C:LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows. This is an outcome test of the specified named internal stage for file reuse action under the pipeline incident investigation conditions. Named internal stages support managed file staging and reusable load references across authorized sessions.
Incorrect Answers
A:The exported object files have the expected schema, row counts, and authorized destination path. This is an outcome for a different requirement: A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. It cannot by itself validate the proposed named internal stage for file reuse action; the appropriate test is: LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
B:In this pipeline incident investigation 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 named internal stage for file reuse action; the appropriate test is: LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
D:In this pipeline incident investigation context, A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome for a different requirement: 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 cannot by itself validate the proposed named internal stage for file reuse action; the appropriate test is: LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
Question 244
[Peak traffic performance incident] A reviewer recommends: Account for local warehouse data-cache loss across suspension, and test steady-state cost/performance without assuming persistence. The requirement remains: A BI engineer is investigating the exact bottleneck observed under production-like load. A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
- Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
- Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage.
Explanation
Correct Answer
D:In this peak traffic performance incident context, Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage. The recommendation is linked to observable evidence for this exact case: Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
B:Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
C:That option concerns durable database storage separation, not the requirement in this case. That explanation applies to a different durable database storage separation problem: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased.
Question 245
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
Explanation
Correct Answer
A:Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables. In this production migration readiness setting, the intended validation is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
Incorrect Answers
B:That action is relevant when A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It is not the primary action for the stated hybrid table transactional access need.
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. It is not the primary action for the stated hybrid table transactional access need.
D:That action is relevant when A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It is not the primary action for the stated hybrid table transactional access need.
Question 246
[Identity and governance change request] The team proposes: Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
- A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
Explanation
Correct Answer
B:Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading. This is an outcome test of the specified least-privilege read role action under the identity and governance change request conditions.
Incorrect Answers
A:In this identity and governance change request context, SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations. This is an outcome for a different requirement: A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It cannot by itself validate the proposed least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
C:In this identity and governance change request context, Both analysts resolve the same fully qualified table after aligning role permissions and namespace context. This is an outcome for a different requirement: Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. It cannot by itself validate the proposed least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
D:In this identity and governance change request 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 least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
Question 247
[Architecture planning workshop] The team proposes: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. Its actual requirement is: An internal platform architecture group is assessing the initial design. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
- Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
- Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
- A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage.
Explanation
Correct Answer
C: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 architecture planning workshop 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 architecture planning workshop 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.
B:In this architecture planning workshop 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.
D:In this architecture planning workshop context, A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage. This is an outcome for a different requirement: A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. 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 248
[Production migration readiness] A reviewer recommends: Inspect the active role's grants and cloud-services authorization path instead of resizing compute. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Key-pair authentication supports service access while avoiding hard-coded interactive user passwords, subject to secure private-key handling.
- MFA protects interactive sign-in beyond knowledge of a single password; it is separate from table permissions.
- Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
Explanation
Correct Answer
D:In this production migration readiness context, Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges. The recommendation is linked to observable evidence for this exact case: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns workload identity key-pair authentication, not the requirement in this case. That explanation applies to a different workload identity key-pair authentication problem: An unattended ingestion service needs noninteractive authentication without embedding an employee's reusable password into scripts.
B:That option concerns multifactor authentication enrollment, not the requirement in this case. It does not justify the specific cloud services authentication boundary action or its validation path: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
C:That option concerns cross-region snowflake account planning, not the requirement in this case. It does not justify the specific cloud services authentication boundary action or its validation path: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
Question 249
[Peak traffic performance incident] The team proposes: Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
Explanation
Correct Answer
A:Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. This is an outcome test of the specified warehouse sizing performance experiment action under the peak traffic performance incident conditions. Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
Incorrect Answers
B:In this peak traffic performance incident context, Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. This is an outcome for a different requirement: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It cannot by itself validate the proposed warehouse sizing performance experiment action; the appropriate test is: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
C:In this peak traffic performance incident context, Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome for a different requirement: A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It cannot by itself validate the proposed warehouse sizing performance experiment action; the appropriate test is: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
D:It cannot by itself validate the proposed warehouse sizing performance experiment action; the appropriate test is: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
Question 250
[Production compliance review] The team proposes: Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. A sandbox warehouse is used for unpredictable experiments and a manager needs credit alerts and a suspension threshold for that warehouse. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
- Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
Explanation
Correct Answer
B:Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds. This is an outcome test of the specified resource monitor warehouse budgeting action under the production compliance review conditions. Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges.
Incorrect Answers
A:In this production compliance review context, Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. This is an outcome for a different requirement: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It cannot by itself validate the proposed resource monitor warehouse budgeting action; the appropriate test is: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
C:In this production compliance review context, Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome for a different requirement: A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It cannot by itself validate the proposed resource monitor warehouse budgeting action; the appropriate test is: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
D:In this production compliance review context, Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. This is an outcome for a different requirement: A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It cannot by itself validate the proposed resource monitor warehouse budgeting action; the appropriate test is: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.