Snowflake SnowPro Core COF-C03 Practice Test 120
Question 1190
[Architecture planning workshop] A reviewer recommends: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. The requirement remains: An internal platform architecture group is assessing the initial design. A retailer's nightly ELT job saturates compute while an unrelated dashboard must keep predictable query latency; both workloads read the same sales tables. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse.
- Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage.
- 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 architecture planning workshop context, Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse. The recommendation is linked to observable evidence for this exact case: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the architecture planning workshop conditions, Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog. That explanation applies to a different account and schema object hierarchy problem: A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It does not justify the specific independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
C:For the architecture planning workshop conditions, Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage. That explanation applies to a different warehouse local data cache problem: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It does not justify the specific independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
D:For the architecture planning workshop 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 independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
Question 1191
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model.
- Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Use the table's built-in stage where suitable and load into the target using supported commands.
Explanation
Correct Answer
C:Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage. In this post-rollout service review setting, the intended validation is: Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
Incorrect Answers
A:That action is relevant when A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It is not the primary action for the stated dynamic table declarative refresh need.
B:That action is relevant when An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It is not the primary action for the stated dynamic table declarative refresh need.
D:It is not the primary action for the stated dynamic table declarative refresh need.
Question 1192
[Production cutover rehearsal] A reviewer recommends: Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format. The requirement remains: 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 explanation best justifies this recommendation?
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
- Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
- Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time.
- Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
Explanation
Correct Answer
D:In this production cutover rehearsal context, Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files. The recommendation is linked to observable evidence for this exact case: The exported object files have the expected schema, row counts, and authorized destination path. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific copy into location for unload action or its validation path: The exported object files have the expected schema, row counts, and authorized destination path.
B:For the production cutover rehearsal conditions, Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation. That explanation applies to a different copy into validation preflight problem: A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. It does not justify the specific copy into location for unload action or its validation path: The exported object files have the expected schema, row counts, and authorized destination path.
C:That option concerns zero-copy clone for sandbox, not the requirement in this case. It does not justify the specific copy into location for unload action or its validation path: The exported object files have the expected schema, row counts, and authorized destination path.
Question 1193
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Add extra multi-cluster warehouses alone to fix a single query's in-memory hash aggregation spill.
- Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
- Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
- Assume a standard tiny warehouse can execute an arbitrary in-memory dataframe operation regardless of memory demand.
Explanation
Correct Answer
A:The discriminating technical reason is: Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time. Add extra multi-cluster warehouses alone to fix a single query's in-memory hash aggregation spill.
Incorrect Answers
B:It does not directly defeat the present remote spill diagnosis requirement, whose proper treatment is: Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring.
C:Under optimization regression test conditions, Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data. That is a mistake for a different warehouse sizing performance experiment task, where A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It does not directly defeat the present remote spill diagnosis requirement, whose proper treatment is: Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring.
D:That is a mistake for a different snowpark optimized workload isolation task, where A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. Under optimization regression test conditions, Assume a standard tiny warehouse can execute an arbitrary in-memory dataframe operation regardless of memory demand.
Question 1194
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. 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. 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?
- Change only the warehouse's name and assume object ownership follows the newly renamed compute resource.
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
Explanation
Correct Answer
B:The supportable direction is: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Incorrect Answers
A:Under security control assessment conditions, Change only the warehouse's name and assume object ownership follows the newly renamed compute resource.
C:Under security control assessment conditions, Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege. That is a mistake for a different least-privilege read role task, where A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It does not directly defeat the present inherited functional role grants requirement, whose proper treatment is: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
D:Under security control assessment conditions, Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role. That is a mistake for a different custom roles versus system roles task, where A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It does not directly defeat the present inherited functional role grants requirement, whose proper treatment is: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Question 1195
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. 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. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Choose a cross-region or cross-cloud listing and fulfillment configuration supported by their accounts and Snowflake edition.
- 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.
- Inspect the active role's grants and cloud-services authorization path instead of resizing compute.
Explanation
Correct Answer
C:Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration. In this production migration readiness setting, the intended validation is: Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
Incorrect Answers
A:It is not the primary action for the stated cross-region snowflake account planning need.
B:That action is relevant when A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It is not the primary action for the stated cross-region snowflake account planning need.
D: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. It is not the primary action for the stated cross-region snowflake account planning need.
Question 1196
[Provider and consumer workshop] A data collaboration team is defining the permitted provider and consumer relationship. A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. 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?
- Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Assume granting the consumer's account name in a remote region is always identical to a local share without any additional setup.
- Assume CLONE DATABASE in one account silently creates an always-current replica in every other geography.
Explanation
Correct Answer
D:The supportable direction is: Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives. Assume CLONE DATABASE in one account silently creates an always-current replica in every other geography.
Incorrect Answers
A:That is a mistake for a different zero-copy clone lifecycle in collaboration task, where A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. Under provider and consumer workshop conditions, Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
B:Under provider and consumer workshop conditions, Export the entire database to CSV and reload it as the only supported cloning approach.
C:Under provider and consumer workshop conditions, Assume granting the consumer's account name in a remote region is always identical to a local share without any additional setup. That is a mistake for a different cross-region data listing fulfillment task, where 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 does not directly defeat the present replication across regions for availability requirement, whose proper treatment is: Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
Question 1197
[Collaboration operating audit] A reviewer recommends: Evaluate the Snowflake Native App Framework and supported listing or package deployment lifecycle for consumers. The requirement remains: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A software vendor needs to package governed application logic with Snowflake-integrated deployment instead of sending a collection of ad hoc scripts. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
- Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
- Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
- Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
Explanation
Correct Answer
A:In this collaboration operating audit context, Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model. The recommendation is linked to observable evidence for this exact case: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns zero-copy clone lifecycle in collaboration, not the requirement in this case. It does not justify the specific native app distribution to consumers action or its validation path: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
C:Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
D:For the collaboration operating audit conditions, Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access. That explanation applies to a different cross-region data listing fulfillment problem: 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 does not justify the specific native app distribution to consumers action or its validation path: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
Question 1198
[Peak traffic performance incident] A reviewer recommends: Load the payload into a VARIANT column and use supported path extraction and casts for downstream typed calculations. The requirement remains: A BI engineer is investigating the exact bottleneck observed under production-like load. A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine.
- VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
- Partition metadata lets Snowflake skip micro-partitions whose ranges cannot satisfy the filter, but scattered values limit effective pruning.
- PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records.
Explanation
Correct Answer
B:In this peak traffic performance incident context, VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data. The recommendation is linked to observable evidence for this exact case: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the peak traffic performance incident conditions, Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. That explanation applies to a different cortex analyst structured nl-to-sql problem: Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It does not justify the specific variant semi-structured access action or its validation path: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic.
C:For the peak traffic performance incident conditions, Partition metadata lets Snowflake skip micro-partitions whose ranges cannot satisfy the filter, but scattered values limit effective pruning. That explanation applies to a different selective filter micro-partition pruning problem: A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table. It does not justify the specific variant semi-structured access action or its validation path: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic.
D:For the peak traffic performance incident conditions, PIVOT turns categorical row values into output columns, making a cross-tab view rather than merging update records. That explanation applies to a different pivot aggregate into columns problem: 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 justify the specific variant semi-structured access action or its validation path: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic.
Question 1199
[Peak traffic performance incident] A reviewer recommends: Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY. The requirement remains: 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 explanation best justifies this recommendation?
- Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
- A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
- QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection.
- Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
Explanation
Correct Answer
C:In this peak traffic performance incident context, QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection. The recommendation is linked to observable evidence for this exact case: A duplicate-key test returns one newest row per customer with deterministic tie-breaking criteria. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns persisted result reuse conditions, not the requirement in this case. It does not justify the specific qualify after window expression action or its validation path: A duplicate-key test returns one newest row per customer with deterministic tie-breaking criteria.
B:It does not justify the specific qualify after window expression action or its validation path: A duplicate-key test returns one newest row per customer with deterministic tie-breaking criteria.
D:For the peak traffic performance incident conditions, Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window. That explanation applies to a different enterprise edition feature selection problem: A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. It does not justify the specific qualify after window expression action or its validation path: A duplicate-key test returns one newest row per customer with deterministic tie-breaking criteria.
Question 1200
[Production migration readiness] A reviewer recommends: Keep data in managed database storage and resume compute only when processing is needed. The requirement remains: 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 explanation best justifies this recommendation?
- Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Explanation
Correct Answer
D:In this production migration readiness context, The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters. The recommendation is linked to observable evidence for this exact case: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific durable database storage separation action or its validation path: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
B:That option concerns transient staging table lifecycle, not the requirement in this case. It does not justify the specific durable database storage separation action or its validation path: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
C:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific durable database storage separation action or its validation path: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.