SnowPro Core COF-C03 Practice Test 65
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.
Question 641
During a pilot, engineers pursued an unrelated workaround: Evaluate Snowflake hybrid tables for the supported transactional access pattern. The required outcome remained unsatisfied: A developer expects creating a regular Snowflake table to require a manually defined physical storage file size. Which correction should the team prioritize?
- Evaluate Snowflake hybrid tables for the supported transactional access pattern.
- Let Snowflake manage storage, compression, and micro-partitions for standard tables.
- Use a PERMANENT table with approved Time Travel retention.
- Use a dynamic table with an explicit target lag and warehouse for eligible transformations.
Explanation
Correct Answer
B:Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement. The corrective step addresses the missing requirement: A developer expects creating a regular Snowflake table to require a manually defined physical storage file size. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “Evaluate Snowflake hybrid tables for the supported transactional access pattern”, but the present requirement calls for “Let Snowflake manage storage, compression, and micro-partitions for standard tables”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
C:Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings. That explains the role of “Use a PERMANENT table with approved Time Travel retention”, but the present requirement calls for “Let Snowflake manage storage, compression, and micro-partitions for standard tables”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
D: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 “Let Snowflake manage storage, compression, and micro-partitions for standard tables”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
Question 642
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: An analyst wants to distinguish a JSON null value from a missing key in a VARIANT document. Which correction should the team prioritize?
- Evaluate supported Snowflake document processing AI features with human validation gates.
- Enable or refresh supported stage directory tables and inspect their file metadata.
- Use VARIANT path traversal with a safe cast or null handling for optional attributes.
- Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates.
Explanation
Correct Answer
D:JSON null and SQL NULL or absent paths can behave differently in comparisons and casts. The corrective step addresses the missing requirement: An analyst wants to distinguish a JSON null value from a missing key in a VARIANT document. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
B: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 “Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
C: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 “Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
Question 643
During a pilot, engineers pursued an unrelated workaround: Use a TRANSIENT table after confirming the shorter recovery requirements. The required outcome remained unsatisfied: A temporary staging dataset should disappear when its creating session ends. Which correction should the team prioritize?
- Keep external table storage ownership and refresh metadata responsibilities explicit.
- Use a TEMPORARY table with an appropriately scoped session.
- Use a TRANSIENT table after confirming the shorter recovery requirements.
- Evaluate a supported externally managed Iceberg table and compatible catalog integration.
Explanation
Correct Answer
B:Temporary tables have session lifetime, unlike permanent tables that persist independently of a session. The corrective step addresses the missing requirement: A temporary staging dataset should disappear when its creating session ends. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 a TEMPORARY table with an appropriately scoped session”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
C:Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs. That explains the role of “Use a TRANSIENT table after confirming the shorter recovery requirements”, but the present requirement calls for “Use a TEMPORARY table with an appropriately scoped session”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
D:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. That explains the role of “Evaluate a supported externally managed Iceberg table and compatible catalog integration”, but the present requirement calls for “Use a TEMPORARY table with an appropriately scoped session”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
Question 644
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 team must ingest XML documents and extract nested element attributes for a report. Which correction should the team prioritize?
- Use Snowflake VARIANT array indexing with appropriate type casting.
- Use a supported XML file format and Snowflake XML parsing or query functions.
- Use OBJECT and VARIANT field traversal functions appropriate to the schema.
- Enable or refresh supported stage directory tables and inspect their file metadata.
Explanation
Correct Answer
B:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. The corrective step addresses the missing requirement: A team must ingest XML documents and extract nested element attributes for a report. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Use a supported XML file format and Snowflake XML parsing or query functions”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
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 “Use a supported XML file format and Snowflake XML parsing or query functions”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
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 a supported XML file format and Snowflake XML parsing or query functions”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
Question 645
During a pilot, engineers pursued an unrelated workaround: Evaluate Snowflake hybrid tables for the supported transactional access pattern. The required outcome remained unsatisfied: An ETL scratch table must survive disconnected sessions but does not need a permanent table's Fail-safe recovery window. Which correction should the team prioritize?
- Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes.
- Keep external table storage ownership and refresh metadata responsibilities explicit.
- Use a TRANSIENT table after confirming the shorter recovery requirements.
- Evaluate Snowflake hybrid tables for the supported transactional access pattern.
Explanation
Correct Answer
C:Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs. The corrective step addresses the missing requirement: An ETL scratch table must survive disconnected sessions but does not need a permanent table's Fail-safe recovery window. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. That explains the role of “Use Snowflake micro-partition metadata and pruning before adding unnecessary indexes”, but the present requirement calls for “Use a TRANSIENT table after confirming the shorter recovery requirements”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
B: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 a TRANSIENT table after confirming the shorter recovery requirements”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
D:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “Evaluate Snowflake hybrid tables for the supported transactional access pattern”, but the present requirement calls for “Use a TRANSIENT table after confirming the shorter recovery requirements”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
Question 646
During a pilot, engineers pursued an unrelated workaround: Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost. The required outcome remained unsatisfied: A production finance table requires supported retention and Snowflake-managed Fail-safe recovery capabilities. Which correction should the team prioritize?
- Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost.
- Use a dynamic table with an explicit target lag and warehouse for eligible transformations.
- Use a PERMANENT table with approved Time Travel retention.
- Evaluate a supported externally managed Iceberg table and compatible catalog integration.
Explanation
Correct Answer
C:Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings. The corrective step addresses the missing requirement: A production finance table requires supported retention and Snowflake-managed Fail-safe recovery capabilities. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Materialized views persist selected computed results but impose storage and maintenance costs. That explains the role of “Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost”, but the present requirement calls for “Use a PERMANENT table with approved Time Travel retention”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
B: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 a PERMANENT table with approved Time Travel retention”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
D:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. That explains the role of “Evaluate a supported externally managed Iceberg table and compatible catalog integration”, but the present requirement calls for “Use a PERMANENT table with approved Time Travel retention”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
Question 647
During a pilot, engineers pursued an unrelated workaround: Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost. The required outcome remained unsatisfied: An analytics app must query parquet data managed in an external Apache Iceberg catalog without copying it to a regular table. Which correction should the team prioritize?
- Use supported zero-copy cloning for the schema and validate dependent objects.
- Evaluate a supported externally managed Iceberg table and compatible catalog integration.
- Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost.
- Store semi-structured payloads in VARIANT and extract typed fields in downstream queries.
Explanation
Correct Answer
B:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. The corrective step addresses the missing requirement: An analytics app must query parquet data managed in an external Apache Iceberg catalog without copying it to a regular table. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Cloning initially shares underlying immutable micro-partitions and creates a logically independent object namespace. That explains the role of “Use supported zero-copy cloning for the schema and validate dependent objects”, but the present requirement calls for “Evaluate a supported externally managed Iceberg table and compatible catalog integration”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
C:Materialized views persist selected computed results but impose storage and maintenance costs. That explains the role of “Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost”, but the present requirement calls for “Evaluate a supported externally managed Iceberg table and compatible catalog integration”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
D:VARIANT holds flexible structured values without forcing one rigid input schema for every record. That explains the role of “Store semi-structured payloads in VARIANT and extract typed fields in downstream queries”, but the present requirement calls for “Evaluate a supported externally managed Iceberg table and compatible catalog integration”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
Question 648
During a pilot, engineers pursued an unrelated workaround: Evaluate clustering only against table size and selective range-filter access patterns. The required outcome remained unsatisfied: A service must perform frequent key-based transactional updates with enforced primary-key behavior. Which correction should the team prioritize?
- Evaluate Snowflake hybrid tables for the supported transactional access pattern.
- Use a TEMPORARY table with an appropriately scoped session.
- Let Snowflake manage storage, compression, and micro-partitions for standard tables.
- Evaluate clustering only against table size and selective range-filter access patterns.
Explanation
Correct Answer
A:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. The corrective step addresses the missing requirement: A service must perform frequent key-based transactional updates with enforced primary-key behavior. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Temporary tables have session lifetime, unlike permanent tables that persist independently of a session. That explains the role of “Use a TEMPORARY table with an appropriately scoped session”, but the present requirement calls for “Evaluate Snowflake hybrid tables for the supported transactional access pattern”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
C:Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement. That explains the role of “Let Snowflake manage storage, compression, and micro-partitions for standard tables”, but the present requirement calls for “Evaluate Snowflake hybrid tables for the supported transactional access pattern”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
D:Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index. That explains the role of “Evaluate clustering only against table size and selective range-filter access patterns”, but the present requirement calls for “Evaluate Snowflake hybrid tables for the supported transactional access pattern”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
Question 649
During a pilot, engineers pursued an unrelated workaround: Let Snowflake manage storage, compression, and micro-partitions for standard tables. The required outcome remained unsatisfied: A reporting dataset needs a maintained derived view of a complex transformation that should refresh with changing input data. Which correction should the team prioritize?
- Let Snowflake manage storage, compression, and micro-partitions for standard tables.
- Use a dynamic table with an explicit target lag and warehouse for eligible transformations.
- Use a PERMANENT table with approved Time Travel retention.
- Evaluate clustering only against table size and selective range-filter access patterns.
Explanation
Correct Answer
B:Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules. The corrective step addresses the missing requirement: A reporting dataset needs a maintained derived view of a complex transformation that should refresh with changing input data. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement. That explains the role of “Let Snowflake manage storage, compression, and micro-partitions for standard tables”, but the present requirement calls for “Use a dynamic table with an explicit target lag and warehouse for eligible transformations”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
C:Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings. That explains the role of “Use a PERMANENT table with approved Time Travel retention”, but the present requirement calls for “Use a dynamic table with an explicit target lag and warehouse for eligible transformations”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
D:Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index. That explains the role of “Evaluate clustering only against table size and selective range-filter access patterns”, but the present requirement calls for “Use a dynamic table with an explicit target lag and warehouse for eligible transformations”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
Question 650
During a pilot, engineers pursued an unrelated workaround: Evaluate Snowflake hybrid tables for the supported transactional access pattern. The required outcome remained unsatisfied: A frequently used aggregate query scans a large table and repeats the same precomputation across many sessions. Which correction should the team prioritize?
- Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost.
- Keep external table storage ownership and refresh metadata responsibilities explicit.
- Evaluate Snowflake hybrid tables for the supported transactional access pattern.
- Evaluate a supported externally managed Iceberg table and compatible catalog integration.
Explanation
Correct Answer
A:Materialized views persist selected computed results but impose storage and maintenance costs. The corrective step addresses the missing requirement: A frequently used aggregate query scans a large table and repeats the same precomputation across many sessions. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost”: Materialized views persist selected computed results but impose storage and maintenance costs.
C:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “Evaluate Snowflake hybrid tables for the supported transactional access pattern”, but the present requirement calls for “Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost”: Materialized views persist selected computed results but impose storage and maintenance costs.
D:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. That explains the role of “Evaluate a supported externally managed Iceberg table and compatible catalog integration”, but the present requirement calls for “Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost”: Materialized views persist selected computed results but impose storage and maintenance costs.