SnowPro Core COF-C03 Practice Test 43
Question 420
An architecture reviewer proposes the following solution: Enable or refresh supported stage directory tables and inspect their file metadata. The business and technical requirement is: A team wants metadata listing of files in an approved external document stage for downstream unstructured processing. Which explanation most accurately justifies this choice?
- A fair warehouse performance test must separate cache effects from the resource configuration change.
- Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
- Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns.
- Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries.
Explanation
Correct Answer
B:Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually. This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata. 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 “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”: This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata.
C:This mechanism explains why the proposed action fits the scenario: Apply ROW_NUMBER over the customer partition and QUALIFY row_number <= 3. That explains the role of “Window ranking plus QUALIFY filters rows based on within-customer order without aggregating away columns”, but the present requirement calls for “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”: This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata.
D:This mechanism explains why the proposed action fits the scenario: Benchmark increasing warehouse size rather than adding multi-cluster capacity first. That explains the role of “Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries”, but the present requirement calls for “Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually”: This mechanism explains why the proposed action fits the scenario: Enable or refresh supported stage directory tables and inspect their file metadata.
Question 421
An architecture reviewer proposes the following solution: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy. The business and technical requirement is: An organization wants reporting queries to resume without an operator after their warehouse has been auto-suspended. Which explanation most accurately justifies this choice?
- Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
- Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions.
- Native development workflows allow experiment history and reproducibility while database privileges still apply.
- Auto-resume lets an eligible statement start stopped compute without manual intervention.
Explanation
Correct Answer
D:Auto-resume lets an eligible statement start stopped compute without manual intervention. This mechanism explains why the proposed action fits the scenario: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Auto-resume lets an eligible statement start stopped compute without manual intervention”: This mechanism explains why the proposed action fits the scenario: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy.
B:This mechanism explains why the proposed action fits the scenario: Package a supported Snowpark UDF with the correct runtime and package permissions. That explains the role of “Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions”, but the present requirement calls for “Auto-resume lets an eligible statement start stopped compute without manual intervention”: This mechanism explains why the proposed action fits the scenario: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy.
C:This mechanism explains why the proposed action fits the scenario: Use Snowflake Notebooks or supported Git-backed developer tooling with approved source control. That explains the role of “Native development workflows allow experiment history and reproducibility while database privileges still apply”, but the present requirement calls for “Auto-resume lets an eligible statement start stopped compute without manual intervention”: This mechanism explains why the proposed action fits the scenario: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy.
Question 422
An architecture reviewer proposes the following solution: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable. The business and technical requirement is: A team wants to locate storage growth after staging-table retention settings changed. Which explanation most accurately justifies this choice?
- Access history exposes which objects or columns were referenced, supporting data governance investigation.
- Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
- Retained historical data can contribute to storage billing even when active row counts are stable.
- Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
Explanation
Correct Answer
C:Retained historical data can contribute to storage billing even when active row counts are stable. This mechanism explains why the proposed action fits the scenario: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role. That explains the role of “Access history exposes which objects or columns were referenced, supporting data governance investigation”, but the present requirement calls for “Retained historical data can contribute to storage billing even when active row counts are stable”: This mechanism explains why the proposed action fits the scenario: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable.
B: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 “Retained historical data can contribute to storage billing even when active row counts are stable”: This mechanism explains why the proposed action fits the scenario: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable.
D:This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles. That explains the role of “Row access governs record visibility while masking governs values in visible rows, so they must be tested separately”, but the present requirement calls for “Retained historical data can contribute to storage billing even when active row counts are stable”: This mechanism explains why the proposed action fits the scenario: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable.
Question 423
An architecture reviewer proposes the following solution: Evaluate supported Snowflake document processing AI features with human validation gates. The business and technical requirement is: An organization wants to analyze PDF invoice contents without hand-building every OCR extraction step. Which explanation most accurately justifies this choice?
- A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
- Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
- Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
- Capacity should be evaluated against actual queue time, execution time and consumed credits.
Explanation
Correct Answer
C:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. That explains the role of “A specialized warehouse might provide better memory characteristics for supported Snowpark jobs”, but the present requirement calls for “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”: This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates.
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates. That explains the role of “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”, but the present requirement calls for “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”: This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates.
D:This mechanism explains why the proposed action fits the scenario: Compare warehouse load, credits and query profile statistics before and after configuration changes. That explains the role of “Capacity should be evaluated against actual queue time, execution time and consumed credits”, but the present requirement calls for “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”: This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates.
Question 424
An architecture reviewer proposes the following solution: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior. The business and technical requirement is: A platform engineer needs to compare Snowpark-optimized and standard warehouse types for memory-heavy Python processing. Which explanation most accurately justifies this choice?
- An explicit session command changes the active namespace used for later unqualified SQL references.
- Native applications bundle data-platform functionality for controlled installation rather than giving recipients unrestricted SQL source access.
- Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
- Views define reusable query projections; they are different from full materialized table copies.
Explanation
Correct Answer
C:Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries. This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults. That explains the role of “An explicit session command changes the active namespace used for later unqualified SQL references”, but the present requirement calls for “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”: This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
B: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 “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”: This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
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 “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”: This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
Question 425
An architecture reviewer proposes the following solution: Use independent warehouses or supported attribution metadata and query tags for the workloads. The business and technical requirement is: Two cost centers share a single warehouse and cannot separate their Snowflake credit charges reliably. Which explanation most accurately justifies this choice?
- Snowflake RBAC places permissions on roles that are granted to users, avoiding broad system administration rights.
- OAuth enables delegated token-based authentication while token and role privileges still constrain data access.
- Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
- Clear compute ownership and query identification improve chargeback compared with account totals alone.
Explanation
Correct Answer
D:Clear compute ownership and query identification improve chargeback compared with account totals alone. This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create a least-privileged custom account role with only the required database and object grants. That explains the role of “Snowflake RBAC places permissions on roles that are granted to users, avoiding broad system administration rights”, but the present requirement calls for “Clear compute ownership and query identification improve chargeback compared with account totals alone”: This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads.
B: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 “Clear compute ownership and query identification improve chargeback compared with account totals alone”: This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads.
C:This mechanism explains why the proposed action fits the scenario: Create and apply governed Snowflake object tags with approved allowed values where suitable. That explains the role of “Tags attach reusable metadata that downstream inventory and governance queries can evaluate”, but the present requirement calls for “Clear compute ownership and query identification improve chargeback compared with account totals alone”: This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads.
Question 426
An architecture reviewer proposes the following solution: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion. The business and technical requirement is: An analyst expects every nested JSON value to be a string and gets type errors when values include booleans and arrays. Which explanation most accurately justifies this choice?
- Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
- Capacity should be evaluated against actual queue time, execution time and consumed credits.
- Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
- VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
Explanation
Correct Answer
D:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text. That explains the role of “Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching”, but the present requirement calls for “VARIANT can contain different underlying types, so unconditional string conversion can be incorrect”: This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion.
B:This mechanism explains why the proposed action fits the scenario: Compare warehouse load, credits and query profile statistics before and after configuration changes. That explains the role of “Capacity should be evaluated against actual queue time, execution time and consumed credits”, but the present requirement calls for “VARIANT can contain different underlying types, so unconditional string conversion can be incorrect”: This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion.
C: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 “VARIANT can contain different underlying types, so unconditional string conversion can be incorrect”: This mechanism explains why the proposed action fits the scenario: Inspect TYPEOF and apply type-aware VARIANT transformations before coercion.
Question 427
An architecture reviewer proposes the following solution: Attribute workloads using dedicated warehouses and query or credit usage reporting. The business and technical requirement is: A business wants to identify which organization group is charging the largest amount of warehouse compute. Which explanation most accurately justifies this choice?
- Views define reusable query projections; they are different from full materialized table copies.
- Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions.
- Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage.
- JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
Explanation
Correct Answer
C:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. This mechanism explains why the proposed action fits the scenario: Attribute workloads using dedicated warehouses and query or credit usage reporting. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage”: This mechanism explains why the proposed action fits the scenario: Attribute workloads using dedicated warehouses and query or credit usage reporting.
B:This mechanism explains why the proposed action fits the scenario: Package a supported Snowpark UDF with the correct runtime and package permissions. That explains the role of “Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions”, but the present requirement calls for “Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage”: This mechanism explains why the proposed action fits the scenario: Attribute workloads using dedicated warehouses and query or credit usage reporting.
D:This mechanism explains why the proposed action fits the scenario: Use the Snowflake JDBC driver with the approved credentials and network policy. That explains the role of “JDBC provides a programmatic database connection for Java applications rather than a browser-only session”, but the present requirement calls for “Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage”: This mechanism explains why the proposed action fits the scenario: Attribute workloads using dedicated warehouses and query or credit usage reporting.
Question 428
An architecture reviewer proposes the following solution: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls. The business and technical requirement is: A department configures a warehouse resource monitor and assumes it will also cap all Snowpipe Streaming charges automatically. Which explanation most accurately justifies this choice?
- Access history exposes which objects or columns were referenced, supporting data governance investigation.
- Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
- Planned rotation allows new credentials to be tested before revoking the old authentication method.
- Account activity history connects query operations to principals and execution context for investigation.
Explanation
Correct Answer
B:Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking. This mechanism explains why the proposed action fits the scenario: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role. That explains the role of “Access history exposes which objects or columns were referenced, supporting data governance investigation”, but the present requirement calls for “Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking”: This mechanism explains why the proposed action fits the scenario: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls.
C: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 “Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking”: This mechanism explains why the proposed action fits the scenario: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls.
D: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 “Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking”: This mechanism explains why the proposed action fits the scenario: Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls.
Question 429
An architecture reviewer proposes the following solution: Use supported stage file access mechanisms and scoped file URLs with intended grants. The business and technical requirement is: A file archive contains documents that must be referenced securely by generated Snowflake URLs. Which explanation most accurately justifies this choice?
- Suspension releases active compute after an idle period rather than relying on staff to stop it.
- Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials.
- Window functions compute rankings across a partition while retaining the underlying row granularity.
- Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
Explanation
Correct Answer
B:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. This mechanism explains why the proposed action fits the scenario: Use supported stage file access mechanisms and scoped file URLs with intended grants. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME. That explains the role of “Suspension releases active compute after an idle period rather than relying on staff to stop it”, but the present requirement calls for “Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials”: This mechanism explains why the proposed action fits the scenario: Use supported stage file access mechanisms and scoped file URLs with intended grants.
C:This mechanism explains why the proposed action fits the scenario: Use RANK or DENSE_RANK with a partitioned window expression appropriate to tie behavior. That explains the role of “Window functions compute rankings across a partition while retaining the underlying row granularity”, but the present requirement calls for “Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials”: This mechanism explains why the proposed action fits the scenario: Use supported stage file access mechanisms and scoped file URLs with intended grants.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates. That explains the role of “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”, but the present requirement calls for “Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials”: This mechanism explains why the proposed action fits the scenario: Use supported stage file access mechanisms and scoped file URLs with intended grants.
Question 430
An architecture reviewer proposes the following solution: Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes. The business and technical requirement is: A fact table contains billions of rows and Snowflake needs to skip irrelevant columnar storage blocks for selective queries. Which explanation most accurately justifies this choice?
- Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges.
- Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
- Structured query generation and unstructured semantic retrieval solve different information-access problems.
- Workload warehouse separation isolates query contention and cost attribution across departments.
Explanation
Correct Answer
A:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. This mechanism explains why the proposed action fits the scenario: Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Move authentication to supported secure identity or credential storage and remove literals from source. That explains the role of “Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords”, but the present requirement calls for “Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges”: This mechanism explains why the proposed action fits the scenario: Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes.
C:This mechanism explains why the proposed action fits the scenario: Use Cortex Analyst for governed structured semantic SQL and Cortex Search for text retrieval as appropriate. That explains the role of “Structured query generation and unstructured semantic retrieval solve different information-access problems”, but the present requirement calls for “Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges”: This mechanism explains why the proposed action fits the scenario: Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes.
D:This mechanism explains why the proposed action fits the scenario: Assign ingestion to its own appropriately sized virtual warehouse. That explains the role of “Workload warehouse separation isolates query contention and cost attribution across departments”, but the present requirement calls for “Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges”: This mechanism explains why the proposed action fits the scenario: Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes.