SnowPro Core COF-C03 Practice Test 40
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.
Question 391
An architecture reviewer proposes the following solution: Select the STANDARD scaling policy for a supported multi-cluster warehouse. The business and technical requirement is: A time-critical dashboard prefers responsiveness over minimizing the credits of additional multi-cluster capacity. Which explanation most accurately justifies this choice?
- Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
- Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries.
- Standard policy starts clusters more aggressively to limit waiting under rising concurrency.
- Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
Explanation
Correct Answer
C:Standard policy starts clusters more aggressively to limit waiting under rising concurrency. This mechanism explains why the proposed action fits the scenario: Select the STANDARD scaling policy for a supported multi-cluster warehouse. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowsight worksheets with the intended role, database, schema and warehouse context. That explains the role of “Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions”, but the present requirement calls for “Standard policy starts clusters more aggressively to limit waiting under rising concurrency”: This mechanism explains why the proposed action fits the scenario: Select the STANDARD scaling policy for a supported multi-cluster warehouse.
B:This mechanism explains why the proposed action fits the scenario: Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements. That explains the role of “Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries”, but the present requirement calls for “Standard policy starts clusters more aggressively to limit waiting under rising concurrency”: This mechanism explains why the proposed action fits the scenario: Select the STANDARD scaling policy for a supported multi-cluster warehouse.
D:This mechanism explains why the proposed action fits the scenario: Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs. That explains the role of “Interactive and automated interfaces suit different workflows but share Snowflake's security and object model”, but the present requirement calls for “Standard policy starts clusters more aggressively to limit waiting under rising concurrency”: This mechanism explains why the proposed action fits the scenario: Select the STANDARD scaling policy for a supported multi-cluster warehouse.
Question 392
An architecture reviewer proposes the following solution: Use Snowflake-supported access history with an authorized investigation role. The business and technical requirement is: A business team wants to know which queries accessed restricted information during an incident window. Which explanation most accurately justifies this choice?
- SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
- Some Snowflake services use serverless credits independently of warehouse runtime.
- Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
- Access history exposes which objects or columns were referenced, supporting data governance investigation.
Explanation
Correct Answer
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context. That explains the role of “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”, but the present requirement calls for “Access history exposes which objects or columns were referenced, supporting data governance investigation”: This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role.
B:This mechanism explains why the proposed action fits the scenario: Inspect serverless ingestion and task usage independently from user-managed warehouse charges. That explains the role of “Some Snowflake services use serverless credits independently of warehouse runtime”, but the present requirement calls for “Access history exposes which objects or columns were referenced, supporting data governance investigation”: This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role.
C:This mechanism explains why the proposed action fits the scenario: Grant the necessary ancestor object USAGE privileges to the intended role. That explains the role of “Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights”, but the present requirement calls for “Access history exposes which objects or columns were referenced, supporting data governance investigation”: This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role.
Question 393
An architecture reviewer proposes the following solution: Use a Snowflake storage integration and controlled external stage grants. The business and technical requirement is: A data access service wants to read cloud storage using centrally authorized integration objects, not individual users' storage keys. Which explanation most accurately justifies this choice?
- Parquet carries structured column data and should not be parsed as plain delimited text.
- Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
- The loader needs explicit format rules to distinguish metadata rows from data records.
- Bulk copy validation checks how staged rows would parse without treating the test as a production load.
Explanation
Correct Answer
B:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. This mechanism explains why the proposed action fits the scenario: Use a Snowflake storage integration and controlled external stage grants. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping. That explains the role of “Parquet carries structured column data and should not be parsed as plain delimited text”, but the present requirement calls for “Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access”: This mechanism explains why the proposed action fits the scenario: Use a Snowflake storage integration and controlled external stage grants.
C:This mechanism explains why the proposed action fits the scenario: Set the correct CSV header-handling option in the file format. That explains the role of “The loader needs explicit format rules to distinguish metadata rows from data records”, but the present requirement calls for “Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access”: This mechanism explains why the proposed action fits the scenario: Use a Snowflake storage integration and controlled external stage grants.
D:This mechanism explains why the proposed action fits the scenario: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases. That explains the role of “Bulk copy validation checks how staged rows would parse without treating the test as a production load”, but the present requirement calls for “Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access”: This mechanism explains why the proposed action fits the scenario: Use a Snowflake storage integration and controlled external stage grants.
Question 394
An architecture reviewer proposes the following solution: Use CASE expressions with explicit ELSE handling for unknown values. The business and technical requirement is: A transform must map a finite set of status codes to human-readable labels without a separate lookup table. Which explanation most accurately justifies this choice?
- Independent compute minimizes competing memory, CPU and concurrency requirements.
- Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
- CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
- Typed extraction converts flexible input data into stable columns for reporting and validation.
Explanation
Correct Answer
C:CASE supplies conditional SQL expressions suited to bounded mappings, including defaults. This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Separate the interactive and transformation workloads into different warehouses. That explains the role of “Independent compute minimizes competing memory, CPU and concurrency requirements”, but the present requirement calls for “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”: This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values.
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 “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”: This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values.
D:This mechanism explains why the proposed action fits the scenario: Extract VARIANT paths and cast them into explicit target types in SQL. That explains the role of “Typed extraction converts flexible input data into stable columns for reporting and validation”, but the present requirement calls for “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”: This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values.
Question 395
An architecture reviewer proposes the following solution: Use the ECONOMY scaling policy on the supported auto-scale warehouse. The business and technical requirement is: A back-office ETL workload accepts some queueing in exchange for conserving multi-cluster compute. Which explanation most accurately justifies this choice?
- Native applications bundle data-platform functionality for controlled installation rather than giving recipients unrestricted SQL source access.
- Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
- Economy favors better cluster utilization before adding parallel compute capacity.
- Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth.
Explanation
Correct Answer
C:Economy favors better cluster utilization before adding parallel compute capacity. This mechanism explains why the proposed action fits the scenario: Use the ECONOMY scaling policy on the supported auto-scale warehouse. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Native App Framework for the supported distribution pattern. That explains the role of “Native applications bundle data-platform functionality for controlled installation rather than giving recipients unrestricted SQL source access”, but the present requirement calls for “Economy favors better cluster utilization before adding parallel compute capacity”: This mechanism explains why the proposed action fits the scenario: Use the ECONOMY scaling policy on the supported auto-scale warehouse.
B:This mechanism explains why the proposed action fits the scenario: Execute supported Snowflake SQL transformations using an appropriate compute warehouse. That explains the role of “Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls”, but the present requirement calls for “Economy favors better cluster utilization before adding parallel compute capacity”: This mechanism explains why the proposed action fits the scenario: Use the ECONOMY scaling policy on the supported auto-scale warehouse.
D:This mechanism explains why the proposed action fits the scenario: Keep central Snowflake-managed database storage while running the teams on independent virtual warehouses. That explains the role of “Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth”, but the present requirement calls for “Economy favors better cluster utilization before adding parallel compute capacity”: This mechanism explains why the proposed action fits the scenario: Use the ECONOMY scaling policy on the supported auto-scale warehouse.
Question 396
An architecture reviewer proposes the following solution: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. The business and technical requirement is: A high-cost warehouse runs idle for hours during every weekend. Which explanation most accurately justifies this choice?
- SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
- Row access policies enforce row-level visibility in queries independently of front-end filters.
- Conditional masking exposes different values to approved roles while retaining one underlying column.
- Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
Explanation
Correct Answer
D:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context. That explains the role of “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”, but the present requirement calls for “Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste”: This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
B:This mechanism explains why the proposed action fits the scenario: Apply a row access policy that filters rows based on authorized role or mapping context. That explains the role of “Row access policies enforce row-level visibility in queries independently of front-end filters”, but the present requirement calls for “Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste”: This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
C:This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches. That explains the role of “Conditional masking exposes different values to approved roles while retaining one underlying column”, but the present requirement calls for “Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste”: This mechanism explains why the proposed action fits the scenario: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
Question 397
An architecture reviewer proposes the following solution: Configure a supported API integration with the required external-function security boundary. The business and technical requirement is: An external function must invoke a controlled cloud API but should not embed arbitrary network credentials in every SQL query. Which explanation most accurately justifies this choice?
- Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch.
- API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions.
- DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
- Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
Explanation
Correct Answer
B:API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions. This mechanism explains why the proposed action fits the scenario: Configure a supported API integration with the required external-function security boundary. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions”: This mechanism explains why the proposed action fits the scenario: Configure a supported API integration with the required external-function security boundary.
C:This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. That explains the role of “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”, but the present requirement calls for “API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions”: This mechanism explains why the proposed action fits the scenario: Configure a supported API integration with the required external-function security boundary.
D:This mechanism explains why the proposed action fits the scenario: Capture supported METADATA$ filename and load timestamp information during staging ingestion. That explains the role of “Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers”, but the present requirement calls for “API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions”: This mechanism explains why the proposed action fits the scenario: Configure a supported API integration with the required external-function security boundary.
Question 398
An architecture reviewer proposes the following solution: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules. The business and technical requirement is: An engineer wants to convert incoming timestamps to a consistent reporting time zone while retaining source timestamps. Which explanation most accurately justifies this choice?
- QAS can offload parts of supported long-running queries to shared compute resources.
- Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
- Materialized views store selected precomputed results that can reduce repeated execution work.
- VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
Explanation
Correct Answer
B:Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved. This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules. 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 “Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved”: This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules.
C:This mechanism explains why the proposed action fits the scenario: Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs. That explains the role of “Materialized views store selected precomputed results that can reduce repeated execution work”, but the present requirement calls for “Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved”: This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules.
D:This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion. That explains the role of “VARIANT can contain different underlying types, so unconditional string conversion can be incorrect”, but the present requirement calls for “Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved”: This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules.
Question 399
An architecture reviewer proposes the following solution: Assign ingestion to its own appropriately sized virtual warehouse. The business and technical requirement is: A 24-hour ingestion process must run on dedicated compute separate from BI reports. Which explanation most accurately justifies this choice?
- Document-oriented AI extracts information from unstructured content but may require validation for difficult scans.
- Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
- Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
- Workload warehouse separation isolates query contention and cost attribution across departments.
Explanation
Correct Answer
D:Workload warehouse separation isolates query contention and cost attribution across departments. This mechanism explains why the proposed action fits the scenario: Assign ingestion to its own appropriately sized virtual warehouse. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Document AI or supported document extraction capabilities with quality checks. That explains the role of “Document-oriented AI extracts information from unstructured content but may require validation for difficult scans”, but the present requirement calls for “Workload warehouse separation isolates query contention and cost attribution across departments”: This mechanism explains why the proposed action fits the scenario: Assign ingestion to its own appropriately sized virtual warehouse.
B:This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables. That explains the role of “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”, but the present requirement calls for “Workload warehouse separation isolates query contention and cost attribution across departments”: This mechanism explains why the proposed action fits the scenario: Assign ingestion to its own appropriately sized virtual warehouse.
C:This mechanism explains why the proposed action fits the scenario: Use a TRANSIENT table after confirming the shorter recovery requirements. That explains the role of “Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs”, but the present requirement calls for “Workload warehouse separation isolates query contention and cost attribution across departments”: This mechanism explains why the proposed action fits the scenario: Assign ingestion to its own appropriately sized virtual warehouse.
Question 400
An architecture reviewer proposes the following solution: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association. The business and technical requirement is: An administrator needs to cap or alert on warehouse consumption before exceeding a department's monthly credit budget. Which explanation most accurately justifies this choice?
- Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds.
- Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
- Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
- Conditional masking exposes different values to approved roles while retaining one underlying column.
Explanation
Correct Answer
A:Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds. This mechanism explains why the proposed action fits the scenario: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants. That explains the role of “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”, but the present requirement calls for “Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds”: This mechanism explains why the proposed action fits the scenario: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association.
C:This mechanism explains why the proposed action fits the scenario: Grant the necessary ancestor object USAGE privileges to the intended role. That explains the role of “Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights”, but the present requirement calls for “Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds”: This mechanism explains why the proposed action fits the scenario: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association.
D:This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches. That explains the role of “Conditional masking exposes different values to approved roles while retaining one underlying column”, but the present requirement calls for “Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds”: This mechanism explains why the proposed action fits the scenario: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association.