SnowPro Core COF-C03 Practice Test 72
Question 710
During a pilot, engineers pursued an unrelated workaround: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. The required outcome remained unsatisfied: A Snowflake account should accept application connections only from approved office egress IP addresses. Which correction should the team prioritize?
- Inspect Snowflake access and query history using properly privileged monitoring views.
- Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Revoke their assigned access roles or object grants through the controlled role hierarchy.
Explanation
Correct Answer
B:Network policies constrain permitted source addresses independently from SQL object grants. The corrective step addresses the missing requirement: A Snowflake account should accept application connections only from approved office egress IP addresses. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Account activity history connects query operations to principals and execution context for investigation. That explains the role of “Inspect Snowflake access and query history using properly privileged monitoring views”, but the present requirement calls for “Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges”: Network policies constrain permitted source addresses independently from SQL object grants.
C:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. That explains the role of “Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely”, but the present requirement calls for “Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges”: Network policies constrain permitted source addresses independently from SQL object grants.
D:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “Revoke their assigned access roles or object grants through the controlled role hierarchy”, but the present requirement calls for “Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges”: Network policies constrain permitted source addresses independently from SQL object grants.
Question 711
During a pilot, engineers pursued an unrelated workaround: Configure the CSV file format with the correct delimiter and enclosure options. The required outcome remained unsatisfied: A team wants to see all staged files for a new source before executing the production load. Which correction should the team prioritize?
- Configure the CSV file format with the correct delimiter and enclosure options.
- Capture supported METADATA$ filename and load timestamp information during staging ingestion.
- Use LIST on the intended stage and file path with appropriate privileges.
- Use a supported Snowflake storage integration for delegated cloud storage access.
Explanation
Correct Answer
C:Listing stage contents validates location, pattern and access independently of a COPY operation. The corrective step addresses the missing requirement: A team wants to see all staged files for a new source before executing the production load. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:File-format parsing rules must match real source encoding and quote conventions. That explains the role of “Configure the CSV file format with the correct delimiter and enclosure options”, but the present requirement calls for “Use LIST on the intended stage and file path with appropriate privileges”: Listing stage contents validates location, pattern and access independently of a COPY operation.
B:Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers. That explains the role of “Capture supported METADATA$ filename and load timestamp information during staging ingestion”, but the present requirement calls for “Use LIST on the intended stage and file path with appropriate privileges”: Listing stage contents validates location, pattern and access independently of a COPY operation.
D:Storage integrations manage cloud authentication using controlled trust and permission assignments. That explains the role of “Use a supported Snowflake storage integration for delegated cloud storage access”, but the present requirement calls for “Use LIST on the intended stage and file path with appropriate privileges”: Listing stage contents validates location, pattern and access independently of a COPY operation.
Question 712
During a pilot, engineers pursued an unrelated workaround: Inspect Snowflake persisted query result reuse and conditions that invalidate it. The required outcome remained unsatisfied: An engineer wants to understand the most expensive stage of a Snowflake SQL plan rather than guess from final duration. Which correction should the team prioritize?
- Inspect the Snowsight Query Profile and operator-level runtime statistics.
- Inspect Snowflake persisted query result reuse and conditions that invalidate it.
- Inspect join cardinality, join keys and query plan before simply adding compute.
- Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes.
Explanation
Correct Answer
A:Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans. The corrective step addresses the missing requirement: An engineer wants to understand the most expensive stage of a Snowflake SQL plan rather than guess from final duration. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Result caching can return compatible prior query results without reexecuting a full warehouse scan. That explains the role of “Inspect Snowflake persisted query result reuse and conditions that invalidate it”, but the present requirement calls for “Inspect the Snowsight Query Profile and operator-level runtime statistics”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
C:Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size. That explains the role of “Inspect join cardinality, join keys and query plan before simply adding compute”, but the present requirement calls for “Inspect the Snowsight Query Profile and operator-level runtime statistics”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
D:A fair warehouse performance test must separate cache effects from the resource configuration change. That explains the role of “Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes”, but the present requirement calls for “Inspect the Snowsight Query Profile and operator-level runtime statistics”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
Question 713
During a pilot, engineers pursued an unrelated workaround: Use CREATE DATABASE CLONE with supported Time Travel options where applicable. The required outcome remained unsatisfied: A team wants to recover a mistakenly deleted schema and all its eligible objects without manually reconstructing DDL. Which correction should the team prioritize?
- Use supported UNDROP SCHEMA within the configured Time Travel window.
- Use a transient table only after approving its limited data-recovery guarantees.
- Review the Time Travel and Fail-safe retention windows and storage effects.
- Use CREATE DATABASE CLONE with supported Time Travel options where applicable.
Explanation
Correct Answer
A:Time Travel object recovery can restore eligible dropped schema structures while retention is valid. The corrective step addresses the missing requirement: A team wants to recover a mistakenly deleted schema and all its eligible objects without manually reconstructing DDL. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics. That explains the role of “Use a transient table only after approving its limited data-recovery guarantees”, but the present requirement calls for “Use supported UNDROP SCHEMA within the configured Time Travel window”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
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 “Use supported UNDROP SCHEMA within the configured Time Travel window”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
D:A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks. That explains the role of “Use CREATE DATABASE CLONE with supported Time Travel options where applicable”, but the present requirement calls for “Use supported UNDROP SCHEMA within the configured Time Travel window”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
Question 714
During a pilot, engineers pursued an unrelated workaround: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers. The required outcome remained unsatisfied: A company needs separate development and production data environments while reusing standard governance patterns. Which correction should the team prioritize?
- Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
- Correct the design to use independent warehouses reading shared Snowflake tables.
- Use the fully managed Snowflake service rather than installing a self-hosted database cluster.
- Organize distinct databases or accounts with documented roles and change promotion boundaries.
Explanation
Correct Answer
D:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. The corrective step addresses the missing requirement: A company needs separate development and production data environments while reusing standard governance patterns. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. That explains the role of “Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers”, but the present requirement calls for “Organize distinct databases or accounts with documented roles and change promotion boundaries”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
B:Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table. That explains the role of “Correct the design to use independent warehouses reading shared Snowflake tables”, but the present requirement calls for “Organize distinct databases or accounts with documented roles and change promotion boundaries”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
C:Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design. That explains the role of “Use the fully managed Snowflake service rather than installing a self-hosted database cluster”, but the present requirement calls for “Organize distinct databases or accounts with documented roles and change promotion boundaries”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
Question 715
During a pilot, engineers pursued an unrelated workaround: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles. The required outcome remained unsatisfied: Sensitive regulatory data must use private connectivity rather than traversing a public internet endpoint for supported clients. Which correction should the team prioritize?
- Create the intended role hierarchy using role-to-role grants.
- Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority.
- Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition.
- Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles.
Explanation
Correct Answer
C:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. The corrective step addresses the missing requirement: Sensitive regulatory data must use private connectivity rather than traversing a public internet endpoint for supported clients. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually. That explains the role of “Create the intended role hierarchy using role-to-role grants”, but the present requirement calls for “Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
B:Read-only business access should be separated from grant management and object modification privileges. That explains the role of “Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority”, but the present requirement calls for “Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
D:Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access. That explains the role of “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”, but the present requirement calls for “Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
Question 716
During a pilot, engineers pursued an unrelated workaround: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. The required outcome remained unsatisfied: A file-loading task fails because the target column names differ in case from incoming Parquet fields. Which correction should the team prioritize?
- Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
- Use a controlled post-load removal policy or supported COPY purge behavior where appropriate.
- Use COPY INTO with a carefully tested PATTERN or specific staged prefix.
- Define a JSON file format and load records into a VARIANT-capable table layout.
Explanation
Correct Answer
A:Name-based matching can align supported file columns without depending on file position alone. The corrective step addresses the missing requirement: A file-loading task fails because the target column names differ in case from incoming Parquet fields. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Stage file deletion and data loading are separate governance decisions that require verification. That explains the role of “Use a controlled post-load removal policy or supported COPY purge behavior where appropriate”, but the present requirement calls for “Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema”: Name-based matching can align supported file columns without depending on file position alone.
C:Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch. That explains the role of “Use COPY INTO with a carefully tested PATTERN or specific staged prefix”, but the present requirement calls for “Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema”: Name-based matching can align supported file columns without depending on file position alone.
D:JSON loading should preserve nested structure instead of assuming fixed CSV column positions. That explains the role of “Define a JSON file format and load records into a VARIANT-capable table layout”, but the present requirement calls for “Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema”: Name-based matching can align supported file columns without depending on file position alone.
Question 717
During a pilot, engineers pursued an unrelated workaround: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. The required outcome remained unsatisfied: A table uses a transformation on the filter column and pruning disappears compared with a simple range predicate. Which correction should the team prioritize?
- Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
- Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs.
- Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
- Prioritize clustering only where measured pruning gains justify reclustering costs.
Explanation
Correct Answer
A:Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter. The corrective step addresses the missing requirement: A table uses a transformation on the filter column and pruning disappears compared with a simple range predicate. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Materialized views store selected precomputed results that can reduce repeated execution work. That explains the role of “Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs”, but the present requirement calls for “Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
C:Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources. That explains the role of “Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size”, but the present requirement calls for “Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
D:Reclustering creates maintenance compute and storage overhead and does not improve every query. That explains the role of “Prioritize clustering only where measured pruning gains justify reclustering costs”, but the present requirement calls for “Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
Question 718
During a pilot, engineers pursued an unrelated workaround: Use separate secured listings or shares with scoped recipients and approved views. The required outcome remained unsatisfied: A provider wants a partner already using Snowflake to read a governed dataset without copying files into the partner's cloud account. Which correction should the team prioritize?
- Use separate secured listings or shares with scoped recipients and approved views.
- Create an approved Snowflake Marketplace listing for the supported data product.
- Create a Secure Data Share with authorized objects and add the approved consumer account.
- Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
Explanation
Correct Answer
C:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. The corrective step addresses the missing requirement: A provider wants a partner already using Snowflake to read a governed dataset without copying files into the partner's cloud account. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Individual product authorization reduces inadvertent cross-tenant data access. That explains the role of “Use separate secured listings or shares with scoped recipients and approved views”, but the present requirement calls for “Create a Secure Data Share with authorized objects and add the approved consumer account”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
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 “Create a Secure Data Share with authorized objects and add the approved consumer account”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
D:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. That explains the role of “Use an approved Snowflake Reader Account managed through the provider's sharing workflow”, but the present requirement calls for “Create a Secure Data Share with authorized objects and add the approved consumer account”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
Question 719
During a pilot, engineers pursued an unrelated workaround: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. The required outcome remained unsatisfied: A data analyst wants to test transformation results quickly without moving source data to a local laptop. Which correction should the team prioritize?
- Keep central Snowflake-managed database storage while running the teams on independent virtual warehouses.
- Execute supported Snowflake SQL transformations using an appropriate compute warehouse.
- Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
- Organize distinct databases or accounts with documented roles and change promotion boundaries.
Explanation
Correct Answer
B:Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls. The corrective step addresses the missing requirement: A data analyst wants to test transformation results quickly without moving source data to a local laptop. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth. That explains the role of “Keep central Snowflake-managed database storage while running the teams on independent virtual warehouses”, but the present requirement calls for “Execute supported Snowflake SQL transformations using an appropriate compute warehouse”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
C:Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption. That explains the role of “Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region”, but the present requirement calls for “Execute supported Snowflake SQL transformations using an appropriate compute warehouse”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
D:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. That explains the role of “Organize distinct databases or accounts with documented roles and change promotion boundaries”, but the present requirement calls for “Execute supported Snowflake SQL transformations using an appropriate compute warehouse”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
Question 720
During a pilot, engineers pursued an unrelated workaround: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges. The required outcome remained unsatisfied: An operator needs to rotate credentials for a service identity without breaking every production connector at once. Which correction should the team prioritize?
- Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
- Use a supported overlapping key or token rotation procedure with staged validation.
- Configure a supported OAuth security integration and validate granted session role behavior.
- Replace broad account administration with a custom reader role and intended warehouse usage privileges.
Explanation
Correct Answer
B:Planned rotation allows new credentials to be tested before revoking the old authentication method. The corrective step addresses the missing requirement: An operator needs to rotate credentials for a service identity without breaking every production connector at once. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Network policies constrain permitted source addresses independently from SQL object grants. That explains the role of “Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges”, but the present requirement calls for “Use a supported overlapping key or token rotation procedure with staged validation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.
C:OAuth enables delegated token-based authentication while token and role privileges still constrain data access. That explains the role of “Configure a supported OAuth security integration and validate granted session role behavior”, but the present requirement calls for “Use a supported overlapping key or token rotation procedure with staged validation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.
D:Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow. That explains the role of “Replace broad account administration with a custom reader role and intended warehouse usage privileges”, but the present requirement calls for “Use a supported overlapping key or token rotation procedure with staged validation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.