Snowflake SnowPro Core COF-C03 Practice Test 12
Question 110
[Pipeline incident investigation] The team proposes: Use a supported API integration and external function pattern after confirming cloud/platform and security requirements. Its actual requirement is: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. 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.
- A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
- A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
Explanation
Correct Answer
B:A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions. This is an outcome test of the specified external function api integration action under the pipeline incident investigation conditions. API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
Incorrect Answers
A:In this pipeline incident investigation 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 external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
C:A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible. This is an outcome for a different requirement: A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. It cannot by itself validate the proposed external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
D:In this pipeline incident investigation context, The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider. This is an outcome for a different requirement: A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It cannot by itself validate the proposed external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
Question 111
[Security control assessment] A reviewer recommends: Configure a supported federated SSO security integration and verify identity, certificates, and account routing. The requirement remains: A quarterly access-control audit requires an evidence-backed answer. An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
- System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
- Federated authentication delegates sign-in to the organization's identity provider while object access still depends on Snowflake roles.
- Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
Explanation
Correct Answer
C:In this security control assessment context, Federated authentication delegates sign-in to the organization's identity provider while object access still depends on Snowflake roles. The recommendation is linked to observable evidence for this exact case: A test user signs in through the approved identity provider and receives only the expected Snowflake role access. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns external stage cloud identity integration, not the requirement in this case. It does not justify the specific federated single sign-on action or its validation path: A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
B:That option concerns custom roles versus system roles, not the requirement in this case. That explanation applies to a different custom roles versus system roles problem: A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses.
D:That option concerns reader account for external consumer, not the requirement in this case. It does not justify the specific federated single sign-on action or its validation path: A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
Question 112
[Optimization regression test] A reviewer recommends: Use Snowflake PIVOT on the supported aggregation and quarter categories or an equivalent conditional aggregate. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
- Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
- Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
- PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
Explanation
Correct Answer
D:In this optimization regression test context, PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records. The recommendation is linked to observable evidence for this exact case: A validated report has one region row and expected quarter columns with reconciled totals. 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. That explanation applies to a different merge keyed upsert problem: A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table.
B:That option concerns cross-region data listing fulfillment, not the requirement in this case. It does not justify the specific pivot aggregate into columns action or its validation path: A validated report has one region row and expected quarter columns with reconciled totals.
C:That option concerns cross-region snowflake account planning, not the requirement in this case. It does not justify the specific pivot aggregate into columns action or its validation path: A validated report has one region row and expected quarter columns with reconciled totals.
Question 113
[Identity and governance change request] 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 governance team is evaluating a controlled policy rollout without relaxing unrelated account access. 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 release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- 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 TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Explanation
Correct Answer
A: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 identity and governance change request conditions. Managed access centralizes grant management and changes who can authorize privileges on contained objects.
Incorrect Answers
B:In this identity and governance change request 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.
C: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 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 identity and governance change request 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 114
[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 specific design mistake would most directly defeat the intended result?
- Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
- Call collect on the entire raw table first and assume all later dataframe operations still execute inside Snowflake.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
- Download the entire confidential source table to a local pandas session before applying a simple supported projection.
Explanation
Correct Answer
B:The discriminating technical reason is: Snowpark can execute supported transformations near governed data; eager client collection changes scale and exposure risks. This directly undermines snowpark transformation pushdown verification in the specified context.
Incorrect Answers
A:That is a mistake for a different private network endpoint verification task, where A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. Under peak traffic performance incident conditions, Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
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 peak traffic performance incident conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
D:That is a mistake for a different snowpark python pushdown task, where A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. Under peak traffic performance incident conditions, Download the entire confidential source table to a local pandas session before applying a simple supported projection.
Question 115
[Query performance review] A performance engineer is benchmarking representative queries before accepting changes. A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
- Assume adding a conventional user-managed B-tree index is the only way Snowflake can prune native tables.
- Strip all JSON structure to a single concatenated string and assume nested numeric comparisons work without parsing.
- Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT.
Explanation
Correct Answer
C:The discriminating technical reason is: VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data. This directly undermines variant semi-structured access in the specified context.
Incorrect Answers
A: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 query performance review conditions, Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
B: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. Under query performance review conditions, Assume adding a conventional user-managed B-tree index is the only way Snowflake can prune native tables.
D: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. Under query performance review conditions, Use MERGE to rewrite base table records as the only available method for a cross-tab SELECT.
Question 116
[Post-rollout service review] The team proposes: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
- Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
- Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
- The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
Explanation
Correct Answer
D:The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. This is an outcome test of the specified transient staging table lifecycle action under the post-rollout service review conditions. Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
Incorrect Answers
A:A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed transient staging table lifecycle action; the appropriate test is: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
B:In this post-rollout service review context, Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target. This is an outcome for a different requirement: A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It cannot by itself validate the proposed transient staging table lifecycle action; the appropriate test is: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
C:Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. This is an outcome for a different requirement: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It cannot by itself validate the proposed transient staging table lifecycle action; the appropriate test is: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
Question 117
[Ingestion design acceptance] A reviewer recommends: Run COPY INTO with an appropriate VALIDATION_MODE or targeted preflight to inspect errors before committing the production load. The requirement remains: A data engineering team is checking the design before promoting a pipeline. A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
Explanation
Correct Answer
A:In this ingestion design acceptance context, Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation. The recommendation is linked to observable evidence for this exact case: Validation output identifies the same malformed records that can be corrected before the final committed load. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns load idempotence and history, not the requirement in this case. It does not justify the specific copy into validation preflight action or its validation path: Validation output identifies the same malformed records that can be corrected before the final committed load.
C:That option concerns table stage file landing, not the requirement in this case. It does not justify the specific copy into validation preflight action or its validation path: Validation output identifies the same malformed records that can be corrected before the final committed load.
D:That option concerns zero-copy clone lifecycle in collaboration, not the requirement in this case. It does not justify the specific copy into validation preflight action or its validation path: Validation output identifies the same malformed records that can be corrected before the final committed load.
Question 118
[Post-rollout service review] A reviewer recommends: Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
- Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
Explanation
Correct Answer
B:In this post-rollout service review context, Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums. The recommendation is linked to observable evidence for this exact case: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns multi-cluster concurrency scaling, not the requirement in this case. Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
C:That option concerns warehouse sizing performance experiment, not the requirement in this case. It does not justify the specific warehouse auto-suspend economics action or its validation path: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
D:That option concerns warehouse scale-up for complex query, not the requirement in this case. That explanation applies to a different warehouse scale-up for complex query problem: A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero.
Question 119
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Write one object-storage CSV per row and assume ordinary hourly COPY INTO is a direct streaming interface.
- Choose a conventional analytical external table and expect the same transactional constraints and row update behavior.
- Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
- Use Cortex Search as though it alone provides a certified semantic definition of revenue aggregations in every structured table.
Explanation
Correct Answer
C:The supportable direction is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. This directly undermines cortex search document retrieval in the specified context.
Incorrect Answers
A:That is a mistake for a different snowpipe streaming low latency task, where An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It does not directly defeat the present cortex search document retrieval requirement, whose proper treatment is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
B:That is a mistake for a different hybrid table transactional access task, where A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It does not directly defeat the present cortex search document retrieval requirement, whose proper treatment is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
D:That is a mistake for a different cortex analyst structured nl-to-sql task, where Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It does not directly defeat the present cortex search document retrieval requirement, whose proper treatment is: Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
Question 120
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources.
- Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
Explanation
Correct Answer
D:Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access. In this post-rollout service review setting, the intended validation is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
Incorrect Answers
A:That action is relevant when A SQL worksheet needs a scratch table only for calculations performed in a single session and must not expose it as a durable shared object. Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect.
B: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. Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
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 snowsight analyst interface need.