Snowflake SnowPro Core COF-C03 Practice Test 32
Question 310
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. 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?
- Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
- Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Explanation
Correct Answer
B:The supportable direction is: Configure an authorized storage integration and external stage with the required cloud trust and path restrictions. The discriminating technical reason is: Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
Incorrect Answers
A:That is a mistake for a different external function api integration task, where A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. Under pipeline incident investigation conditions, Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
C: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 pipeline incident investigation conditions, Increase warehouse size repeatedly without checking role grants or the denied object privilege.
D:Under pipeline incident investigation conditions, Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files. That is a mistake for a different copy into location for unload task, where A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job.
Question 311
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
- Inspect the active role's grants and cloud-services authorization path instead of resizing compute.
- Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials.
- Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
Explanation
Correct Answer
C:Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles. In this production migration readiness setting, the intended validation is: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
Incorrect Answers
A:That action is relevant when An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. It is not the primary action for the stated snowflake cli reproducible developer work need.
B:It is not the primary action for the stated snowflake cli reproducible developer work need. That action is relevant when An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity.
D: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 snowflake cli reproducible developer work need.
Question 312
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A sandbox warehouse is used for unpredictable experiments and a manager needs credit alerts and a suspension threshold for that warehouse. 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?
- Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
- Assume a warehouse resource monitor automatically prevents every possible Snowflake storage and serverless service charge.
Explanation
Correct Answer
D:The supportable direction is: Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers. The discriminating technical reason is: Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges.
Incorrect Answers
A:That is a mistake for a different warehouse scale-up for complex query task, where A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. Under identity and governance change request conditions, Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
B:That is a mistake for a different managed access schema grants task, where A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. Under identity and governance change request conditions, Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
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 identity and governance change request conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
Question 313
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
- Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage.
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
Explanation
Correct Answer
A:Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
Incorrect Answers
B:That action is relevant when A retailer's nightly ELT job saturates compute while an unrelated dashboard must keep predictable query latency; both workloads read the same sales tables. Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
C:That action is relevant when Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. It is not the primary action for the stated persisted result reuse conditions need.
D:That action is relevant when A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It is not the primary action for the stated persisted result reuse conditions need.
Question 314
[Collaboration operating audit] A reviewer recommends: Evaluate a Snowflake Data Clean Room with approved collaboration templates and privacy controls for the intended aggregate analysis. The requirement remains: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. Two advertisers want to calculate joint audience overlap while preventing either company from freely inspecting the other's raw person-level records. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Private collaboration environments govern which organizations can discover and share listings beyond simple public marketplace exposure.
- Data Clean Rooms enable governed joint analytics with protections around raw participant data and supported query results.
- Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Explanation
Correct Answer
B:In this collaboration operating audit context, Data Clean Rooms enable governed joint analytics with protections around raw participant data and supported query results. The recommendation is linked to observable evidence for this exact case: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns private data exchange collaboration, not the requirement in this case. It does not justify the specific privacy-preserving data clean room action or its validation path: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
C:Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
D:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific privacy-preserving data clean room action or its validation path: The approved overlap result returns only permitted aggregate metrics and tests reject prohibited raw-identifier disclosures.
Question 315
[Pipeline incident investigation] The team proposes: Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design. Its actual requirement is: 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 observation most directly validates success?
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Explanation
Correct Answer
C: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 pipeline incident investigation 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 pipeline incident investigation context, A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome for a different requirement: One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. It cannot by itself validate the proposed 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.
B:Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome for a different requirement: A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. 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 pipeline incident investigation 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 316
[Security control assessment] A reviewer recommends: Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation. The requirement remains: A quarterly access-control audit requires an evidence-backed answer. A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
- Managed access centralizes grant management and changes who can authorize privileges on contained objects.
- 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.
Explanation
Correct Answer
D:In this security control assessment context, 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. The recommendation is linked to observable evidence for this exact case: Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns merge keyed upsert, not the requirement in this case. It does not justify the specific customer-managed encryption key option action or its validation path: Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
B:That option concerns dynamic data masking policy, not the requirement in this case. It does not justify the specific customer-managed encryption key option action or its validation path: Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
C:That option concerns managed access schema grants, not the requirement in this case. It does not justify the specific customer-managed encryption key option action or its validation path: Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
Question 317
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. Python engineers built Snowpark DataFrame transformations and want to avoid accidental collection of millions of protected records to a laptop. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Keep supported DataFrame operations in Snowflake and inspect query execution before invoking local collect operations.
- Use the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings.
- Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration.
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
Explanation
Correct Answer
A:Snowpark can execute supported transformations near governed data; eager client collection changes scale and exposure risks. In this peak traffic performance incident setting, the intended validation is: Query history shows the pushed-down SQL and only a bounded intended result is fetched to the local client.
Incorrect Answers
B:That action is relevant when A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. It is not the primary action for the stated snowpark transformation pushdown verification need.
C:That action is relevant when A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. It is not the primary action for the stated snowpark transformation pushdown verification need.
D:That action is relevant when Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. It is not the primary action for the stated snowpark transformation pushdown verification need.
Question 318
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A table contains several rows per customer and an analyst wants exactly the latest row for each customer after computing ROW_NUMBER. 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?
- Create a serverless ingestion pipe and expect it to act as a row-level scalar SQL function in every SELECT.
- Put a window function directly inside a WHERE predicate and assume WHERE executes after window evaluation.
- Assume adding a conventional user-managed B-tree index is the only way Snowflake can prune native tables.
- Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
Explanation
Correct Answer
B:The supportable direction is: Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY. This directly undermines qualify after window expression in the specified context.
Incorrect Answers
A:That is a mistake for a different sql udf reusable expression task, where Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. Under peak traffic performance incident conditions, Create a serverless ingestion pipe and expect it to act as a row-level scalar SQL function in every SELECT.
C:That is a mistake for a different selective filter micro-partition pruning task, where A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table. It does not directly defeat the present qualify after window expression requirement, whose proper treatment is: Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
D:That is a mistake for a different window-function deterministic ranking task, where A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. 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 319
[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 specific design mistake would most directly defeat the intended result?
- Assume ordinary SQL grants automatically create a private cloud endpoint or satisfy infrastructure-level isolation requirements.
- Grant consumers direct ownership of every sensitive base table and rely on a regular view to undo those grants.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
- Store an administrator's plaintext password in every CI job and assume a network policy makes it equivalent to key authentication.
Explanation
Correct Answer
C:The supportable direction is: Inspect the active role's grants and cloud-services authorization path instead of resizing compute. The discriminating technical reason is: Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
Incorrect Answers
A:That is a mistake for a different business critical private connectivity task, where A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. Under post-rollout service review conditions, Assume ordinary SQL grants automatically create a private cloud endpoint or satisfy infrastructure-level isolation requirements.
B:That is a mistake for a different secure view exposure boundary task, where A data provider must hide sensitive query definition details while exposing a restricted projection of source data to consumers. Under post-rollout service review conditions, Grant consumers direct ownership of every sensitive base table and rely on a regular view to undo those grants.
D: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. It does not directly defeat the present cloud services authentication boundary requirement, whose proper treatment is: Inspect the active role's grants and cloud-services authorization path instead of resizing compute.
Question 320
[Collaboration operating audit] The team proposes: Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort. Its actual requirement is: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A production permanent table was dropped within its configured retention period, and an operator needs a self-service recovery plan rather than a support escalation. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
- A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
Explanation
Correct Answer
D:A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. This is an outcome test of the specified time travel versus fail-safe recoverability action under the collaboration operating audit conditions. Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
Incorrect Answers
A:In this collaboration operating audit context, Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. This is an outcome for a different requirement: An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It cannot by itself validate the proposed time travel versus fail-safe recoverability action; the appropriate test is: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
B:In this collaboration operating audit context, Account edition and the table's retention parameter demonstrate a supported value, and a within-window historical read succeeds. This is an outcome for a different requirement: A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. It cannot by itself validate the proposed time travel versus fail-safe recoverability action; the appropriate test is: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
C:A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys. This is an outcome for a different requirement: An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. It cannot by itself validate the proposed time travel versus fail-safe recoverability action; the appropriate test is: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.