SnowPro Core COF-C03 Practice Test 81
Question 800
A deployment team has configured this Snowflake capability: Use ROLLUP or supported GROUPING SETS for the required subtotal levels. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The output contains region subtotals and exactly one correct grand total.
- Measured credit use falls within budget while average queueing remains acceptable.
- Records with valid cities are extracted while missing paths do not produce erroneous values.
- The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy.
Explanation
Correct Answer
A:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. The stated acceptance evidence is: The output contains region subtotals and exactly one correct grand total. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:ECONOMY prioritizes fuller use of existing clusters before starting more compute. That explains the role of “Measured credit use falls within budget while average queueing remains acceptable”, but the present requirement calls for “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
C:Path access reads nested semi-structured fields and absent paths require careful NULL semantics. That explains the role of “Records with valid cities are extracted while missing paths do not produce erroneous values”, but the present requirement calls for “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
D:Parsing JSON converts text into structured semi-structured values suitable for path operations. That explains the role of “The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy”, but the present requirement calls for “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
Question 801
A deployment team has configured this Snowflake capability: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Usage views distinguish warehouse credits from storage footprint over the reporting period.
- The team can resize or suspend reporting compute without removing persisted tables.
- The Snowpark job runs on the assigned warehouse and returns the expected transformed row set.
- Queued overload time drops as demand spreads across active clusters.
Explanation
Correct Answer
D:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. The stated acceptance evidence is: Queued overload time drops as demand spreads across active clusters. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. That explains the role of “Usage views distinguish warehouse credits from storage footprint over the reporting period”, but the present requirement calls for “Queued overload time drops as demand spreads across active clusters”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
B:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. That explains the role of “The team can resize or suspend reporting compute without removing persisted tables”, but the present requirement calls for “Queued overload time drops as demand spreads across active clusters”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
C:Snowpark expresses data operations that Snowflake can execute close to governed persisted data. That explains the role of “The Snowpark job runs on the assigned warehouse and returns the expected transformed row set”, but the present requirement calls for “Queued overload time drops as demand spreads across active clusters”: Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
Question 802
A deployment team has configured this Snowflake capability: Implement a governed masking expression that exposes only the permitted suffix. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Usage reporting attributes representative jobs to the intended cost centers.
- A support role sees the approved masked prefix and a privileged role sees the full value.
- The cost audit reconciles all contributing meter categories against the account total.
- After the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
Explanation
Correct Answer
B:Column masking can transform visible values for less-privileged roles without changing stored source values. The stated acceptance evidence is: A support role sees the approved masked prefix and a privileged role sees the full value. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Clear compute ownership and query identification improve chargeback compared with account totals alone. That explains the role of “Usage reporting attributes representative jobs to the intended cost centers”, but the present requirement calls for “A support role sees the approved masked prefix and a privileged role sees the full value”: Column masking can transform visible values for less-privileged roles without changing stored source values.
C:Current warehouse size alone omits runtime, concurrency, and independent serverless consumption. That explains the role of “The cost audit reconciles all contributing meter categories against the account total”, but the present requirement calls for “A support role sees the approved masked prefix and a privileged role sees the full value”: Column masking can transform visible values for less-privileged roles without changing stored source values.
D:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”, but the present requirement calls for “A support role sees the approved masked prefix and a privileged role sees the full value”: Column masking can transform visible values for less-privileged roles without changing stored source values.
Question 803
A deployment team has configured this Snowflake capability: Configure a Snowflake ODBC driver and approved connection profile. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The scheduled report completes and query history records the intended warehouse context.
- An update to the downstream consumer causes the intermediate table to refresh in dependency order.
- Only successfully processed and approved files disappear while failed inputs remain available for review.
- A test file loads expected named fields and no important columns silently become NULL.
Explanation
Correct Answer
A:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. The stated acceptance evidence is: The scheduled report completes and query history records the intended warehouse context. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “An update to the downstream consumer causes the intermediate table to refresh in dependency order”, but the present requirement calls for “The scheduled report completes and query history records the intended warehouse context”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
C:Stage file deletion and data loading are separate governance decisions that require verification. That explains the role of “Only successfully processed and approved files disappear while failed inputs remain available for review”, but the present requirement calls for “The scheduled report completes and query history records the intended warehouse context”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
D:Name-based matching can align supported file columns without depending on file position alone. That explains the role of “A test file loads expected named fields and no important columns silently become NULL”, but the present requirement calls for “The scheduled report completes and query history records the intended warehouse context”: The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
Question 804
A deployment team has configured this Snowflake capability: Use common table expressions with the WITH clause to organize query stages. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The smaller warehouse meets the same reporting targets with fewer credits consumed.
- Authorized users retrieve one test document while unauthorized users are blocked.
- The refactored query returns identical results and execution plan remains acceptable.
- Query Profile uses the view and end-to-end billed cost improves across refresh and reads.
Explanation
Correct Answer
C:CTEs structure intermediate logic for readability while still permitting optimizer planning. The stated acceptance evidence is: The refactored query returns identical results and execution plan remains acceptable. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence. That explains the role of “The smaller warehouse meets the same reporting targets with fewer credits consumed”, but the present requirement calls for “The refactored query returns identical results and execution plan remains acceptable”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
B:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. That explains the role of “Authorized users retrieve one test document while unauthorized users are blocked”, but the present requirement calls for “The refactored query returns identical results and execution plan remains acceptable”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
D:Materialized views store selected precomputed results that can reduce repeated execution work. That explains the role of “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”, but the present requirement calls for “The refactored query returns identical results and execution plan remains acceptable”: CTEs structure intermediate logic for readability while still permitting optimizer planning.
Question 805
A deployment team has configured this Snowflake capability: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Query Profile shows the number of partitions scanned decreases for selective predicates.
- Warehouse history shows suspension during idle periods and automatic restart on new work.
- A recipient can select the authorized shared objects and losing the grant removes further access.
- An approved user opens the Streamlit application and sees current authorized table results.
Explanation
Correct Answer
B:Auto-suspend stops idle compute while auto-resume restarts it for eligible queries. The stated acceptance evidence is: Warehouse history shows suspension during idle periods and automatic restart on new work. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. That explains the role of “Query Profile shows the number of partitions scanned decreases for selective predicates”, but the present requirement calls for “Warehouse history shows suspension during idle periods and automatic restart on new work”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
C:Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset. That explains the role of “A recipient can select the authorized shared objects and losing the grant removes further access”, but the present requirement calls for “Warehouse history shows suspension during idle periods and automatic restart on new work”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
D:Streamlit supports rapid Python application user interfaces with Snowflake-backed data and access controls. That explains the role of “An approved user opens the Streamlit application and sees current authorized table results”, but the present requirement calls for “Warehouse history shows suspension during idle periods and automatic restart on new work”: Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
Question 806
A deployment team has configured this Snowflake capability: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Approved origins connect while an unapproved test origin is denied at the network policy boundary.
- The admin creates a test user and cannot SELECT restricted production data.
- The catalog query finds every scoped object carrying an accepted tag value or a flagged exception.
- SHOW GRANTS TO ROLE shows the expected inherited lower role and successful authorized query.
Explanation
Correct Answer
C:Consistent tag semantics support reliable downstream policy and reporting behavior. The stated acceptance evidence is: The catalog query finds every scoped object carrying an accepted tag value or a flagged exception. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Network policies constrain permitted source addresses independently from SQL object grants. That explains the role of “Approved origins connect while an unapproved test origin is denied at the network policy boundary”, but the present requirement calls for “The catalog query finds every scoped object carrying an accepted tag value or a flagged exception”: Consistent tag semantics support reliable downstream policy and reporting behavior.
B:Managing identities and accessing all customer tables are distinct authorization duties. That explains the role of “The admin creates a test user and cannot SELECT restricted production data”, but the present requirement calls for “The catalog query finds every scoped object carrying an accepted tag value or a flagged exception”: Consistent tag semantics support reliable downstream policy and reporting behavior.
D:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. That explains the role of “SHOW GRANTS TO ROLE shows the expected inherited lower role and successful authorized query”, but the present requirement calls for “The catalog query finds every scoped object carrying an accepted tag value or a flagged exception”: Consistent tag semantics support reliable downstream policy and reporting behavior.
Question 807
A deployment team has configured this Snowflake capability: Evaluate the supported Snowflake Connector for Kafka and its delivery mode. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A controlled update produces expected change records that can be consumed in one transaction.
- Refresh history shows incremental behavior and the transformed row differences match the source delta.
- A test message is delivered, its ingestion status is observable and no duplicates appear after replay.
- SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run.
Explanation
Correct Answer
C:Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling. The stated acceptance evidence is: A test message is delivered, its ingestion status is observable and no duplicates appear after replay. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Streams track the table changes visible between transactional consumption points without cloning the full table each time. That explains the role of “A controlled update produces expected change records that can be consumed in one transaction”, but the present requirement calls for “A test message is delivered, its ingestion status is observable and no duplicates appear after replay”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
B:Change-based processing limits recomputation when the SQL pattern and source changes support incremental work. That explains the role of “Refresh history shows incremental behavior and the transformed row differences match the source delta”, but the present requirement calls for “A test message is delivered, its ingestion status is observable and no duplicates appear after replay”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
D:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. That explains the role of “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”, but the present requirement calls for “A test message is delivered, its ingestion status is observable and no duplicates appear after replay”: Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
Question 808
A deployment team has configured this Snowflake capability: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Warehouse load history shows lower queued overload time after adding capacity.
- The output contains no more than three invoices per customer and preserves their details.
- An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items.
- A seeded new key appears in query output without altering the base table definition.
Explanation
Correct Answer
B:Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns. The stated acceptance evidence is: The output contains no more than three invoices per customer and preserves their details. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources. That explains the role of “Warehouse load history shows lower queued overload time after adding capacity”, but the present requirement calls for “The output contains no more than three invoices per customer and preserves their details”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
C:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. That explains the role of “An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items”, but the present requirement calls for “The output contains no more than three invoices per customer and preserves their details”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
D:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. That explains the role of “A seeded new key appears in query output without altering the base table definition”, but the present requirement calls for “The output contains no more than three invoices per customer and preserves their details”: Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
Question 809
A deployment team has configured this Snowflake capability: Select the STANDARD scaling policy for a supported multi-cluster warehouse. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A developer runs a test query in the editor and verifies the correct account and role.
- After the session closes, querying the temporary table from a new session fails as expected.
- Warehouse load history shows reduced queueing during spikes under the chosen policy.
- An evaluation batch produces field values and low-confidence cases enter a review queue.
Explanation
Correct Answer
C:Standard policy starts clusters more aggressively to limit waiting under rising concurrency. The stated acceptance evidence is: Warehouse load history shows reduced queueing during spikes under the chosen policy. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges. That explains the role of “A developer runs a test query in the editor and verifies the correct account and role”, but the present requirement calls for “Warehouse load history shows reduced queueing during spikes under the chosen policy”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
B:Temporary tables have session lifetime, unlike permanent tables that persist independently of a session. That explains the role of “After the session closes, querying the temporary table from a new session fails as expected”, but the present requirement calls for “Warehouse load history shows reduced queueing during spikes under the chosen policy”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
D:Document-oriented AI extracts information from unstructured content but may require validation for difficult scans. That explains the role of “An evaluation batch produces field values and low-confidence cases enter a review queue”, but the present requirement calls for “Warehouse load history shows reduced queueing during spikes under the chosen policy”: Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
Question 810
A deployment team has configured this Snowflake capability: Use Snowflake-supported access history with an authorized investigation role. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- SHOW GRANTS TO ROLE shows the expected inherited lower role and successful authorized query.
- A test login requires the configured factor and expected exception accounts are reviewed.
- The admin creates a test user and cannot SELECT restricted production data.
- The reviewer can correlate the time window and affected objects with accountable user sessions.
Explanation
Correct Answer
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. The stated acceptance evidence is: The reviewer can correlate the time window and affected objects with accountable user sessions. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. That explains the role of “SHOW GRANTS TO ROLE shows the expected inherited lower role and successful authorized query”, but the present requirement calls for “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.
B:MFA raises assurance beyond a single compromised password or reused secret. That explains the role of “A test login requires the configured factor and expected exception accounts are reviewed”, but the present requirement calls for “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.
C:Managing identities and accessing all customer tables are distinct authorization duties. That explains the role of “The admin creates a test user and cannot SELECT restricted production data”, but the present requirement calls for “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.