Snowflake SnowPro Core COF-C03 Practice Test 83
Question 820
[Post-rollout service review] The team proposes: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. 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 conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
- Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
- Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
Explanation
Correct Answer
D:Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse. This is an outcome test of the specified independent compute for bi and elt action under the post-rollout service review conditions.
Incorrect Answers
A:In this post-rollout service review 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 independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
B:In this post-rollout service review context, Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable. This is an outcome for a different requirement: During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It cannot by itself validate the proposed independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
C:In this post-rollout service review context, Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data. This is an outcome for a different requirement: A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It cannot by itself validate the proposed independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
Question 821
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design.
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
- Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.
Explanation
Correct Answer
A:Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file. In this ingestion design acceptance setting, the intended validation is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
Incorrect Answers
B:That action is relevant when An analyst must stage a small support file used only to load one existing target table, with no need for a shared named-stage contract. Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
C:That action is relevant when A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
D:That action is relevant when A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. It is not the primary action for the stated snowpipe streaming low latency need.
Question 822
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. 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. 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?
- Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
- Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
- Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
Explanation
Correct Answer
B:The discriminating technical reason is: Temporary tables are session-scoped and suited to disposable intermediate data, unlike persistent shared tables. Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
Incorrect Answers
A:Under architecture planning workshop conditions, Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
C:That is a mistake for a different durable database storage separation task, where An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It does not directly defeat the present temporary session-bound data requirement, whose proper treatment is: Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect.
D:That is a mistake for a different snowsight analyst interface task, where An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. It does not directly defeat the present temporary session-bound data requirement, whose proper treatment is: Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect.
Question 823
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
- Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
Explanation
Correct Answer
C:Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. In this production cutover rehearsal setting, the intended validation is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
Incorrect Answers
A:That action is relevant when A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. It is not the primary action for the stated load idempotence and history need.
B:That action is relevant when One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
D:That action is relevant when A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
Question 824
[Architecture planning workshop] The team proposes: Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects. Its actual requirement is: An internal platform architecture group is assessing the initial design. An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
- Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
- The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
Explanation
Correct Answer
D:The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight. This is an outcome test of the specified snowsight analyst interface action under the architecture planning workshop conditions. Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
Incorrect Answers
A:In this architecture planning workshop context, Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows. This is an outcome for a different requirement: Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
B:In this architecture planning workshop context, Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions. This is an outcome for a different requirement: A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
C:Both analysts resolve the same fully qualified table after aligning role permissions and namespace context. This is an outcome for a different requirement: Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. It cannot by itself validate the proposed snowsight analyst interface action; the appropriate test is: The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
Question 825
[Post-rollout service review] A reviewer recommends: Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
- Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows.
Explanation
Correct Answer
A:In this post-rollout service review context, Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model. The recommendation is linked to observable evidence for this exact case: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
C:It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
D:Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows.
Question 826
[Production compliance review] A reviewer recommends: Define custom least-privilege operational roles and keep broad system roles for controlled administration duties. The requirement remains: 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 explanation best justifies this recommendation?
- Federated authentication delegates sign-in to the organization's identity provider while object access still depends on Snowflake roles.
- System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
- Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition.
- Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles.
Explanation
Correct Answer
B:In this production compliance review context, System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority. The recommendation is linked to observable evidence for this exact case: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That explanation applies to a different federated single sign-on problem: An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords.
C:That option concerns future grants in new schema, not the requirement in this case. It does not justify the specific custom roles versus system roles action or its validation path: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
D:For the production compliance review conditions, Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles. That explanation applies to a different primary and secondary role session problem: 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. It does not justify the specific custom roles versus system roles action or its validation path: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
Question 827
[Production migration readiness] The team proposes: Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. 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. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
- Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
- The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
Explanation
Correct Answer
C:The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends. This is an outcome test of the specified temporary session-bound data action under the production migration readiness conditions. Temporary tables are session-scoped and suited to disposable intermediate data, unlike persistent shared tables.
Incorrect Answers
A:In this production migration readiness context, The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. This is an outcome for a different requirement: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It cannot by itself validate the proposed temporary session-bound data action; the appropriate test is: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
B:In this production migration readiness context, Both analysts resolve the same fully qualified table after aligning role permissions and namespace context. This is an outcome for a different requirement: Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. It cannot by itself validate the proposed temporary session-bound data action; the appropriate test is: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
D:In this production migration readiness 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 temporary session-bound data action; the appropriate test is: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
Question 828
[Security control assessment] The team proposes: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges. Its actual requirement is: A quarterly access-control audit requires an evidence-backed answer. Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A relevant finding changes state after the corrective configuration and a refreshed review or scan.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
Explanation
Correct Answer
D:Historical usage matches billed and recorded account activity after the documented latency window has elapsed. This is an outcome test of the specified account_usage audit latency action under the security control assessment conditions. Account usage views support historical auditing but can lag live activity; they are distinct from instant session state.
Incorrect Answers
A:In this security control assessment context, A relevant finding changes state after the corrective configuration and a refreshed review or scan. This is an outcome for a different requirement: A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. It cannot by itself validate the proposed account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
B:In this security control assessment context, 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 account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
C:In this security control assessment context, End-to-end event timestamps show data arriving within the required streaming latency under peak event load. This is an outcome for a different requirement: An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It cannot by itself validate the proposed account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
Question 829
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. The conclusion must be justified with observable verification rather than an undocumented assumption. Which 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.
- Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
- Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
- Create a SQL file format object alone and assume it becomes a running Kafka consumer.
Explanation
Correct Answer
A:The discriminating technical reason is: Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file. Write one object-storage CSV per row and assume ordinary hourly COPY INTO is a direct streaming interface.
Incorrect Answers
B:Under production cutover rehearsal conditions, Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
C:That is a mistake for a different snowpipe file event auto ingest task, where Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. Under production cutover rehearsal conditions, Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
D:That is a mistake for a different kafka connector topic ingestion task, where A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. Under production cutover rehearsal conditions, Create a SQL file format object alone and assume it becomes a running Kafka consumer.
Question 830
[Production migration readiness] A reviewer recommends: Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
- Snowpark-optimized warehouses provide a higher memory profile that can help memory-intensive Snowpark computations, subject to the workload's actual bottleneck.
- Snowpark can execute supported transformations near governed data; eager client collection changes scale and exposure risks.
- Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
Explanation
Correct Answer
B:In this production migration readiness context, Snowpark-optimized warehouses provide a higher memory profile that can help memory-intensive Snowpark computations, subject to the workload's actual bottleneck. The recommendation is linked to observable evidence for this exact case: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the production migration readiness conditions, Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits. That explanation applies to a different warehouse sizing performance experiment problem: A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It does not justify the specific snowpark optimized workload isolation action or its validation path: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.
C:Snowpark can execute supported transformations near governed data; eager client collection changes scale and exposure risks.
D:That option concerns warehouse auto-suspend economics, not the requirement in this case. It does not justify the specific snowpark optimized workload isolation action or its validation path: The pipeline completes with acceptable spill, runtime, and compute spend after a like-for-like resource test.