SnowPro Core COF-C03 Practice Test 55
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.
Question 541
During a pilot, engineers pursued an unrelated workaround: Create a supported task graph with dependency links between tasks. The required outcome remained unsatisfied: A team wants a declarative cleaned dataset refreshed automatically to be no more than ten minutes behind its base table when feasible. Which correction should the team prioritize?
- Create an eligible dynamic table with TARGET_LAG and a refresh warehouse.
- Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
- Create a supported task graph with dependency links between tasks.
- Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing.
Explanation
Correct Answer
A:Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval. The corrective step addresses the missing requirement: A team wants a declarative cleaned dataset refreshed automatically to be no more than ten minutes behind its base table when feasible. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table”, but the present requirement calls for “Create an eligible dynamic table with TARGET_LAG and a refresh warehouse”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
C: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 an eligible dynamic table with TARGET_LAG and a refresh warehouse”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
D:Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending. That explains the role of “Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing”, but the present requirement calls for “Create an eligible dynamic table with TARGET_LAG and a refresh warehouse”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
Question 542
During a pilot, engineers pursued an unrelated workaround: Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work. The required outcome remained unsatisfied: A team needs a straightforward method to monitor whether warehouse scaling changes actually improved throughput. Which correction should the team prioritize?
- Compare warehouse load, credits and query profile statistics before and after configuration changes.
- Separate the interactive and transformation workloads into different warehouses.
- Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work.
- Configure multi-cluster auto-scale within supported edition limits.
Explanation
Correct Answer
A:Capacity should be evaluated against actual queue time, execution time and consumed credits. The corrective step addresses the missing requirement: A team needs a straightforward method to monitor whether warehouse scaling changes actually improved throughput. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Separate the interactive and transformation workloads into different warehouses”, but the present requirement calls for “Compare warehouse load, credits and query profile statistics before and after configuration changes”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
C:Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution. That explains the role of “Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work”, but the present requirement calls for “Compare warehouse load, credits and query profile statistics before and after configuration changes”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
D:Scaling out adds active clusters as workload concurrency rises to reduce queued requests. That explains the role of “Configure multi-cluster auto-scale within supported edition limits”, but the present requirement calls for “Compare warehouse load, credits and query profile statistics before and after configuration changes”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
Question 543
During a pilot, engineers pursued an unrelated workaround: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. The required outcome remained unsatisfied: A provider needs a recoverable test environment snapshot from a specific historical point before a schema migration. Which correction should the team prioritize?
- Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
- Create an eligible zero-copy clone at the supported Time Travel point and verify its schema.
- Review the Time Travel and Fail-safe retention windows and storage effects.
- Create a Secure Data Share with authorized objects and add the approved consumer account.
Explanation
Correct Answer
B:Time Travel plus cloning can capture retained historical state for independent testing when object support permits. The corrective step addresses the missing requirement: A provider needs a recoverable test environment snapshot from a specific historical point before a schema migration. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model. That explains the role of “Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options”, but the present requirement calls for “Create an eligible zero-copy clone at the supported Time Travel point and verify its schema”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
C:Historical storage can remain recoverable or billable according to the table type and retention rules. That explains the role of “Review the Time Travel and Fail-safe retention windows and storage effects”, but the present requirement calls for “Create an eligible zero-copy clone at the supported Time Travel point and verify its schema”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
D:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. That explains the role of “Create a Secure Data Share with authorized objects and add the approved consumer account”, but the present requirement calls for “Create an eligible zero-copy clone at the supported Time Travel point and verify its schema”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
Question 544
During a pilot, engineers pursued an unrelated workaround: Use Snowsight worksheets with the intended role, database, schema and warehouse context. The required outcome remained unsatisfied: A deployment pipeline must create Snowflake objects through repeatable commands under version control. Which correction should the team prioritize?
- Use the supported Snowflake CLI and authenticated configuration for scripted deployment.
- Check effective session context and precedence of explicit USE statements over connection defaults.
- Use Snowsight worksheets with the intended role, database, schema and warehouse context.
- Configure an approved Snowflake ODBC driver and connection context.
Explanation
Correct Answer
A:CLI workflows allow controlled automation and environment selection without fragile UI clicking. The corrective step addresses the missing requirement: A deployment pipeline must create Snowflake objects through repeatable commands under version control. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:An explicit session command changes the active namespace used for later unqualified SQL references. That explains the role of “Check effective session context and precedence of explicit USE statements over connection defaults”, but the present requirement calls for “Use the supported Snowflake CLI and authenticated configuration for scripted deployment”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
C:Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions. That explains the role of “Use Snowsight worksheets with the intended role, database, schema and warehouse context”, but the present requirement calls for “Use the supported Snowflake CLI and authenticated configuration for scripted deployment”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
D:ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication. That explains the role of “Configure an approved Snowflake ODBC driver and connection context”, but the present requirement calls for “Use the supported Snowflake CLI and authenticated configuration for scripted deployment”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
Question 545
During a pilot, engineers pursued an unrelated workaround: Use object tagging and catalog metadata to track data classification and responsible owners. The required outcome remained unsatisfied: A developer tries to circumvent table masking by querying through a simple view over the same protected column. Which correction should the team prioritize?
- Retain masking enforcement on underlying governed columns and test effective role conditions.
- Use object tagging and catalog metadata to track data classification and responsible owners.
- Enforce policy-based governance and classification alongside least-privilege data access.
- Design a masking policy with clearly defined role-based conditional branches.
Explanation
Correct Answer
A:A view does not automatically remove column-level policy obligations inherited from its sources. The corrective step addresses the missing requirement: A developer tries to circumvent table masking by querying through a simple view over the same protected column. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. That explains the role of “Use object tagging and catalog metadata to track data classification and responsible owners”, but the present requirement calls for “Retain masking enforcement on underlying governed columns and test effective role conditions”: A view does not automatically remove column-level policy obligations inherited from its sources.
C:Table privileges alone may permit data use that governance and purpose restrictions prohibit. That explains the role of “Enforce policy-based governance and classification alongside least-privilege data access”, but the present requirement calls for “Retain masking enforcement on underlying governed columns and test effective role conditions”: A view does not automatically remove column-level policy obligations inherited from its sources.
D: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 “Retain masking enforcement on underlying governed columns and test effective role conditions”: A view does not automatically remove column-level policy obligations inherited from its sources.
Question 546
During a pilot, engineers pursued an unrelated workaround: Create a Snowflake task with an appropriate schedule and execution context. The required outcome remained unsatisfied: A stream-based task runs every minute even when the upstream table has no new changes. Which correction should the team prioritize?
- Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration.
- Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing.
- Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
- Create a Snowflake task with an appropriate schedule and execution context.
Explanation
Correct Answer
B:Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending. The corrective step addresses the missing requirement: A stream-based task runs every minute even when the upstream table has no new changes. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
C:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. That explains the role of “Define an auto-ingest Snowpipe with a stage and supported cloud event notifications”, but the present requirement calls for “Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
D:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. That explains the role of “Create a Snowflake task with an appropriate schedule and execution context”, but the present requirement calls for “Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
Question 547
During a pilot, engineers pursued an unrelated workaround: Enable AUTO_RESUME after verifying user role USAGE and operational expectations. The required outcome remained unsatisfied: A scheduled transformation warehouse suspends unexpectedly while its long query is still executing. Which correction should the team prioritize?
- Separate the interactive and transformation workloads into different warehouses.
- Configure multi-cluster auto-scale within supported edition limits.
- Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work.
- Enable AUTO_RESUME after verifying user role USAGE and operational expectations.
Explanation
Correct Answer
C:Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution. The corrective step addresses the missing requirement: A scheduled transformation warehouse suspends unexpectedly while its long query is still executing. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Separate the interactive and transformation workloads into different warehouses”, but the present requirement calls for “Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
B:Scaling out adds active clusters as workload concurrency rises to reduce queued requests. That explains the role of “Configure multi-cluster auto-scale within supported edition limits”, but the present requirement calls for “Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
D:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. That explains the role of “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”, but the present requirement calls for “Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running work”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
Question 548
During a pilot, engineers pursued an unrelated workaround: Move authentication to supported secure identity or credential storage and remove literals from source. The required outcome remained unsatisfied: An application server needs database connectivity using a mature Java integration instead of interactive worksheets. Which correction should the team prioritize?
- Check effective session context and precedence of explicit USE statements over connection defaults.
- Use the Snowflake JDBC driver with the approved credentials and network policy.
- Validate the supported Snowflake account identifier and connection endpoint configuration.
- Move authentication to supported secure identity or credential storage and remove literals from source.
Explanation
Correct Answer
B:JDBC provides a programmatic database connection for Java applications rather than a browser-only session. The corrective step addresses the missing requirement: An application server needs database connectivity using a mature Java integration instead of interactive worksheets. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:An explicit session command changes the active namespace used for later unqualified SQL references. That explains the role of “Check effective session context and precedence of explicit USE statements over connection defaults”, but the present requirement calls for “Use the Snowflake JDBC driver with the approved credentials and network policy”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
C:Client connections must target the correct account and supported hostname rather than an arbitrary database display label. That explains the role of “Validate the supported Snowflake account identifier and connection endpoint configuration”, but the present requirement calls for “Use the Snowflake JDBC driver with the approved credentials and network policy”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
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 the Snowflake JDBC driver with the approved credentials and network policy”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
Question 549
During a pilot, engineers pursued an unrelated workaround: Review Snowflake Trust Center findings and supported remediation recommendations. The required outcome remained unsatisfied: A data steward wants to block use of unapproved customer personal data in a marketing dataset despite role grants. Which correction should the team prioritize?
- Enforce policy-based governance and classification alongside least-privilege data access.
- Evaluate row access filtering and column masking independently with representative roles.
- Review Snowflake Trust Center findings and supported remediation recommendations.
- Use Snowflake-supported access history with an authorized investigation role.
Explanation
Correct Answer
A:Table privileges alone may permit data use that governance and purpose restrictions prohibit. The corrective step addresses the missing requirement: A data steward wants to block use of unapproved customer personal data in a marketing dataset despite role grants. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
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 “Enforce policy-based governance and classification alongside least-privilege data access”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
C: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 “Enforce policy-based governance and classification alongside least-privilege data access”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. That explains the role of “Use Snowflake-supported access history with an authorized investigation role”, but the present requirement calls for “Enforce policy-based governance and classification alongside least-privilege data access”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
Question 550
During a pilot, engineers pursued an unrelated workaround: Create a supported task graph with dependency links between tasks. The required outcome remained unsatisfied: A task keeps processing the same stream delta because a developer queries the stream without consuming changes inside committed DML. Which correction should the team prioritize?
- Consume the stream with a committed downstream DML transaction.
- Create a supported task graph with dependency links between tasks.
- Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
- Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
Explanation
Correct Answer
A:A stream offset advances when its changes are consumed by a committed transactional operation. The corrective step addresses the missing requirement: A task keeps processing the same stream delta because a developer queries the stream without consuming changes inside committed DML. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Consume the stream with a committed downstream DML transaction”: A stream offset advances when its changes are consumed by a committed transactional operation.
C:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. That explains the role of “Define an auto-ingest Snowpipe with a stage and supported cloud event notifications”, but the present requirement calls for “Consume the stream with a committed downstream DML transaction”: A stream offset advances when its changes are consumed by a committed transactional operation.
D:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table”, but the present requirement calls for “Consume the stream with a committed downstream DML transaction”: A stream offset advances when its changes are consumed by a committed transactional operation.