Snowflake SnowPro Core COF-C03 Practice Test 7
Question 60
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
- Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection.
- Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources.
- Use Snowflake Time Travel AT or BEFORE syntax with a valid historical reference for the affected table.
Explanation
Correct Answer
D:Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. In this architecture planning workshop setting, the intended validation is: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
Incorrect Answers
A:That action is relevant when A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. It is not the primary action for the stated time travel historical query need.
B:That action is relevant when An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It is not the primary action for the stated time travel historical query need.
C:That action is relevant when A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It is not the primary action for the stated time travel historical query need.
Question 61
[Pipeline incident investigation] A reviewer recommends: Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
- Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
Explanation
Correct Answer
A:In this pipeline incident investigation context, Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. The recommendation is linked to observable evidence for this exact case: Load history and target counts confirm expected files were not ingested twice after simulated network retry. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns copy into validation preflight, not the requirement in this case. Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
C:That option concerns reusable csv file format, not the requirement in this case. It does not justify the specific load idempotence and history action or its validation path: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
D:That option concerns copy into location for unload, not the requirement in this case. Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
Question 62
[Production compliance review] The team proposes: Use a managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
- A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Explanation
Correct Answer
B:A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can. This is an outcome test of the specified managed access schema grants action under the production compliance review conditions. Managed access centralizes grant management and changes who can authorize privileges on contained objects.
Incorrect Answers
A:Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities. This is an outcome for a different requirement: A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. It cannot by itself validate the proposed managed access schema grants action; the appropriate test is: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
C: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 managed access schema grants action; the appropriate test is: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
D:In this production compliance review context, SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome for a different requirement: A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. It cannot by itself validate the proposed managed access schema grants action; the appropriate test is: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
Question 63
[Pipeline incident investigation] A reviewer recommends: Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- 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.
- Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
- Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
Explanation
Correct Answer
C:In this pipeline incident investigation context, Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file. The recommendation is linked to observable evidence for this exact case: End-to-end event timestamps show data arriving within the required streaming latency under peak event load. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns table stage file landing, not the requirement in this case. It does not justify the specific snowpipe streaming low latency action or its validation path: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
B:That option concerns reusable csv file format, not the requirement in this case. It does not justify the specific snowpipe streaming low latency action or its validation path: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
D:That option concerns hybrid table transactional access, not the requirement in this case. It does not justify the specific snowpipe streaming low latency action or its validation path: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
Question 64
[Architecture planning workshop] The team proposes: Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency. Its actual requirement is: An internal platform architecture group is assessing the initial design. During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely.
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
Explanation
Correct Answer
D:Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable. This is an outcome test of the specified multi-cluster concurrency scaling action under the architecture planning workshop conditions. Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
Incorrect Answers
A:In this architecture planning workshop context, 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 multi-cluster concurrency scaling action; the appropriate test is: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
B:The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely. This is an outcome for a different requirement: An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. It cannot by itself validate the proposed multi-cluster concurrency scaling action; the appropriate test is: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
C:In this architecture planning workshop context, The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed. This is an outcome for a different requirement: An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It cannot by itself validate the proposed multi-cluster concurrency scaling action; the appropriate test is: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
Question 65
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. 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?
- Set a masking policy on a table column and assume that supplies a second authentication factor at login.
- Store an administrator's plaintext password in every CI job and assume a network policy makes it equivalent to key authentication.
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
Explanation
Correct Answer
A:The discriminating technical reason is: MFA protects interactive sign-in beyond knowledge of a single password; it is separate from table permissions. This directly undermines multifactor authentication enrollment in the specified context.
Incorrect Answers
B:That is a mistake for a different workload identity key-pair authentication task, where An unattended ingestion service needs noninteractive authentication without embedding an employee's reusable password into scripts. Under identity and governance change request conditions, Store an administrator's plaintext password in every CI job and assume a network policy makes it equivalent to key authentication.
C:That is a mistake for a different dynamic data masking policy task, where A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It does not directly defeat the present multifactor authentication enrollment requirement, whose proper treatment is: Enforce and verify appropriate Snowflake MFA or federated IdP MFA controls according to the active policy.
D:That is a mistake for a different cloud services authentication boundary task, where An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. Under identity and governance change request conditions, Increase warehouse size repeatedly without checking role grants or the denied object privilege.
Question 66
[Production migration readiness] A reviewer recommends: Evaluate the Business Critical or otherwise eligible edition and configure a supported private connectivity option for its cloud. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
- Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
Explanation
Correct Answer
B:In this production migration readiness context, Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC. The recommendation is linked to observable evidence for this exact case: The account's edition and configured private endpoint show a private connection path, and network tests reject unintended access. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns cloud services authentication boundary, not the requirement in this case. That explanation applies to a different cloud services authentication boundary problem: An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity.
C:That option concerns jdbc or odbc application connection, not the requirement in this case. Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
D:That option concerns enterprise edition feature selection, not the requirement in this case. That explanation applies to a different enterprise edition feature selection problem: A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities.
Question 67
[Architecture planning workshop] A reviewer recommends: Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period. The requirement remains: An internal platform architecture group is assessing the initial design. A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection.
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
- Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
Explanation
Correct Answer
C:In this architecture planning workshop context, Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window. The recommendation is linked to observable evidence for this exact case: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns qualify after window expression, not the requirement in this case. It does not justify the specific enterprise edition feature selection action or its validation path: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
B:That option concerns account and schema object hierarchy, not the requirement in this case. It does not justify the specific enterprise edition feature selection action or its validation path: Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
D:That option concerns business critical private connectivity, not the requirement in this case. Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
Question 68
[Architecture planning workshop] The team proposes: Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration. Its actual requirement is: An internal platform architecture group is assessing the initial design. A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Query history shows the pushed-down SQL and only a bounded intended result is fetched to the local client.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
- The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.
Explanation
Correct Answer
D:The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test. This is an outcome test of the specified snowpark optimized workload isolation action under the architecture planning workshop conditions. Snowpark-optimized warehouses provide a higher memory profile that can help memory-intensive Snowpark computations, subject to the workload's actual bottleneck.
Incorrect Answers
A:In this architecture planning workshop context, Query history shows the pushed-down SQL and only a bounded intended result is fetched to the local client. This is an outcome for a different requirement: Python engineers built Snowpark DataFrame transformations and want to avoid accidental collection of millions of protected records to a laptop. It cannot by itself validate the proposed snowpark optimized workload isolation action; the appropriate test is: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.
B:In this architecture planning workshop 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 snowpark optimized workload isolation action; the appropriate test is: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.
C:In this architecture planning workshop context, Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results. This is an outcome for a different requirement: A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. It cannot by itself validate the proposed snowpark optimized workload isolation action; the appropriate test is: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.
Question 69
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files.
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
Explanation
Correct Answer
A:Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. In this ingestion design acceptance setting, the intended validation is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
Incorrect Answers
B: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 load idempotence and history need.
C:That action is relevant when A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It is not the primary action for the stated load idempotence and history need.
D: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 load idempotence and history need.
Question 70
[Production migration readiness] The team proposes: Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Explanation
Correct Answer
B:A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings. This is an outcome test of the specified iceberg interoperability decision action under the production migration readiness conditions. Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model.
Incorrect Answers
A:In this production migration readiness context, SELECT against the external table returns staged records after location metadata has been refreshed appropriately. This is an outcome for a different requirement: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It cannot by itself validate the proposed iceberg interoperability decision action; the appropriate test is: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
C: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 iceberg interoperability decision action; the appropriate test is: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
D: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 iceberg interoperability decision action; the appropriate test is: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.