SnowPro Core COF-C03 Practice Test 54
Question 530
During a pilot, engineers pursued an unrelated workaround: Review Snowflake Trust Center findings and supported remediation recommendations. The required outcome remained unsatisfied: A finance table includes email addresses and national identifiers that must be identified across hundreds of schemas. Which correction should the team prioritize?
- Review Snowflake Trust Center findings and supported remediation recommendations.
- Evaluate row access filtering and column masking independently with representative roles.
- Use supported data classification and semantic labeling to locate sensitive columns.
- Combine role-based access with monitored egress controls and approved data governance policies.
Explanation
Correct Answer
C:Automated or assisted classification helps discover and manage sensitive data across a large catalog. The corrective step addresses the missing requirement: A finance table includes email addresses and national identifiers that must be identified across hundreds of schemas. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Centralized posture views help detect configuration and security risks that object grants alone miss. That explains the role of “Review Snowflake Trust Center findings and supported remediation recommendations”, but the present requirement calls for “Use supported data classification and semantic labeling to locate sensitive columns”: Automated or assisted classification helps discover and manage sensitive data across a large catalog.
B:Row access governs record visibility while masking governs values in visible rows, so they must be tested separately. That explains the role of “Evaluate row access filtering and column masking independently with representative roles”, but the present requirement calls for “Use supported data classification and semantic labeling to locate sensitive columns”: Automated or assisted classification helps discover and manage sensitive data across a large catalog.
D:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. That explains the role of “Combine role-based access with monitored egress controls and approved data governance policies”, but the present requirement calls for “Use supported data classification and semantic labeling to locate sensitive columns”: Automated or assisted classification helps discover and manage sensitive data across a large catalog.
Question 531
During a pilot, engineers pursued an unrelated workaround: Explain target lag as a desired freshness bound and monitor actual refresh timing. The required outcome remained unsatisfied: A daily transformation SQL statement should run at an established time even when nobody opens a worksheet. Which correction should the team prioritize?
- Create a supported task graph with dependency links between tasks.
- Use Snowpipe Streaming with a supported SDK or connector for row-level streaming ingestion.
- Create a Snowflake task with an appropriate schedule and execution context.
- Explain target lag as a desired freshness bound and monitor actual refresh timing.
Explanation
Correct Answer
C:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. The corrective step addresses the missing requirement: A daily transformation SQL statement should run at an established time even when nobody opens a worksheet. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Task DAGs express ordered execution and permit management of dependent pipeline steps. That explains the role of “Create a supported task graph with dependency links between tasks”, but the present requirement calls for “Create a Snowflake task with an appropriate schedule and execution context”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
B:Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive. That explains the role of “Use Snowpipe Streaming with a supported SDK or connector for row-level streaming ingestion”, but the present requirement calls for “Create a Snowflake task with an appropriate schedule and execution context”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
D:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. That explains the role of “Explain target lag as a desired freshness bound and monitor actual refresh timing”, but the present requirement calls for “Create a Snowflake task with an appropriate schedule and execution context”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
Question 532
During a pilot, engineers pursued an unrelated workaround: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. The required outcome remained unsatisfied: A team pauses a warehouse to reduce spending but users need queries to recover on the next scheduled dashboard refresh. Which correction should the team prioritize?
- Enable AUTO_RESUME after verifying user role USAGE and operational expectations.
- Verify multi-cluster auto-scale rules and minimum versus maximum cluster settings.
- Benchmark increasing warehouse size rather than adding multi-cluster capacity first.
- Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands.
Explanation
Correct Answer
A:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. The corrective step addresses the missing requirement: A team pauses a warehouse to reduce spending but users need queries to recover on the next scheduled dashboard refresh. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:A maximum permits capacity growth but does not force permanent use of all configured clusters. That explains the role of “Verify multi-cluster auto-scale rules and minimum versus maximum cluster settings”, but the present requirement calls for “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
C:Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries. That explains the role of “Benchmark increasing warehouse size rather than adding multi-cluster capacity first”, but the present requirement calls for “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
D:A specialized warehouse might provide better memory characteristics for supported Snowpark jobs. That explains the role of “Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands”, but the present requirement calls for “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
Question 533
During a pilot, engineers pursued an unrelated workaround: Distinguish same-environment clone use from supported cross-account or cross-region replication and failover. The required outcome remained unsatisfied: A data provider wants to synchronize a set of supported databases across two accounts without relying on nightly CSV exports. Which correction should the team prioritize?
- Create an eligible zero-copy clone at the supported Time Travel point and verify its schema.
- Distinguish same-environment clone use from supported cross-account or cross-region replication and failover.
- Evaluate supported database replication and failover configuration for the required regions and account editions.
- Configure authorized database replication and monitor refresh status.
Explanation
Correct Answer
D:Replication propagates supported database state between accounts rather than rebuilding tables through files. The corrective step addresses the missing requirement: A data provider wants to synchronize a set of supported databases across two accounts without relying on nightly CSV exports. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Time Travel plus cloning can capture retained historical state for independent testing when object support permits. That explains the role of “Create an eligible zero-copy clone at the supported Time Travel point and verify its schema”, but the present requirement calls for “Configure authorized database replication and monitor refresh status”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
B:Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience. That explains the role of “Distinguish same-environment clone use from supported cross-account or cross-region replication and failover”, but the present requirement calls for “Configure authorized database replication and monitor refresh status”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
C:Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features. That explains the role of “Evaluate supported database replication and failover configuration for the required regions and account editions”, but the present requirement calls for “Configure authorized database replication and monitor refresh status”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
Question 534
During a pilot, engineers pursued an unrelated workaround: Verify the active database and schema context used for unqualified object references. The required outcome remained unsatisfied: A query planner needs table statistics to prune unnecessary micro-partitions before the physical execution phase. Which correction should the team prioritize?
- Identify managed database storage as the persistence layer for compressed columnar table data.
- Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
- Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile.
- Verify the active database and schema context used for unqualified object references.
Explanation
Correct Answer
C:Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans. The corrective step addresses the missing requirement: A query planner needs table statistics to prune unnecessary micro-partitions before the physical execution phase. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. That explains the role of “Identify managed database storage as the persistence layer for compressed columnar table data”, but the present requirement calls for “Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
B:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. That explains the role of “Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work”, but the present requirement calls for “Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
D:Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions. That explains the role of “Verify the active database and schema context used for unqualified object references”, but the present requirement calls for “Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
Question 535
During a pilot, engineers pursued an unrelated workaround: Design a masking policy with clearly defined role-based conditional branches. The required outcome remained unsatisfied: An organization wants consistent governance tags for data-owner department and retention category across database objects. Which correction should the team prioritize?
- Inspect supported Snowflake data lineage for the table and view dependency chain.
- Create and apply governed Snowflake object tags with approved allowed values where suitable.
- Design a masking policy with clearly defined role-based conditional branches.
- Restrict grants and implement an approved secure projection with scoped consumer roles.
Explanation
Correct Answer
B:Tags attach reusable metadata that downstream inventory and governance queries can evaluate. The corrective step addresses the missing requirement: An organization wants consistent governance tags for data-owner department and retention category across database objects. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Data lineage reveals how downstream analytical objects depend on upstream sources. That explains the role of “Inspect supported Snowflake data lineage for the table and view dependency chain”, but the present requirement calls for “Create and apply governed Snowflake object tags with approved allowed values where suitable”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
C:Conditional masking exposes different values to approved roles while retaining one underlying column. That explains the role of “Design a masking policy with clearly defined role-based conditional branches”, but the present requirement calls for “Create and apply governed Snowflake object tags with approved allowed values where suitable”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
D:Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data. That explains the role of “Restrict grants and implement an approved secure projection with scoped consumer roles”, but the present requirement calls for “Create and apply governed Snowflake object tags with approved allowed values where suitable”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
Question 536
During a pilot, engineers pursued an unrelated workaround: Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation. The required outcome remained unsatisfied: A pipeline must run cleansing only after ingestion validation succeeds, then refresh a reporting table. Which correction should the team prioritize?
- Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation.
- Create a supported task graph with dependency links between tasks.
- Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps.
- Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration.
Explanation
Correct Answer
B:Task DAGs express ordered execution and permit management of dependent pipeline steps. The corrective step addresses the missing requirement: A pipeline must run cleansing only after ingestion validation succeeds, then refresh a reporting table. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Change-based processing limits recomputation when the SQL pattern and source changes support incremental work. That explains the role of “Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation”, but the present requirement calls for “Create a supported task graph with dependency links between tasks”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
C:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. That explains the role of “Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps”, but the present requirement calls for “Create a supported task graph with dependency links between tasks”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
D:The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches. That explains the role of “Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration”, but the present requirement calls for “Create a supported task graph with dependency links between tasks”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
Question 537
During a pilot, engineers pursued an unrelated workaround: Benchmark increasing warehouse size rather than adding multi-cluster capacity first. The required outcome remained unsatisfied: A warehouse is oversized and finishing most queries in seconds while credits spike without any queueing. Which correction should the team prioritize?
- Benchmark a smaller warehouse with representative query sizes and verify service-level objectives.
- Benchmark increasing warehouse size rather than adding multi-cluster capacity first.
- Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits.
- Compare warehouse load, credits and query profile statistics before and after configuration changes.
Explanation
Correct Answer
A:Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence. The corrective step addresses the missing requirement: A warehouse is oversized and finishing most queries in seconds while credits spike without any queueing. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries. That explains the role of “Benchmark increasing warehouse size rather than adding multi-cluster capacity first”, but the present requirement calls for “Benchmark a smaller warehouse with representative query sizes and verify service-level objectives”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
C:ECONOMY prioritizes fuller use of existing clusters before starting more compute. That explains the role of “Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits”, but the present requirement calls for “Benchmark a smaller warehouse with representative query sizes and verify service-level objectives”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
D:Capacity should be evaluated against actual queue time, execution time and consumed credits. That explains the role of “Compare warehouse load, credits and query profile statistics before and after configuration changes”, but the present requirement calls for “Benchmark a smaller warehouse with representative query sizes and verify service-level objectives”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
Question 538
During a pilot, engineers pursued an unrelated workaround: Verify share grants and the required database and schema object privileges in the provider account. The required outcome remained unsatisfied: An administrator assumes any Zero-Copy Clone automatically replaces a multi-region disaster-recovery replication plan. Which correction should the team prioritize?
- Use Time Travel AT or BEFORE with an appropriate statement identifier where supported.
- Create an approved Snowflake Marketplace listing for the supported data product.
- Verify share grants and the required database and schema object privileges in the provider account.
- Distinguish same-environment clone use from supported cross-account or cross-region replication and failover.
Explanation
Correct Answer
D:Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience. The corrective step addresses the missing requirement: An administrator assumes any Zero-Copy Clone automatically replaces a multi-region disaster-recovery replication plan. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Statement-based history offers precise temporal reference points for eligible Snowflake objects. That explains the role of “Use Time Travel AT or BEFORE with an appropriate statement identifier where supported”, but the present requirement calls for “Distinguish same-environment clone use from supported cross-account or cross-region replication and failover”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
B:Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share. That explains the role of “Create an approved Snowflake Marketplace listing for the supported data product”, but the present requirement calls for “Distinguish same-environment clone use from supported cross-account or cross-region replication and failover”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
C:Cross-account access requires the provider to grant the intended objects and containing namespace appropriately. That explains the role of “Verify share grants and the required database and schema object privileges in the provider account”, but the present requirement calls for “Distinguish same-environment clone use from supported cross-account or cross-region replication and failover”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
Question 539
During a pilot, engineers pursued an unrelated workaround: Select the intended warehouse in the session or connection before executing the job. The required outcome remained unsatisfied: A new developer wants to write SQL in the Snowflake web interface with saved worksheets and query history. Which correction should the team prioritize?
- Select the intended warehouse in the session or connection before executing the job.
- Use Snowsight worksheets with the intended role, database, schema and warehouse context.
- Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs.
- Move authentication to supported secure identity or credential storage and remove literals from source.
Explanation
Correct Answer
B:Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions. The corrective step addresses the missing requirement: A new developer wants to write SQL in the Snowflake web interface with saved worksheets and query history. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Session warehouse context controls the compute resource charged for a query. That explains the role of “Select the intended warehouse in the session or connection before executing the job”, but the present requirement calls for “Use Snowsight worksheets with the intended role, database, schema and warehouse context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
C:Interactive and automated interfaces suit different workflows but share Snowflake's security and object model. That explains the role of “Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs”, but the present requirement calls for “Use Snowsight worksheets with the intended role, database, schema and warehouse context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
D:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. That explains the role of “Move authentication to supported secure identity or credential storage and remove literals from source”, but the present requirement calls for “Use Snowsight worksheets with the intended role, database, schema and warehouse context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
Question 540
During a pilot, engineers pursued an unrelated workaround: Attach Snowflake governance policies at the data object instead of implementing separate app-only filters. The required outcome remained unsatisfied: An auditor must determine where an executive metric's source fields originated across a series of views. Which correction should the team prioritize?
- Retain masking enforcement on underlying governed columns and test effective role conditions.
- Inspect supported Snowflake data lineage for the table and view dependency chain.
- Use data classification, catalog tags and lineage to identify relevant data objects and dependencies.
- Attach Snowflake governance policies at the data object instead of implementing separate app-only filters.
Explanation
Correct Answer
B:Data lineage reveals how downstream analytical objects depend on upstream sources. The corrective step addresses the missing requirement: An auditor must determine where an executive metric's source fields originated across a series of views. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:A view does not automatically remove column-level policy obligations inherited from its sources. That explains the role of “Retain masking enforcement on underlying governed columns and test effective role conditions”, but the present requirement calls for “Inspect supported Snowflake data lineage for the table and view dependency chain”: Data lineage reveals how downstream analytical objects depend on upstream sources.
C:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. That explains the role of “Use data classification, catalog tags and lineage to identify relevant data objects and dependencies”, but the present requirement calls for “Inspect supported Snowflake data lineage for the table and view dependency chain”: Data lineage reveals how downstream analytical objects depend on upstream sources.
D:Data-level controls travel with queries across clients and minimize inconsistent authorization behavior. That explains the role of “Attach Snowflake governance policies at the data object instead of implementing separate app-only filters”, but the present requirement calls for “Inspect supported Snowflake data lineage for the table and view dependency chain”: Data lineage reveals how downstream analytical objects depend on upstream sources.