SnowPro Core COF-C03 Practice Test 69
Question 680
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 team wants employees to inherit existing report-reader grants when promoted to a new support-supervisor role. 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.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
Explanation
Correct Answer
A:Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually. The corrective step addresses the missing requirement: A team wants employees to inherit existing report-reader grants when promoted to a new support-supervisor role. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
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 “Create the intended role hierarchy using role-to-role grants”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
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 “Create the intended role hierarchy using role-to-role grants”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
D:Routine creation should use governed roles rather than expanding use of top-level account administration. That explains the role of “Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate”, but the present requirement calls for “Create the intended role hierarchy using role-to-role grants”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
Question 681
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: An organization wants recurring data loads from cloud storage but must not store permanent cloud access keys in stage DDL. Which correction should the team prioritize?
- Use a supported Snowflake storage integration for delegated cloud storage access.
- Define a JSON file format and load records into a VARIANT-capable table layout.
- Use COPY INTO an external stage location with an approved file format and storage integration.
- Set the correct CSV header-handling option in the file format.
Explanation
Correct Answer
A:Storage integrations manage cloud authentication using controlled trust and permission assignments. The corrective step addresses the missing requirement: An organization wants recurring data loads from cloud storage but must not store permanent cloud access keys in stage DDL. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Use a supported Snowflake storage integration for delegated cloud storage access”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
C:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. That explains the role of “Use COPY INTO an external stage location with an approved file format and storage integration”, but the present requirement calls for “Use a supported Snowflake storage integration for delegated cloud storage access”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
D:The loader needs explicit format rules to distinguish metadata rows from data records. That explains the role of “Set the correct CSV header-handling option in the file format”, but the present requirement calls for “Use a supported Snowflake storage integration for delegated cloud storage access”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
Question 682
During a pilot, engineers pursued an unrelated workaround: Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes. The required outcome remained unsatisfied: A query performs an expensive repeated aggregate over slowly changing source data for a frequently used dashboard. Which correction should the team prioritize?
- Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes.
- Inspect the Snowsight Query Profile and operator-level runtime statistics.
- Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs.
- Consider Query Acceleration Service for eligible selective large scans and aggregations.
Explanation
Correct Answer
C:Materialized views store selected precomputed results that can reduce repeated execution work. The corrective step addresses the missing requirement: A query performs an expensive repeated aggregate over slowly changing source data for a frequently used dashboard. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs”: Materialized views store selected precomputed results that can reduce repeated execution work.
B: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 a materialized view for the stable aggregation with monitored storage and maintenance costs”: Materialized views store selected precomputed results that can reduce repeated execution work.
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 “Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs”: Materialized views store selected precomputed results that can reduce repeated execution work.
Question 683
During a pilot, engineers pursued an unrelated workaround: Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker. The required outcome remained unsatisfied: A team wants a recoverable copy of a database before applying a risky transformation migration. Which correction should the team prioritize?
- Use a transient table only after approving its limited data-recovery guarantees.
- Use CREATE DATABASE CLONE with supported Time Travel options where applicable.
- Review the Time Travel and Fail-safe retention windows and storage effects.
- Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker.
Explanation
Correct Answer
B:A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks. The corrective step addresses the missing requirement: A team wants a recoverable copy of a database before applying a risky transformation migration. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 CREATE DATABASE CLONE with supported Time Travel options where applicable”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
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 CREATE DATABASE CLONE with supported Time Travel options where applicable”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
D:Verify its use in the approved role and runtime context. That explains the role of “Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker”, but the present requirement calls for “Use CREATE DATABASE CLONE with supported Time Travel options where applicable”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
Question 684
During a pilot, engineers pursued an unrelated workaround: Organize distinct databases or accounts with documented roles and change promotion boundaries. The required outcome remained unsatisfied: A regional company wants analysts to exchange authorized datasets without manually shipping full database extracts every night. 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.
- Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern.
Explanation
Correct Answer
D:Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset. The corrective step addresses the missing requirement: A regional company wants analysts to exchange authorized datasets without manually shipping full database extracts every night. 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 “Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
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 “Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
C:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. That explains the role of “Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage”, but the present requirement calls for “Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
Question 685
During a pilot, engineers pursued an unrelated workaround: Assign an available warehouse with USAGE to the connecting role and update the client context. The required outcome remained unsatisfied: A report fails because the session's current role does not have USAGE on the database and schema despite SELECT on the table. Which correction should the team prioritize?
- Use a supported overlapping key or token rotation procedure with staged validation.
- Grant the necessary ancestor object USAGE privileges to the intended role.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Assign an available warehouse with USAGE to the connecting role and update the client context.
Explanation
Correct Answer
B:Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights. The corrective step addresses the missing requirement: A report fails because the session's current role does not have USAGE on the database and schema despite SELECT on the table. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Grant the necessary ancestor object USAGE privileges to the intended role”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
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 “Grant the necessary ancestor object USAGE privileges to the intended role”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
D:SQL execution requires an accessible running or resumable warehouse, separate from table read rights. That explains the role of “Assign an available warehouse with USAGE to the connecting role and update the client context”, but the present requirement calls for “Grant the necessary ancestor object USAGE privileges to the intended role”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
Question 686
During a pilot, engineers pursued an unrelated workaround: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases. The required outcome remained unsatisfied: A CSV feed sometimes includes delimiter characters inside quoted fields and naive loads split columns incorrectly. Which correction should the team prioritize?
- Configure the CSV file format with the correct delimiter and enclosure options.
- Use COPY INTO a target table from a configured external stage and CSV file format.
- 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.
Explanation
Correct Answer
A:File-format parsing rules must match real source encoding and quote conventions. The corrective step addresses the missing requirement: A CSV feed sometimes includes delimiter characters inside quoted fields and naive loads split columns incorrectly. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches. That explains the role of “Use COPY INTO a target table from a configured external stage and CSV file format”, but the present requirement calls for “Configure the CSV file format with the correct delimiter and enclosure options”: File-format parsing rules must match real source encoding and quote conventions.
C: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 “Configure the CSV file format with the correct delimiter and enclosure options”: File-format parsing rules must match real source encoding and quote conventions.
D: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 “Configure the CSV file format with the correct delimiter and enclosure options”: File-format parsing rules must match real source encoding and quote conventions.
Question 687
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 few exceptionally large analytical scans dominate warehouse runtime while ordinary queries are fast. Which correction should the team prioritize?
- Inspect the Snowsight Query Profile and operator-level runtime statistics.
- Consider Query Acceleration Service for eligible selective large scans and aggregations.
- Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
- Compare search optimization and targeted materialized views against actual filter patterns.
Explanation
Correct Answer
B:QAS can offload parts of supported long-running queries to shared compute resources. The corrective step addresses the missing requirement: A few exceptionally large analytical scans dominate warehouse runtime while ordinary queries are fast. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Consider Query Acceleration Service for eligible selective large scans and aggregations”: QAS can offload parts of supported long-running queries to shared compute resources.
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 “Consider Query Acceleration Service for eligible selective large scans and aggregations”: QAS can offload parts of supported long-running queries to shared compute resources.
D:Clustering optimizes data locality for one key expression, while other services can target distinct access paths. That explains the role of “Compare search optimization and targeted materialized views against actual filter patterns”, but the present requirement calls for “Consider Query Acceleration Service for eligible selective large scans and aggregations”: QAS can offload parts of supported long-running queries to shared compute resources.
Question 688
During a pilot, engineers pursued an unrelated workaround: Use a transient table only after approving its limited data-recovery guarantees. The required outcome remained unsatisfied: An analyst thinks Snowflake Fail-safe allows immediate self-service SELECT against data from three months ago after Time Travel expired. Which correction should the team prioritize?
- Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive.
- Use a transient table only after approving its limited data-recovery guarantees.
- Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker.
- Review the Time Travel and Fail-safe retention windows and storage effects.
Explanation
Correct Answer
A:Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel. The corrective step addresses the missing requirement: An analyst thinks Snowflake Fail-safe allows immediate self-service SELECT against data from three months ago after Time Travel expired. 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 “Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
C:Verify its use in the approved role and runtime context. That explains the role of “Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker”, but the present requirement calls for “Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
D: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 “Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
Question 689
During a pilot, engineers pursued an unrelated workaround: Combine Snowflake SQL with supported Snowpark and native application development capabilities. The required outcome remained unsatisfied: A business is comparing its own managed servers with an elastic cloud analytics platform to handle unpredictable reporting demand. Which correction should the team prioritize?
- Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
- Combine Snowflake SQL with supported Snowpark and native application development capabilities.
- Correct the design to use independent warehouses reading shared Snowflake tables.
- Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
Explanation
Correct Answer
D:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. The corrective step addresses the missing requirement: A business is comparing its own managed servers with an elastic cloud analytics platform to handle unpredictable reporting demand. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
B:Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces. That explains the role of “Combine Snowflake SQL with supported Snowpark and native application development capabilities”, but the present requirement calls for “Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
C: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 “Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
Question 690
During a pilot, engineers pursued an unrelated workaround: Inspect Snowflake access and query history using properly privileged monitoring views. The required outcome remained unsatisfied: An application can read a table under one activated primary role but not when it changes its default role. Which correction should the team prioritize?
- Inspect CURRENT_ROLE and effective primary or secondary role grants for the session.
- Inspect Snowflake access and query history using properly privileged monitoring views.
- Revoke their assigned access roles or object grants through the controlled role hierarchy.
- Use a supported overlapping key or token rotation procedure with staged validation.
Explanation
Correct Answer
A:The active session role context determines which object privileges are available. The corrective step addresses the missing requirement: An application can read a table under one activated primary role but not when it changes its default role. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Inspect CURRENT_ROLE and effective primary or secondary role grants for the session”: The active session role context determines which object privileges are available.
C: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 “Inspect CURRENT_ROLE and effective primary or secondary role grants for the session”: The active session role context determines which object privileges are available.
D: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 CURRENT_ROLE and effective primary or secondary role grants for the session”: The active session role context determines which object privileges are available.