SnowPro Core COF-C03 Practice Test 73
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.
Question 721
During a pilot, engineers pursued an unrelated workaround: Create or use a supported internal Snowflake stage with appropriate file format and grants. The required outcome remained unsatisfied: An ETL group wants to remove staged temporary files only after successful ingestion and retention approval. Which correction should the team prioritize?
- Choose an appropriate COPY INTO ON_ERROR setting and inspect load results.
- Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
- Use a controlled post-load removal policy or supported COPY purge behavior where appropriate.
- Create or use a supported internal Snowflake stage with appropriate file format and grants.
Explanation
Correct Answer
C:Stage file deletion and data loading are separate governance decisions that require verification. The corrective step addresses the missing requirement: An ETL group wants to remove staged temporary files only after successful ingestion and retention approval. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:COPY loading error behavior is configurable; silent skipping without review can hide data loss. That explains the role of “Choose an appropriate COPY INTO ON_ERROR setting and inspect load results”, but the present requirement calls for “Use a controlled post-load removal policy or supported COPY purge behavior where appropriate”: Stage file deletion and data loading are separate governance decisions that require verification.
B:Bulk copy validation checks how staged rows would parse without treating the test as a production load. That explains the role of “Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases”, but the present requirement calls for “Use a controlled post-load removal policy or supported COPY purge behavior where appropriate”: Stage file deletion and data loading are separate governance decisions that require verification.
D:Internal stages allow Snowflake-managed file staging without direct external cloud bucket access. That explains the role of “Create or use a supported internal Snowflake stage with appropriate file format and grants”, but the present requirement calls for “Use a controlled post-load removal policy or supported COPY purge behavior where appropriate”: Stage file deletion and data loading are separate governance decisions that require verification.
Question 722
During a pilot, engineers pursued an unrelated workaround: Inspect the Snowsight Query Profile and operator-level runtime statistics. The required outcome remained unsatisfied: A team wants to improve selectivity for nested VARIANT key searches rather than clustering every whole document. Which correction should the team prioritize?
- Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
- Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
- Inspect the Snowsight Query Profile and operator-level runtime statistics.
- Evaluate supported search optimization for qualified semi-structured path predicates.
Explanation
Correct Answer
D:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. The corrective step addresses the missing requirement: A team wants to improve selectivity for nested VARIANT key searches rather than clustering every whole document. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Evaluate supported search optimization for qualified semi-structured path predicates”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
B:Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter. That explains the role of “Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid”, but the present requirement calls for “Evaluate supported search optimization for qualified semi-structured path predicates”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
C:Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans. That explains the role of “Inspect the Snowsight Query Profile and operator-level runtime statistics”, but the present requirement calls for “Evaluate supported search optimization for qualified semi-structured path predicates”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
Question 723
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: A data provider must make a subset of rows available to a partner while retaining sensitive attributes in the underlying table. Which correction should the team prioritize?
- Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
- Verify share grants and the required database and schema object privileges in the provider account.
- Expose a governed secure view through a direct share rather than granting raw base-table access.
- Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
Explanation
Correct Answer
C:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. The corrective step addresses the missing requirement: A data provider must make a subset of rows available to a partner while retaining sensitive attributes in the underlying table. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Expose a governed secure view through a direct share rather than granting raw base-table access”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
B: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 “Expose a governed secure view through a direct share rather than granting raw base-table access”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
D:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. That explains the role of “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”, but the present requirement calls for “Expose a governed secure view through a direct share rather than granting raw base-table access”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
Question 724
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 large organization wants to distinguish Snowflake operational charges caused by compute from charges caused by stored data. Which correction should the team prioritize?
- Organize distinct databases or accounts with documented roles and change promotion boundaries.
- Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
- Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage.
- Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
Explanation
Correct Answer
C:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. The corrective step addresses the missing requirement: A large organization wants to distinguish Snowflake operational charges caused by compute from charges caused by stored data. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
B: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 “Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
D: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 “Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
Question 725
During a pilot, engineers pursued an unrelated workaround: Use a supported overlapping key or token rotation procedure with staged validation. The required outcome remained unsatisfied: An organization asks which default system role should own routine data objects rather than using ACCOUNTADMIN for all development. Which correction should the team prioritize?
- Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
- Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges.
- Use a supported overlapping key or token rotation procedure with staged validation.
- Grant the necessary ancestor object USAGE privileges to the intended role.
Explanation
Correct Answer
A:Routine creation should use governed roles rather than expanding use of top-level account administration. The corrective step addresses the missing requirement: An organization asks which default system role should own routine data objects rather than using ACCOUNTADMIN for all development. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate”: Routine creation should use governed roles rather than expanding use of top-level account administration.
C:Planned rotation allows new credentials to be tested before revoking the old authentication method. That explains the role of “Use a supported overlapping key or token rotation procedure with staged validation”, but the present requirement calls for “Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate”: Routine creation should use governed roles rather than expanding use of top-level account administration.
D:Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights. That explains the role of “Grant the necessary ancestor object USAGE privileges to the intended role”, but the present requirement calls for “Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate”: Routine creation should use governed roles rather than expanding use of top-level account administration.
Question 726
During a pilot, engineers pursued an unrelated workaround: Define a JSON file format and load records into a VARIANT-capable table layout. The required outcome remained unsatisfied: A large CSV file takes unusually long to parse and the team is considering splitting the source into parallelizable chunks. Which correction should the team prioritize?
- Define a JSON file format and load records into a VARIANT-capable table layout.
- Capture supported METADATA$ filename and load timestamp information during staging ingestion.
- Use a supported Snowflake storage integration for delegated cloud storage access.
- Tune staged file sizing and compression based on Snowflake loading best practices.
Explanation
Correct Answer
D:File granularity and format affect parallelism and parsing overhead for warehouse-based loads. The corrective step addresses the missing requirement: A large CSV file takes unusually long to parse and the team is considering splitting the source into parallelizable chunks. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Tune staged file sizing and compression based on Snowflake loading best practices”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
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 “Tune staged file sizing and compression based on Snowflake loading best practices”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
C: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 “Tune staged file sizing and compression based on Snowflake loading best practices”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
Question 727
During a pilot, engineers pursued an unrelated workaround: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid. The required outcome remained unsatisfied: A DBA activates clustering on every table without checking table size or query access patterns. Which correction should the team prioritize?
- Prioritize clustering only where measured pruning gains justify reclustering costs.
- Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid.
- Evaluate supported search optimization for qualified semi-structured path predicates.
- Consider Query Acceleration Service for eligible selective large scans and aggregations.
Explanation
Correct Answer
A:Reclustering creates maintenance compute and storage overhead and does not improve every query. The corrective step addresses the missing requirement: A DBA activates clustering on every table without checking table size or query access patterns. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter. That explains the role of “Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid”, but the present requirement calls for “Prioritize clustering only where measured pruning gains justify reclustering costs”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
C:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. That explains the role of “Evaluate supported search optimization for qualified semi-structured path predicates”, but the present requirement calls for “Prioritize clustering only where measured pruning gains justify reclustering costs”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
D:QAS can offload parts of supported long-running queries to shared compute resources. That explains the role of “Consider Query Acceleration Service for eligible selective large scans and aggregations”, but the present requirement calls for “Prioritize clustering only where measured pruning gains justify reclustering costs”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
Question 728
During a pilot, engineers pursued an unrelated workaround: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls. The required outcome remained unsatisfied: A non-Snowflake customer needs governed access to a provider dataset and does not want to operate its own existing Snowflake account. Which correction should the team prioritize?
- Create an approved Snowflake Marketplace listing for the supported data product.
- Expose a governed secure view through a direct share rather than granting raw base-table access.
- Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
- Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
Explanation
Correct Answer
D:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. The corrective step addresses the missing requirement: A non-Snowflake customer needs governed access to a provider dataset and does not want to operate its own existing Snowflake account. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Use an approved Snowflake Reader Account managed through the provider's sharing workflow”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
B:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. That explains the role of “Expose a governed secure view through a direct share rather than granting raw base-table access”, but the present requirement calls for “Use an approved Snowflake Reader Account managed through the provider's sharing workflow”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
C:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. That explains the role of “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”, but the present requirement calls for “Use an approved Snowflake Reader Account managed through the provider's sharing workflow”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
Question 729
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 team argues that cloud services is the layer that scans all data blocks when a reporting SQL statement executes. Which correction should the team prioritize?
- Verify the active database and schema context used for unqualified object references.
- Query the committed Snowflake table from the second warehouse under an authorized role.
- Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization.
- Investigate authentication and authorization in the cloud services control path and the selected role.
Explanation
Correct Answer
C:Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution. The corrective step addresses the missing requirement: A team argues that cloud services is the layer that scans all data blocks when a reporting SQL statement executes. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
B:Committed persisted storage is shared across warehouses; a data copy is not inherently required between compute clusters. That explains the role of “Query the committed Snowflake table from the second warehouse under an authorized role”, but the present requirement calls for “Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
D:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. That explains the role of “Investigate authentication and authorization in the cloud services control path and the selected role”, but the present requirement calls for “Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
Question 730
During a pilot, engineers pursued an unrelated workaround: Use a supported overlapping key or token rotation procedure with staged validation. The required outcome remained unsatisfied: A security engineer must find who ran a sensitive SQL query and whether the operation succeeded. Which correction should the team prioritize?
- Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Use a supported overlapping key or token rotation procedure with staged validation.
- Inspect Snowflake access and query history using properly privileged monitoring views.
Explanation
Correct Answer
D:Account activity history connects query operations to principals and execution context for investigation. The corrective step addresses the missing requirement: A security engineer must find who ran a sensitive SQL query and whether the operation succeeded. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Inspect Snowflake access and query history using properly privileged monitoring views”: Account activity history connects query operations to principals and execution context for investigation.
B: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 “Inspect Snowflake access and query history using properly privileged monitoring views”: Account activity history connects query operations to principals and execution context for investigation.
C:Planned rotation allows new credentials to be tested before revoking the old authentication method. That explains the role of “Use a supported overlapping key or token rotation procedure with staged validation”, but the present requirement calls for “Inspect Snowflake access and query history using properly privileged monitoring views”: Account activity history connects query operations to principals and execution context for investigation.