SnowPro Core COF-C03 Practice Test 64
Question 630
During a pilot, engineers pursued an unrelated workaround: Attribute workloads using dedicated warehouses and query or credit usage reporting. The required outcome remained unsatisfied: An organization wants reporting queries to resume without an operator after their warehouse has been auto-suspended. Which correction should the team prioritize?
- Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy.
- Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate.
- Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously.
- Attribute workloads using dedicated warehouses and query or credit usage reporting.
Explanation
Correct Answer
A:Auto-resume lets an eligible statement start stopped compute without manual intervention. The corrective step addresses the missing requirement: An organization wants reporting queries to resume without an operator after their warehouse has been auto-suspended. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently. That explains the role of “Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate”, but the present requirement calls for “Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
C:Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds. That explains the role of “Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously”, but the present requirement calls for “Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
D:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. That explains the role of “Attribute workloads using dedicated warehouses and query or credit usage reporting”, but the present requirement calls for “Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
Question 631
During a pilot, engineers pursued an unrelated workaround: Use independent warehouses or supported attribution metadata and query tags for the workloads. The required outcome remained unsatisfied: A team wants to locate storage growth after staging-table retention settings changed. Which correction should the team prioritize?
- Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
- Use independent warehouses or supported attribution metadata and query tags for the workloads.
- Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls.
- Review database storage usage and Time Travel or Fail-safe storage footprint where applicable.
Explanation
Correct Answer
D:Retained historical data can contribute to storage billing even when active row counts are stable. The corrective step addresses the missing requirement: A team wants to locate storage growth after staging-table retention settings changed. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. That explains the role of “Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually”, but the present requirement calls for “Review database storage usage and Time Travel or Fail-safe storage footprint where applicable”: Retained historical data can contribute to storage billing even when active row counts are stable.
B:Clear compute ownership and query identification improve chargeback compared with account totals alone. That explains the role of “Use independent warehouses or supported attribution metadata and query tags for the workloads”, but the present requirement calls for “Review database storage usage and Time Travel or Fail-safe storage footprint where applicable”: Retained historical data can contribute to storage billing even when active row counts are stable.
C:Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking. That explains the role of “Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls”, but the present requirement calls for “Review database storage usage and Time Travel or Fail-safe storage footprint where applicable”: Retained historical data can contribute to storage billing even when active row counts are stable.
Question 632
During a pilot, engineers pursued an unrelated workaround: Use Snowflake VARIANT array indexing with appropriate type casting. The required outcome remained unsatisfied: An organization wants to analyze PDF invoice contents without hand-building every OCR extraction step. Which correction should the team prioritize?
- Evaluate supported Snowflake document processing AI features with human validation gates.
- Use Snowflake VARIANT array indexing with appropriate type casting.
- Use OBJECT and VARIANT field traversal functions appropriate to the schema.
- Use a supported XML file format and Snowflake XML parsing or query functions.
Explanation
Correct Answer
A:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. The corrective step addresses the missing requirement: An organization wants to analyze PDF invoice contents without hand-building every OCR extraction step. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Array access supports positional extraction from nested semi-structured values. That explains the role of “Use Snowflake VARIANT array indexing with appropriate type casting”, but the present requirement calls for “Evaluate supported Snowflake document processing AI features with human validation gates”: Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
C:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. That explains the role of “Use OBJECT and VARIANT field traversal functions appropriate to the schema”, but the present requirement calls for “Evaluate supported Snowflake document processing AI features with human validation gates”: Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
D:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. That explains the role of “Use a supported XML file format and Snowflake XML parsing or query functions”, but the present requirement calls for “Evaluate supported Snowflake document processing AI features with human validation gates”: Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
Question 633
During a pilot, engineers pursued an unrelated workaround: Benchmark end-to-end credits and latency for representative queries before choosing warehouse size. The required outcome remained unsatisfied: A platform engineer needs to compare Snowpark-optimized and standard warehouse types for memory-heavy Python processing. Which correction should the team prioritize?
- Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior.
- Benchmark end-to-end credits and latency for representative queries before choosing warehouse size.
- Select the STANDARD scaling policy for a supported multi-cluster warehouse.
- Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
Explanation
Correct Answer
A:Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries. The corrective step addresses the missing requirement: A platform engineer needs to compare Snowpark-optimized and standard warehouse types for memory-heavy Python processing. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage. That explains the role of “Benchmark end-to-end credits and latency for representative queries before choosing warehouse size”, but the present requirement calls for “Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior”: Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
C:Standard policy starts clusters more aggressively to limit waiting under rising concurrency. That explains the role of “Select the STANDARD scaling policy for a supported multi-cluster warehouse”, but the present requirement calls for “Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior”: Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
D:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”, but the present requirement calls for “Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior”: Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
Question 634
During a pilot, engineers pursued an unrelated workaround: Inspect serverless ingestion and task usage independently from user-managed warehouse charges. The required outcome remained unsatisfied: Two cost centers share a single warehouse and cannot separate their Snowflake credit charges reliably. Which correction should the team prioritize?
- Use independent warehouses or supported attribution metadata and query tags for the workloads.
- Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
- Configure and monitor a resource monitor with appropriate credit triggers and warehouse association.
- Inspect serverless ingestion and task usage independently from user-managed warehouse charges.
Explanation
Correct Answer
A:Clear compute ownership and query identification improve chargeback compared with account totals alone. The corrective step addresses the missing requirement: Two cost centers share a single warehouse and cannot separate their Snowflake credit charges reliably. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. That explains the role of “Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually”, but the present requirement calls for “Use independent warehouses or supported attribution metadata and query tags for the workloads”: Clear compute ownership and query identification improve chargeback compared with account totals alone.
C:Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds. That explains the role of “Configure and monitor a resource monitor with appropriate credit triggers and warehouse association”, but the present requirement calls for “Use independent warehouses or supported attribution metadata and query tags for the workloads”: Clear compute ownership and query identification improve chargeback compared with account totals alone.
D:Some Snowflake services use serverless credits independently of warehouse runtime. That explains the role of “Inspect serverless ingestion and task usage independently from user-managed warehouse charges”, but the present requirement calls for “Use independent warehouses or supported attribution metadata and query tags for the workloads”: Clear compute ownership and query identification improve chargeback compared with account totals alone.
Question 635
During a pilot, engineers pursued an unrelated workaround: Use supported stage file access mechanisms and scoped file URLs with intended grants. The required outcome remained unsatisfied: An analyst expects every nested JSON value to be a string and gets type errors when values include booleans and arrays. Which correction should the team prioritize?
- Inspect TYPEOF and apply type-aware VARIANT transformations before coercion.
- Use OBJECT and VARIANT field traversal functions appropriate to the schema.
- Use supported stage file access mechanisms and scoped file URLs with intended grants.
- Extract VARIANT paths and cast them into explicit target types in SQL.
Explanation
Correct Answer
A:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. The corrective step addresses the missing requirement: An analyst expects every nested JSON value to be a string and gets type errors when values include booleans and arrays. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. That explains the role of “Use OBJECT and VARIANT field traversal functions appropriate to the schema”, but the present requirement calls for “Inspect TYPEOF and apply type-aware VARIANT transformations before coercion”: VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
C:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. That explains the role of “Use supported stage file access mechanisms and scoped file URLs with intended grants”, but the present requirement calls for “Inspect TYPEOF and apply type-aware VARIANT transformations before coercion”: VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
D:Typed extraction converts flexible input data into stable columns for reporting and validation. That explains the role of “Extract VARIANT paths and cast them into explicit target types in SQL”, but the present requirement calls for “Inspect TYPEOF and apply type-aware VARIANT transformations before coercion”: VARIANT can contain different underlying types, so unconditional string conversion can be incorrect.
Question 636
During a pilot, engineers pursued an unrelated workaround: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. The required outcome remained unsatisfied: A business wants to identify which organization group is charging the largest amount of warehouse compute. Which correction should the team prioritize?
- Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements.
- Use an appropriately configured multi-cluster warehouse to increase concurrent capacity.
- Attribute workloads using dedicated warehouses and query or credit usage reporting.
- Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate.
Explanation
Correct Answer
C:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. The corrective step addresses the missing requirement: A business wants to identify which organization group is charging the largest amount of warehouse compute. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements. That explains the role of “Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements”, but the present requirement calls for “Attribute workloads using dedicated warehouses and query or credit usage reporting”: Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage.
B:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Use an appropriately configured multi-cluster warehouse to increase concurrent capacity”, but the present requirement calls for “Attribute workloads using dedicated warehouses and query or credit usage reporting”: Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage.
D:Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently. That explains the role of “Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate”, but the present requirement calls for “Attribute workloads using dedicated warehouses and query or credit usage reporting”: Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage.
Question 637
During a pilot, engineers pursued an unrelated workaround: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. The required outcome remained unsatisfied: A department configures a warehouse resource monitor and assumes it will also cap all Snowpipe Streaming charges automatically. Which correction should the team prioritize?
- Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually.
- Review database storage usage and Time Travel or Fail-safe storage footprint where applicable.
- Inspect serverless ingestion and task usage independently from user-managed warehouse charges.
- Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls.
Explanation
Correct Answer
D:Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking. The corrective step addresses the missing requirement: A department configures a warehouse resource monitor and assumes it will also cap all Snowpipe Streaming charges automatically. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. That explains the role of “Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually”, but the present requirement calls for “Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls”: Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
B:Retained historical data can contribute to storage billing even when active row counts are stable. That explains the role of “Review database storage usage and Time Travel or Fail-safe storage footprint where applicable”, but the present requirement calls for “Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls”: Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
C:Some Snowflake services use serverless credits independently of warehouse runtime. That explains the role of “Inspect serverless ingestion and task usage independently from user-managed warehouse charges”, but the present requirement calls for “Separate warehouse resource monitors from serverless ingestion cost monitoring and budget controls”: Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking.
Question 638
During a pilot, engineers pursued an unrelated workaround: Enable or refresh supported stage directory tables and inspect their file metadata. The required outcome remained unsatisfied: A file archive contains documents that must be referenced securely by generated Snowflake URLs. Which correction should the team prioritize?
- Use supported stage file access mechanisms and scoped file URLs with intended grants.
- Evaluate supported Snowflake document processing AI features with human validation gates.
- Use LATERAL FLATTEN against the relevant VARIANT path.
- Enable or refresh supported stage directory tables and inspect their file metadata.
Explanation
Correct Answer
A:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. The corrective step addresses the missing requirement: A file archive contains documents that must be referenced securely by generated Snowflake URLs. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. That explains the role of “Evaluate supported Snowflake document processing AI features with human validation gates”, but the present requirement calls for “Use supported stage file access mechanisms and scoped file URLs with intended grants”: Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials.
C:FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values. That explains the role of “Use LATERAL FLATTEN against the relevant VARIANT path”, but the present requirement calls for “Use supported stage file access mechanisms and scoped file URLs with intended grants”: Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials.
D:Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually. That explains the role of “Enable or refresh supported stage directory tables and inspect their file metadata”, but the present requirement calls for “Use supported stage file access mechanisms and scoped file URLs with intended grants”: Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials.
Question 639
During a pilot, engineers pursued an unrelated workaround: Keep external table storage ownership and refresh metadata responsibilities explicit. The required outcome remained unsatisfied: A fact table contains billions of rows and Snowflake needs to skip irrelevant columnar storage blocks for selective queries. Which correction should the team prioritize?
- Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes.
- Create a view or secure view with the appropriate authorization model.
- Use a dynamic table with an explicit target lag and warehouse for eligible transformations.
- Keep external table storage ownership and refresh metadata responsibilities explicit.
Explanation
Correct Answer
A:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. The corrective step addresses the missing requirement: A fact table contains billions of rows and Snowflake needs to skip irrelevant columnar storage blocks for selective queries. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Views define reusable query projections; they are different from full materialized table copies. That explains the role of “Create a view or secure view with the appropriate authorization model”, but the present requirement calls for “Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes”: Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges.
C:Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules. That explains the role of “Use a dynamic table with an explicit target lag and warehouse for eligible transformations”, but the present requirement calls for “Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes”: Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges.
D:External tables reference data outside Snowflake-managed table storage and require consistent metadata handling. That explains the role of “Keep external table storage ownership and refresh metadata responsibilities explicit”, but the present requirement calls for “Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes”: Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges.
Question 640
During a pilot, engineers pursued an unrelated workaround: Use a supported XML file format and Snowflake XML parsing or query functions. The required outcome remained unsatisfied: A team wants to query key-value mappings in nested JSON without hardcoding a separate column for every key. Which correction should the team prioritize?
- Use a supported XML file format and Snowflake XML parsing or query functions.
- Use VARIANT path traversal with a safe cast or null handling for optional attributes.
- Enable or refresh supported stage directory tables and inspect their file metadata.
- Use OBJECT and VARIANT field traversal functions appropriate to the schema.
Explanation
Correct Answer
D:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. The corrective step addresses the missing requirement: A team wants to query key-value mappings in nested JSON without hardcoding a separate column for every key. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. That explains the role of “Use a supported XML file format and Snowflake XML parsing or query functions”, but the present requirement calls for “Use OBJECT and VARIANT field traversal functions appropriate to the schema”: Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values.
B:Path access reads nested semi-structured fields and absent paths require careful NULL semantics. That explains the role of “Use VARIANT path traversal with a safe cast or null handling for optional attributes”, but the present requirement calls for “Use OBJECT and VARIANT field traversal functions appropriate to the schema”: Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values.
C:Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually. That explains the role of “Enable or refresh supported stage directory tables and inspect their file metadata”, but the present requirement calls for “Use OBJECT and VARIANT field traversal functions appropriate to the schema”: Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values.