SnowPro Core COF-C03 Practice Test 70
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.
Question 691
During a pilot, engineers pursued an unrelated workaround: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema. The required outcome remained unsatisfied: A partner wants to unload daily query results to a secured external cloud-storage location as compressed files. Which correction should the team prioritize?
- Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
- Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants.
- Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
- Use COPY INTO an external stage location with an approved file format and storage integration.
Explanation
Correct Answer
D:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. The corrective step addresses the missing requirement: A partner wants to unload daily query results to a secured external cloud-storage location as compressed files. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 COPY INTO an external stage location with an approved file format and storage integration”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
B:Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table. That explains the role of “Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants”, but the present requirement calls for “Use COPY INTO an external stage location with an approved file format and storage integration”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
C:Name-based matching can align supported file columns without depending on file position alone. That explains the role of “Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema”, but the present requirement calls for “Use COPY INTO an external stage location with an approved file format and storage integration”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
Question 692
During a pilot, engineers pursued an unrelated workaround: Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs. The required outcome remained unsatisfied: A dashboard reruns identical SELECT statements and stakeholders want to understand why some executions are nearly instantaneous. Which correction should the team prioritize?
- Inspect Snowflake persisted query result reuse and conditions that invalidate it.
- Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy.
- Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes.
- Evaluate a materialized view for the stable aggregation with monitored storage and maintenance costs.
Explanation
Correct Answer
A:Result caching can return compatible prior query results without reexecuting a full warehouse scan. The corrective step addresses the missing requirement: A dashboard reruns identical SELECT statements and stakeholders want to understand why some executions are nearly instantaneous. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Large intermediate joins that exceed memory can create costly remote spill and longer runtimes. That explains the role of “Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy”, but the present requirement calls for “Inspect Snowflake persisted query result reuse and conditions that invalidate it”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
C: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 Snowflake persisted query result reuse and conditions that invalidate it”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
D: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 “Inspect Snowflake persisted query result reuse and conditions that invalidate it”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
Question 693
During a pilot, engineers pursued an unrelated workaround: Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window. The required outcome remained unsatisfied: A low-value transient staging table should avoid the additional permanent-table Fail-safe storage window. Which correction should the team prioritize?
- 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.
- Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window.
- Configure eligible extended Time Travel retention up to the edition's supported maximum.
Explanation
Correct Answer
A:Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics. The corrective step addresses the missing requirement: A low-value transient staging table should avoid the additional permanent-table Fail-safe storage window. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 a transient table only after approving its limited data-recovery guarantees”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
C:Time Travel supports restoration of recently dropped eligible objects while their retention remains valid. That explains the role of “Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window”, but the present requirement calls for “Use a transient table only after approving its limited data-recovery guarantees”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
D:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. That explains the role of “Configure eligible extended Time Travel retention up to the edition's supported maximum”, but the present requirement calls for “Use a transient table only after approving its limited data-recovery guarantees”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
Question 694
During a pilot, engineers pursued an unrelated workaround: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets. The required outcome remained unsatisfied: An engineering lead wants to use SQL, Python and application tooling within one governed data platform rather than export every dataset. Which correction should the team prioritize?
- Combine Snowflake SQL with supported Snowpark and native application development capabilities.
- Keep central Snowflake-managed database storage while running the teams on independent virtual warehouses.
- Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
- Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets.
Explanation
Correct Answer
A:Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces. The corrective step addresses the missing requirement: An engineering lead wants to use SQL, Python and application tooling within one governed data platform rather than export every dataset. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Combine Snowflake SQL with supported Snowpark and native application development capabilities”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
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 “Combine Snowflake SQL with supported Snowpark and native application development capabilities”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
D:The platform combines managed storage and compute with authentication and object privileges across its data lifecycle. That explains the role of “Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets”, but the present requirement calls for “Combine Snowflake SQL with supported Snowpark and native application development capabilities”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
Question 695
During a pilot, engineers pursued an unrelated workaround: Create a least-privileged custom account role with only the required database and object grants. The required outcome remained unsatisfied: An application should authenticate without a long-lived static password embedded in deployment files. Which correction should the team prioritize?
- Replace broad account administration with a custom reader role and intended warehouse usage privileges.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Create a least-privileged custom account role with only the required database and object grants.
- Inspect Snowflake access and query history using properly privileged monitoring views.
Explanation
Correct Answer
B:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. The corrective step addresses the missing requirement: An application should authenticate without a long-lived static password embedded in deployment files. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
C:Snowflake RBAC places permissions on roles that are granted to users, avoiding broad system administration rights. That explains the role of “Create a least-privileged custom account role with only the required database and object grants”, but the present requirement calls for “Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
D: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 “Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
Question 696
During a pilot, engineers pursued an unrelated workaround: Use COPY INTO a target table from a configured external stage and CSV file format. The required outcome remained unsatisfied: A data engineer needs to validate a batch of staged CSV files for parse errors before committing any target rows. Which correction should the team prioritize?
- 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.
- Use LIST on the intended stage and file path with appropriate privileges.
Explanation
Correct Answer
B:Bulk copy validation checks how staged rows would parse without treating the test as a production load. The corrective step addresses the missing requirement: A data engineer needs to validate a batch of staged CSV files for parse errors before committing any target rows. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
C: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 “Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
D:Listing stage contents validates location, pattern and access independently of a COPY operation. That explains the role of “Use LIST on the intended stage and file path with appropriate privileges”, but the present requirement calls for “Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
Question 697
During a pilot, engineers pursued an unrelated workaround: Evaluate supported search optimization for qualified semi-structured path predicates. The required outcome remained unsatisfied: An analytics job slows after its warehouse resumes from an extended suspension even though SQL has not changed. Which correction should the team prioritize?
- Evaluate supported search optimization for qualified semi-structured path predicates.
- Compare search optimization and targeted materialized views against actual filter patterns.
- Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
- Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy.
Explanation
Correct Answer
C:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. The corrective step addresses the missing requirement: An analytics job slows after its warehouse resumes from an extended suspension even though SQL has not changed. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Investigate local warehouse cache warm-up before attributing the slowdown solely to query text”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
B: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 “Investigate local warehouse cache warm-up before attributing the slowdown solely to query text”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
D:Large intermediate joins that exceed memory can create costly remote spill and longer runtimes. That explains the role of “Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy”, but the present requirement calls for “Investigate local warehouse cache warm-up before attributing the slowdown solely to query text”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
Question 698
During a pilot, engineers pursued an unrelated workaround: Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window. The required outcome remained unsatisfied: A regulated table needs historical recovery for more than a day under a supported Snowflake edition. Which correction should the team prioritize?
- 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 UNDROP TABLE under appropriate privileges within the Time Travel recovery window.
- Configure eligible extended Time Travel retention up to the edition's supported maximum.
Explanation
Correct Answer
D:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. The corrective step addresses the missing requirement: A regulated table needs historical recovery for more than a day under a supported Snowflake edition. 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 “Configure eligible extended Time Travel retention up to the edition's supported maximum”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
B: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 “Configure eligible extended Time Travel retention up to the edition's supported maximum”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
C:Time Travel supports restoration of recently dropped eligible objects while their retention remains valid. That explains the role of “Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window”, but the present requirement calls for “Configure eligible extended Time Travel retention up to the edition's supported maximum”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
Question 699
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: An executive assumes copying the same table into separate warehouses is necessary to isolate dashboards from transformations. Which correction should the team prioritize?
- Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers.
- Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern.
- Assign each workload its own virtual warehouse while retaining the common tables.
- Correct the design to use independent warehouses reading shared Snowflake tables.
Explanation
Correct Answer
D:Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table. The corrective step addresses the missing requirement: An executive assumes copying the same table into separate warehouses is necessary to isolate dashboards from transformations. 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 “Correct the design to use independent warehouses reading shared Snowflake tables”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
B:Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset. That explains the role of “Evaluate Snowflake Secure Data Sharing as a governed cross-account access pattern”, but the present requirement calls for “Correct the design to use independent warehouses reading shared Snowflake tables”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
C:Independent warehouses isolate compute usage and query queues even though both read the same storage objects. That explains the role of “Assign each workload its own virtual warehouse while retaining the common tables”, but the present requirement calls for “Correct the design to use independent warehouses reading shared Snowflake tables”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
Question 700
During a pilot, engineers pursued an unrelated workaround: Create the intended role hierarchy using role-to-role grants. The required outcome remained unsatisfied: A company already uses enterprise identity federation and wants employee Snowflake sign-ins tied to its central identity provider. Which correction should the team prioritize?
- Create a least-privileged custom account role with only the required database and object grants.
- Enforce the supported MFA and authentication policy for the target user population.
- Configure supported federated single sign-on with the organization's identity provider.
- Create the intended role hierarchy using role-to-role grants.
Explanation
Correct Answer
C:Federated SSO centralizes login assurance and deprovisioning for interactive employees. The corrective step addresses the missing requirement: A company already uses enterprise identity federation and wants employee Snowflake sign-ins tied to its central identity provider. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Snowflake RBAC places permissions on roles that are granted to users, avoiding broad system administration rights. That explains the role of “Create a least-privileged custom account role with only the required database and object grants”, but the present requirement calls for “Configure supported federated single sign-on with the organization's identity provider”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.
B:MFA raises assurance beyond a single compromised password or reused secret. That explains the role of “Enforce the supported MFA and authentication policy for the target user population”, but the present requirement calls for “Configure supported federated single sign-on with the organization's identity provider”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.
D: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 “Configure supported federated single sign-on with the organization's identity provider”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.