Snowflake SnowPro Core COF-C03 Practice Test 111
Question 1100
[Production migration readiness] A reviewer recommends: Configure an external table and its stage/integration and maintain the external file metadata as required. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves.
- Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Explanation
Correct Answer
D:In this production migration readiness context, External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table. The recommendation is linked to observable evidence for this exact case: SELECT against the external table returns staged records after location metadata has been refreshed appropriately. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns directory table unstructured metadata, not the requirement in this case. It does not justify the specific external table over data lake action or its validation path: SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
B:It does not justify the specific external table over data lake action or its validation path: SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
C:That option concerns table stage file landing, not the requirement in this case. It does not justify the specific external table over data lake action or its validation path: SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
Question 1101
[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 specific design mistake would most directly defeat the intended result?
- Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
- Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT.
- Assume every syntactically similar SELECT always reuses cached results even after source tables are modified.
- Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
Explanation
Correct Answer
A:The supportable direction is: Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches. Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
Incorrect Answers
B:Under peak traffic performance incident conditions, Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT. That is a mistake for a different pivot aggregate into columns task, where A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. It does not directly defeat the present merge keyed upsert requirement, whose proper treatment is: Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
C:Under peak traffic performance incident conditions, Assume every syntactically similar SELECT always reuses cached results even after source tables are modified.
D:Under peak traffic performance incident conditions, Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
Question 1102
[Architecture planning workshop] A reviewer recommends: Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency. The requirement remains: 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 explanation best justifies this recommendation?
- Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
- Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
- Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
- Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
Explanation
Correct Answer
B:In this architecture planning workshop context, Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count. The recommendation is linked to observable evidence for this exact case: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the architecture planning workshop conditions, Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums. That explanation applies to a different warehouse auto-suspend economics problem: A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It does not justify the specific multi-cluster concurrency scaling action or its validation path: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
C:For the architecture planning workshop conditions, Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints. 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. It does not justify the specific multi-cluster concurrency scaling action or its validation path: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
D:For the architecture planning workshop conditions, Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency. That explanation applies to a different search optimization selective lookup problem: An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It does not justify the specific multi-cluster concurrency scaling action or its validation path: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
Question 1103
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
- Use ON_ERROR=CONTINUE and call the loaded row count complete without logging the rejected records.
Explanation
Correct Answer
C:The discriminating technical reason is: Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files. Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Incorrect Answers
A:Under production cutover rehearsal conditions, Export the entire database to CSV and reload it as the only supported cloning approach. That is a mistake for a different zero-copy clone for sandbox task, where A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. It does not directly defeat the present copy into location for unload requirement, whose proper treatment is: Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
B:Under production cutover rehearsal conditions, Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
D:That is a mistake for a different copy into error-handling choice task, where A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. Under production cutover rehearsal conditions, Use ON_ERROR=CONTINUE and call the loaded row count complete without logging the rejected records.
Question 1104
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. 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?
- Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Store an administrator's plaintext password in every CI job and assume a network policy makes it equivalent to key authentication.
- Assume every Standard edition account automatically gains a customer-managed key simply by creating a masking policy.
Explanation
Correct Answer
D:The discriminating technical reason is: Tri-Secret Secure combines Snowflake-managed key protection with an eligible customer-managed key model, but it is not enabled just by a SQL grant. Assume every Standard edition account automatically gains a customer-managed key simply by creating a masking policy.
Incorrect Answers
A:That is a mistake for a different merge keyed upsert task, where A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. Under identity and governance change request conditions, Run unconditional INSERT for every retry and rely on order-by formatting to prevent duplicate customer keys.
B: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 customer-managed encryption key option requirement, whose proper treatment is: Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
C: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.
Question 1105
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Run COPY INTO with an appropriate VALIDATION_MODE or targeted preflight to inspect errors before committing the production load.
- 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.
- Select a strict COPY INTO error policy such as ABORT_STATEMENT and reconcile source counts before releasing downstream results.
Explanation
Correct Answer
A:Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation. In this pipeline incident investigation setting, the intended validation is: Validation output identifies the same malformed records that can be corrected before the final committed load. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
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. Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
C:That action is relevant when A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
D:That action is relevant when A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
Question 1106
[Optimization regression test] A reviewer recommends: Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
- Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
- COPY error behavior determines whether load execution aborts or continues past bad rows; strict policy fits completeness-sensitive feeds.
- Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
Explanation
Correct Answer
B:In this optimization regression test context, Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints. The recommendation is linked to observable evidence for this exact case: The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That explanation applies to a different task scheduled orchestration problem: A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable.
C:That explanation applies to a different copy into error-handling choice problem: A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data.
D:For the optimization regression test conditions, Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count. That explanation applies to a different multi-cluster concurrency scaling problem: During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It does not justify the specific stored procedure multi-step operation action or its validation path: The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely.
Question 1107
[Collaboration operating audit] The team proposes: Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance. Its actual requirement is: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
- An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
- Only authorized member organizations see the private listings and permitted data products after membership checks.
- The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
Explanation
Correct Answer
C:Only authorized member organizations see the private listings and permitted data products after membership checks. This is an outcome test of the specified private data exchange collaboration action under the collaboration operating audit conditions. Private collaboration environments govern which organizations can discover and share listings beyond simple public marketplace exposure.
Incorrect Answers
A:In this collaboration operating audit context, Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used. This is an outcome for a different requirement: A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. It cannot by itself validate the proposed private data exchange collaboration action; the appropriate test is: Only authorized member organizations see the private listings and permitted data products after membership checks.
B:In this collaboration operating audit context, An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure. This is an outcome for a different requirement: A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. It cannot by itself validate the proposed private data exchange collaboration action; the appropriate test is: Only authorized member organizations see the private listings and permitted data products after membership checks.
D:In this collaboration operating audit context, The recipient discovers the listing in its region and can read the expected version after fulfillment completes. This is an outcome for a different requirement: A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. It cannot by itself validate the proposed private data exchange collaboration action; the appropriate test is: Only authorized member organizations see the private listings and permitted data products after membership checks.
Question 1108
[Architecture planning workshop] The team proposes: Keep data in managed database storage and resume compute only when processing is needed. Its actual requirement is: An internal platform architecture group is assessing the initial design. An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
Explanation
Correct Answer
D:Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. This is an outcome test of the specified durable database storage separation action under the architecture planning workshop conditions. The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Incorrect Answers
A:In this architecture planning workshop 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 durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
B:In this architecture planning workshop 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 durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
C:In this architecture planning workshop 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 durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
Question 1109
[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 specific design mistake would most directly defeat the intended result?
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
- Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
Explanation
Correct Answer
A:The supportable direction is: Keep data in managed database storage and resume compute only when processing is needed. Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
Incorrect Answers
B:That is a mistake for a different transient staging table lifecycle task, where An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It does not directly defeat the present durable database storage separation requirement, whose proper treatment is: Keep data in managed database storage and resume compute only when processing is needed.
C:That is a mistake for a different zero-copy clone for sandbox task, where A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. Under production migration readiness conditions, Export the entire database to CSV and reload it as the only supported cloning approach.
D: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. It does not directly defeat the present durable database storage separation requirement, whose proper treatment is: Keep data in managed database storage and resume compute only when processing is needed.
Question 1110
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
Explanation
Correct Answer
B:System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority. In this production compliance review setting, the intended validation is: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
Incorrect Answers
A:That action is relevant when A user has an approved reporting role and a separate engineering role but a worksheet unexpectedly lacks SELECT even though the second role has the grant. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
C:That action is relevant when A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
D: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. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.