Snowflake SnowPro Core COF-C03 Practice Test 2
Question 10
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create a secure direct share for eligible objects and grant it to the approved consumer account under supported region and cloud conditions.
- Evaluate and provision a Snowflake reader account with authorized shares and documented provider billing responsibilities.
- Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
- Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
Explanation
Correct Answer
B:Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls. In this partner onboarding review setting, the intended validation is: The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
Incorrect Answers
A:It is not the primary action for the stated reader account for external consumer need.
C:That action is relevant when 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 is not the primary action for the stated reader account for external consumer need.
D:That action is relevant when A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It is not the primary action for the stated reader account for external consumer need.
Question 11
[Collaboration operating audit] A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
- Create a supported zero-copy clone of the database or selected schema and track later divergence.
- Use zero-copy cloning for an authorized internal copy and distinguish it from a cross-account secure share.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
Explanation
Correct Answer
C:Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption. In this collaboration operating audit 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 multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. 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. It is not the primary action for the stated zero-copy clone lifecycle in collaboration 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 zero-copy clone lifecycle in collaboration need.
Question 12
[Production migration readiness] The team proposes: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage.
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- 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 production migration readiness 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 production migration readiness 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.
B: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 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 production migration readiness 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 13
[Architecture planning workshop] A reviewer recommends: Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection. The requirement remains: An internal platform architecture group is assessing the initial design. An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
- Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
Explanation
Correct Answer
A:In this architecture planning workshop context, Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees. The recommendation is linked to observable evidence for this exact case: Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns hybrid table transactional access, not the requirement in this case. That explanation applies to a different hybrid table transactional access problem: A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design.
C:That option concerns transient staging table lifecycle, not the requirement in this case. Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
D:That option concerns time travel historical query, not the requirement in this case. Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
Question 14
[Architecture planning workshop] A reviewer recommends: Evaluate the Business Critical or otherwise eligible edition and configure a supported private connectivity option for its cloud. The requirement remains: An internal platform architecture group is assessing the initial design. A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Private connectivity and enhanced security functionality have edition and cloud prerequisites that must be verified independently of ordinary RBAC.
- Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
Explanation
Correct Answer
B:In this architecture planning workshop 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 jdbc or odbc application connection, not the requirement in this case. That explanation applies to a different jdbc or odbc application connection problem: A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity.
C:That option concerns private network endpoint verification, not the requirement in this case. That explanation applies to a different private network endpoint verification problem: A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints.
D:That option concerns cloud services authentication boundary, not the requirement in this case. Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
Question 15
[Production compliance review] 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 Snowflake action best meets this specific requirement?
- Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Use a managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS.
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
Explanation
Correct Answer
C:Managed access centralizes grant management and changes who can authorize privileges on contained objects. In this production compliance review setting, the intended validation is: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
Incorrect Answers
A: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 managed access schema grants need.
B: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. It is not the primary action for the stated managed access schema grants need.
D:That action is relevant when A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It is not the primary action for the stated managed access schema grants need.
Question 16
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. An organization must restrict logins to approved corporate egress ranges even when credentials are correct. 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 labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
- Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
- Pass an arbitrary object-stage URL as a database hostname and expect it to authenticate like the Snowflake SQL endpoint.
- Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
Explanation
Correct Answer
D:The discriminating technical reason is: Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy. Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
Incorrect Answers
A:That is a mistake for a different automated sensitive-data classification task, where A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. Under production compliance review conditions, Assume labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
B:That is a mistake for a different row access policy filtering task, where Regional managers share a table but must see only the geographic rows permitted by their assigned region. Under production compliance review conditions, Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
C:That is a mistake for a different jdbc or odbc application connection task, where A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. Under production compliance review conditions, Pass an arbitrary object-stage URL as a database hostname and expect it to authenticate like the Snowflake SQL endpoint.
Question 17
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect the active role's grants and cloud-services authorization path instead of resizing compute.
- Evaluate the Business Critical or otherwise eligible edition and configure a supported private connectivity option for its cloud.
- Publish an appropriately designed secure view and grant only the needed access to the consumer role.
- Use an appropriately supported programmatic identity with managed key-pair authentication and rotation controls.
Explanation
Correct Answer
A:Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges. In this post-rollout service review setting, the intended validation is: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
Incorrect Answers
B:That action is relevant when A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. It is not the primary action for the stated cloud services authentication boundary need.
C:That action is relevant when A data provider must hide sensitive query definition details while exposing a restricted projection of source data to consumers. It is not the primary action for the stated cloud services authentication boundary 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 cloud services authentication boundary need.
Question 18
[Production cutover rehearsal] The team proposes: Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
- Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Explanation
Correct Answer
B:End-to-end event timestamps show data arriving within the required streaming latency under peak event load. This is an outcome test of the specified snowpipe streaming low latency action under the production cutover rehearsal conditions. Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
Incorrect Answers
A:In this production cutover rehearsal 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 snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
C:A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY. This is an outcome for a different requirement: Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. It cannot by itself validate the proposed snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
D:In this production cutover rehearsal context, Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart. This is an outcome for a different requirement: A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. It cannot by itself validate the proposed snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
Question 19
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
- 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.
- Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
Explanation
Correct Answer
C:A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Incorrect Answers
A: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 reusable csv file format need.
B:That action is relevant when A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It is not the primary action for the stated reusable csv file format need.
D:That action is relevant when Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. It is not the primary action for the stated reusable csv file format need.
Question 20
[Production cutover rehearsal] A reviewer recommends: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it. The requirement remains: A data integration group runs a controlled replay with representative files or events. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Named internal stages support managed file staging and reusable load references across authorized sessions.
- Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
Explanation
Correct Answer
D:In this production cutover rehearsal 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 named internal stage for file reuse, 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.
B:That option concerns stored procedure multi-step operation, not the requirement in this case. That explanation applies to a different stored procedure multi-step operation problem: An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation.
C:That option concerns table stage file landing, not the requirement in this case. A table stage gives a convenient table-associated internal landing location without creating a separate named stage.