Snowflake SnowPro Core COF-C03 Practice Test 62
Question 610
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Keep supported DataFrame operations in Snowflake and inspect query execution before invoking local collect operations.
- Configure the available private connectivity option for the eligible edition and cloud, then validate DNS and routing.
- Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
- Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges.
Explanation
Correct Answer
B:Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions. In this security control assessment setting, the intended validation is: Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
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. It is not the primary action for the stated private network endpoint verification need.
C:That action is relevant when A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
D:It is not the primary action for the stated private network endpoint verification need.
Question 611
[Optimization regression test] The team proposes: Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring. Its actual requirement is: A team is validating a targeted tuning plan against documented workloads and costs. A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
- A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
Explanation
Correct Answer
C:Remote spill bytes and elapsed time decrease on a representative workload after the targeted change. This is an outcome test of the specified remote spill diagnosis action under the optimization regression test conditions. Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time.
Incorrect Answers
A:In this optimization regression test 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 remote spill diagnosis action; the appropriate test is: Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
B:Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. This is an outcome for a different requirement: A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. It cannot by itself validate the proposed remote spill diagnosis action; the appropriate test is: Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
D:In this optimization regression test context, A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data. This is an outcome for a different requirement: A 70-second analytics query has become slow after a schema change, and the team wants to find whether scanning, joining, or spilling dominates its runtime. It cannot by itself validate the proposed remote spill diagnosis action; the appropriate test is: Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
Question 612
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create an appropriate stream on the table and consume its change records transactionally through a downstream process.
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
Explanation
Correct Answer
D:Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage. In this production migration readiness setting, the intended validation is: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
Incorrect Answers
A:That action is relevant when A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. It is not the primary action for the stated dynamic table declarative refresh need.
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. Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
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. Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
Question 613
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Keep data in managed database storage and resume compute only when processing is needed.
- Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
Explanation
Correct Answer
A:The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters. In this production migration readiness setting, the intended validation is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
Incorrect Answers
B:That action is relevant when An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It is not the primary action for the stated durable database storage separation 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. The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
D:That action is relevant when A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Question 614
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Explanation
Correct Answer
B:OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance. In this security control assessment setting, the intended validation is: The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
Incorrect Answers
A:That action is relevant when A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
C:That action is relevant when A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
D:That action is relevant when 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. OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
Question 615
[Production compliance review] The team proposes: Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. 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 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.
- The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
- A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Explanation
Correct Answer
C:A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context. This is an outcome test of the specified primary and secondary role session action under the production compliance review conditions. Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles.
Incorrect Answers
A: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 primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
B:In this production compliance review context, The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends. This is an outcome for a different requirement: A SQL worksheet needs a scratch table only for calculations performed in a single session and must not expose it as a durable shared object. It cannot by itself validate the proposed primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
D: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 primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
Question 616
[Post-rollout service review] The team proposes: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
- Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
- The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
Explanation
Correct Answer
D:Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome test of the specified hybrid table transactional access action under the post-rollout service review conditions. Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
Incorrect Answers
A:In this post-rollout service review context, Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers. This is an outcome for a different requirement: A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
B:In this post-rollout service review context, Separate user-role tests return only the authorized region's row keys while total source data remains unchanged. This is an outcome for a different requirement: Regional managers share a table but must see only the geographic rows permitted by their assigned region. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
C:In this post-rollout service review context, The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. This is an outcome for a different requirement: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
Question 617
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
- Specify a deterministic secondary ordering key in ROW_NUMBER or another suitable window ranking expression.
- Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
- Use an appropriately supported programmatic identity with managed key-pair authentication and rotation controls.
Explanation
Correct Answer
A:MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries. In this peak traffic performance incident setting, the intended validation is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
Incorrect Answers
B:That action is relevant when A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. Specify a deterministic secondary ordering key in ROW_NUMBER or another suitable window ranking expression.
C:That action is relevant when A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. It is not the primary action for the stated merge keyed upsert need.
D:That action is relevant when An unattended ingestion service needs noninteractive authentication without embedding an employee's reusable password into scripts. It is not the primary action for the stated merge keyed upsert need.
Question 618
[Production compliance review] 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 specific design mistake would most directly defeat the intended result?
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
- Assume a warehouse resource monitor automatically prevents every possible Snowflake storage and serverless service charge.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
- Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
Explanation
Correct Answer
B:The supportable direction is: Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers. This directly undermines resource monitor warehouse budgeting in the specified context.
Incorrect Answers
A:It does not directly defeat the present resource monitor warehouse budgeting requirement, whose proper treatment is: Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers.
C:That is a mistake for a different warehouse local data cache task, where A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. Under production compliance review conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
D:That is a mistake for a different warehouse sizing performance experiment task, where A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. Under production compliance review conditions, Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
Question 619
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Leave the warehouse running indefinitely to preserve tables, even when no compute-intensive activity remains.
- Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
- Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
- Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions.
Explanation
Correct Answer
C:The supportable direction is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications. The discriminating technical reason is: Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
Incorrect Answers
A:That is a mistake for a different warehouse auto-suspend economics task, where A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. Under production cutover rehearsal conditions, Leave the warehouse running indefinitely to preserve tables, even when no compute-intensive activity remains.
B:That is a mistake for a different reusable csv file format task, where One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. Under production cutover rehearsal conditions, Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
D:Under production cutover rehearsal conditions, Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions. That is a mistake for a different named internal stage for file reuse task, where A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It does not directly defeat the present snowpipe file event auto ingest requirement, whose proper treatment is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
Question 620
[Pipeline incident investigation] The team proposes: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query. Its actual requirement is: 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 observation most directly validates success?
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
- The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
- Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
- Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
Explanation
Correct Answer
D:Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load. This is an outcome test of the specified dynamic table downstream freshness action under the pipeline incident investigation conditions. Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies.
Incorrect Answers
A:In this pipeline incident investigation context, Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh. This is an outcome for a different requirement: A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
B:In this pipeline incident investigation context, The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests. This is an outcome for a different requirement: A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
C:Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target. This is an outcome for a different requirement: A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.