SnowPro Core COF-C03 Practice Test 39
Question 380
An architecture reviewer proposes the following solution: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies. The business and technical requirement is: A legal team requests an inventory of locations where particular personal data elements are copied across schemas. Which explanation most accurately justifies this choice?
- Managing identities and accessing all customer tables are distinct authorization duties.
- Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
- Authorization revocation separates identity lifecycle from destructive changes to stored data.
- OAuth enables delegated token-based authentication while token and role privileges still constrain data access.
Explanation
Correct Answer
B:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use user-management privileges or the appropriate system administration role without broad data grants. That explains the role of “Managing identities and accessing all customer tables are distinct authorization duties”, but the present requirement calls for “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
C:This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy. That explains the role of “Authorization revocation separates identity lifecycle from destructive changes to stored data”, but the present requirement calls for “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
D:This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior. That explains the role of “OAuth enables delegated token-based authentication while token and role privileges still constrain data access”, but the present requirement calls for “Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets”: This mechanism explains why the proposed action fits the scenario: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
Question 381
An architecture reviewer proposes the following solution: Use the supported Snowflake JDBC driver with correct account and authentication configuration. The business and technical requirement is: A Java analytics service requires a stable database interface for pooled SQL connections. Which explanation most accurately justifies this choice?
- JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
- Load history provides observable file-level execution and error outcomes for ingestion investigations.
- Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
- Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch.
Explanation
Correct Answer
A:JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions. This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake JDBC driver with correct account and authentication configuration. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Inspect COPY_HISTORY or supported load history and detailed COPY results. That explains the role of “Load history provides observable file-level execution and error outcomes for ingestion investigations”, but the present requirement calls for “JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake JDBC driver with correct account and authentication configuration.
C:This mechanism explains why the proposed action fits the scenario: Create an eligible dynamic table with TARGET_LAG and a refresh warehouse. That explains the role of “Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval”, but the present requirement calls for “JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake JDBC driver with correct account and authentication configuration.
D:This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. That explains the role of “Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch”, but the present requirement calls for “JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake JDBC driver with correct account and authentication configuration.
Question 382
An architecture reviewer proposes the following solution: Use ROLLUP or supported GROUPING SETS for the required subtotal levels. The business and technical requirement is: A report needs subtotals by region and an overall grand total from one grouped query. Which explanation most accurately justifies this choice?
- Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
- Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
- A fair warehouse performance test must separate cache effects from the resource configuration change.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
Explanation
Correct Answer
A:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. This mechanism explains why the proposed action fits the scenario: Use ROLLUP or supported GROUPING SETS for the required subtotal levels. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. That explains the role of “Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources”, but the present requirement calls for “Grouping extensions compute multiple aggregation levels without separately combining unrelated queries”: This mechanism explains why the proposed action fits the scenario: Use ROLLUP or supported GROUPING SETS for the required subtotal levels.
C:This mechanism explains why the proposed action fits the scenario: Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes. That explains the role of “A fair warehouse performance test must separate cache effects from the resource configuration change”, but the present requirement calls for “Grouping extensions compute multiple aggregation levels without separately combining unrelated queries”: This mechanism explains why the proposed action fits the scenario: Use ROLLUP or supported GROUPING SETS for the required subtotal levels.
D:This mechanism explains why the proposed action fits the scenario: Use LATERAL FLATTEN against the relevant VARIANT path. That explains the role of “FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values”, but the present requirement calls for “Grouping extensions compute multiple aggregation levels without separately combining unrelated queries”: This mechanism explains why the proposed action fits the scenario: Use ROLLUP or supported GROUPING SETS for the required subtotal levels.
Question 383
An architecture reviewer proposes the following solution: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. The business and technical requirement is: Hundreds of dashboard queries are queued during business hours although individual queries finish quickly. Which explanation most accurately justifies this choice?
- Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
- Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
- Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
- Views define reusable query projections; they are different from full materialized table copies.
Explanation
Correct Answer
B:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use a TEMPORARY table with an appropriately scoped session. That explains the role of “Temporary tables have session lifetime, unlike permanent tables that persist independently of a session”, but the present requirement calls for “Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement”: This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
C:This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. That explains the role of “Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption”, but the present requirement calls for “Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement”: This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
D:This mechanism explains why the proposed action fits the scenario: Create a view or secure view with the appropriate authorization model. That explains the role of “Views define reusable query projections; they are different from full materialized table copies”, but the present requirement calls for “Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement”: This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
Question 384
An architecture reviewer proposes the following solution: Implement a governed masking expression that exposes only the permitted suffix. The business and technical requirement is: A column with telephone numbers must appear partially redacted but remain useful for matching last-four digits in an authorized service desk. Which explanation most accurately justifies this choice?
- Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
- Query metadata supports operational reporting of status, user, role and execution context.
- Column masking can transform visible values for less-privileged roles without changing stored source values.
- Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
Explanation
Correct Answer
C:Column masking can transform visible values for less-privileged roles without changing stored source values. This mechanism explains why the proposed action fits the scenario: Implement a governed masking expression that exposes only the permitted suffix. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships. That explains the role of “Privilege flow follows the role hierarchy and cannot be inferred from role names alone”, but the present requirement calls for “Column masking can transform visible values for less-privileged roles without changing stored source values”: This mechanism explains why the proposed action fits the scenario: Implement a governed masking expression that exposes only the permitted suffix.
B:This mechanism explains why the proposed action fits the scenario: Use authorized QUERY_HISTORY and related account monitoring views. That explains the role of “Query metadata supports operational reporting of status, user, role and execution context”, but the present requirement calls for “Column masking can transform visible values for less-privileged roles without changing stored source values”: This mechanism explains why the proposed action fits the scenario: Implement a governed masking expression that exposes only the permitted suffix.
D:This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. That explains the role of “Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle”, but the present requirement calls for “Column masking can transform visible values for less-privileged roles without changing stored source values”: This mechanism explains why the proposed action fits the scenario: Implement a governed masking expression that exposes only the permitted suffix.
Question 385
An architecture reviewer proposes the following solution: Configure a Snowflake ODBC driver and approved connection profile. The business and technical requirement is: A BI tool only supports ODBC DSNs and must connect to a Snowflake reporting warehouse. Which explanation most accurately justifies this choice?
- Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive.
- The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet.
- Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
- Listing stage contents validates location, pattern and access independently of a COPY operation.
Explanation
Correct Answer
B:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. This mechanism explains why the proposed action fits the scenario: Configure a Snowflake ODBC driver and approved connection profile. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowpipe Streaming with a supported SDK or connector for row-level streaming ingestion. That explains the role of “Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive”, but the present requirement calls for “The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet”: This mechanism explains why the proposed action fits the scenario: Configure a Snowflake ODBC driver and approved connection profile.
C:This mechanism explains why the proposed action fits the scenario: Create an eligible dynamic table with TARGET_LAG and a refresh warehouse. That explains the role of “Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval”, but the present requirement calls for “The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet”: This mechanism explains why the proposed action fits the scenario: Configure a Snowflake ODBC driver and approved connection profile.
D:This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges. That explains the role of “Listing stage contents validates location, pattern and access independently of a COPY operation”, but the present requirement calls for “The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet”: This mechanism explains why the proposed action fits the scenario: Configure a Snowflake ODBC driver and approved connection profile.
Question 386
An architecture reviewer proposes the following solution: Use common table expressions with the WITH clause to organize query stages. The business and technical requirement is: An analytics team wants reusable named subqueries to make a long Snowflake SELECT easier to review. Which explanation most accurately justifies this choice?
- A fair warehouse performance test must separate cache effects from the resource configuration change.
- Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
- Scaling out adds active clusters as workload concurrency rises to reduce queued requests.
- CTEs structure intermediate logic for readability while still permitting optimizer planning.
Explanation
Correct Answer
D:CTEs structure intermediate logic for readability while still permitting optimizer planning. This mechanism explains why the proposed action fits the scenario: Use common table expressions with the WITH clause to organize query stages. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes. That explains the role of “A fair warehouse performance test must separate cache effects from the resource configuration change”, but the present requirement calls for “CTEs structure intermediate logic for readability while still permitting optimizer planning”: This mechanism explains why the proposed action fits the scenario: Use common table expressions with the WITH clause to organize query stages.
B:This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy. That explains the role of “Large intermediate joins that exceed memory can create costly remote spill and longer runtimes”, but the present requirement calls for “CTEs structure intermediate logic for readability while still permitting optimizer planning”: This mechanism explains why the proposed action fits the scenario: Use common table expressions with the WITH clause to organize query stages.
C:This mechanism explains why the proposed action fits the scenario: Configure multi-cluster auto-scale within supported edition limits. That explains the role of “Scaling out adds active clusters as workload concurrency rises to reduce queued requests”, but the present requirement calls for “CTEs structure intermediate logic for readability while still permitting optimizer planning”: This mechanism explains why the proposed action fits the scenario: Use common table expressions with the WITH clause to organize query stages.
Question 387
An architecture reviewer proposes the following solution: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse. The business and technical requirement is: A warehouse continues consuming credits all night despite no workload demand. Which explanation most accurately justifies this choice?
- Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
- Auto-suspend stops idle compute while auto-resume restarts it for eligible queries.
- Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
- Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design.
Explanation
Correct Answer
B:Auto-suspend stops idle compute while auto-resume restarts it for eligible queries. This mechanism explains why the proposed action fits the scenario: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate a supported externally managed Iceberg table and compatible catalog integration. That explains the role of “Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes”, but the present requirement calls for “Auto-suspend stops idle compute while auto-resume restarts it for eligible queries”: This mechanism explains why the proposed action fits the scenario: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse.
C:This mechanism explains why the proposed action fits the scenario: Combine Snowflake SQL with supported Snowpark and native application development capabilities. That explains the role of “Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces”, but the present requirement calls for “Auto-suspend stops idle compute while auto-resume restarts it for eligible queries”: This mechanism explains why the proposed action fits the scenario: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse.
D:This mechanism explains why the proposed action fits the scenario: Use the fully managed Snowflake service rather than installing a self-hosted database cluster. That explains the role of “Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design”, but the present requirement calls for “Auto-suspend stops idle compute while auto-resume restarts it for eligible queries”: This mechanism explains why the proposed action fits the scenario: Configure sensible AUTO_SUSPEND and AUTO_RESUME settings for the warehouse.
Question 388
An architecture reviewer proposes the following solution: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks. The business and technical requirement is: A governance review finds tags applied inconsistently to objects created by different engineering teams. Which explanation most accurately justifies this choice?
- Consistent tag semantics support reliable downstream policy and reporting behavior.
- Account activity history connects query operations to principals and execution context for investigation.
- Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
- Planned rotation allows new credentials to be tested before revoking the old authentication method.
Explanation
Correct Answer
A:Consistent tag semantics support reliable downstream policy and reporting behavior. This mechanism explains why the proposed action fits the scenario: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Inspect Snowflake access and query history using properly privileged monitoring views. That explains the role of “Account activity history connects query operations to principals and execution context for investigation”, but the present requirement calls for “Consistent tag semantics support reliable downstream policy and reporting behavior”: This mechanism explains why the proposed action fits the scenario: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks.
C:This mechanism explains why the proposed action fits the scenario: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. That explains the role of “Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle”, but the present requirement calls for “Consistent tag semantics support reliable downstream policy and reporting behavior”: This mechanism explains why the proposed action fits the scenario: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks.
D:This mechanism explains why the proposed action fits the scenario: Use a supported overlapping key or token rotation procedure with staged validation. That explains the role of “Planned rotation allows new credentials to be tested before revoking the old authentication method”, but the present requirement calls for “Consistent tag semantics support reliable downstream policy and reporting behavior”: This mechanism explains why the proposed action fits the scenario: Define centralized tag naming, approved values, owner responsibilities, and periodic tag coverage checks.
Question 389
An architecture reviewer proposes the following solution: Evaluate the supported Snowflake Connector for Kafka and its delivery mode. The business and technical requirement is: A data platform receives events from an Apache Kafka cluster and wants a managed integration into Snowflake. Which explanation most accurately justifies this choice?
- Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling.
- Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive.
- File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
- COPY loading error behavior is configurable; silent skipping without review can hide data loss.
Explanation
Correct Answer
A:Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling. This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use Snowpipe Streaming with a supported SDK or connector for row-level streaming ingestion. That explains the role of “Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive”, but the present requirement calls for “Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode.
C:This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices. That explains the role of “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”, but the present requirement calls for “Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode.
D:This mechanism explains why the proposed action fits the scenario: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results. That explains the role of “COPY loading error behavior is configurable; silent skipping without review can hide data loss”, but the present requirement calls for “Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling”: This mechanism explains why the proposed action fits the scenario: Evaluate the supported Snowflake Connector for Kafka and its delivery mode.
Question 390
An architecture reviewer proposes the following solution: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3. The business and technical requirement is: A business report needs the top three invoices per customer while keeping all other columns intact. Which explanation most accurately justifies this choice?
- QAS can offload parts of supported long-running queries to shared compute resources.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
- Result caching can return compatible prior query results without reexecuting a full warehouse scan.
- Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
Explanation
Correct Answer
D:Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns. This mechanism explains why the proposed action fits the scenario: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Consider Query Acceleration Service for eligible selective large scans and aggregations. That explains the role of “QAS can offload parts of supported long-running queries to shared compute resources”, but the present requirement calls for “Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns”: This mechanism explains why the proposed action fits the scenario: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3.
B:This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata. That explains the role of “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”, but the present requirement calls for “Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns”: This mechanism explains why the proposed action fits the scenario: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3.
C:This mechanism explains why the proposed action fits the scenario: Inspect Snowflake persisted query result reuse and conditions that invalidate it. That explains the role of “Result caching can return compatible prior query results without reexecuting a full warehouse scan”, but the present requirement calls for “Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns”: This mechanism explains why the proposed action fits the scenario: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3.