SnowPro Core COF-C03 Practice Test 75
Question 740
During a pilot, engineers pursued an unrelated workaround: Grant the necessary ancestor object USAGE privileges to the intended role. The required outcome remained unsatisfied: A development role has been granted to a higher-level analyst role in the wrong direction, leaving analysts without expected privileges. Which correction should the team prioritize?
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships.
- Grant the necessary ancestor object USAGE privileges to the intended role.
- Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
Explanation
Correct Answer
B:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. The corrective step addresses the missing requirement: A development role has been granted to a higher-level analyst role in the wrong direction, leaving analysts without expected privileges. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships”: Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
C: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 “Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships”: Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
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 “Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships”: Privilege flow follows the role hierarchy and cannot be inferred from role names alone.
Question 741
During a pilot, engineers pursued an unrelated workaround: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional. The required outcome remained unsatisfied: An administrator needs to troubleshoot a historical load failure from a particular staged file. Which correction should the team prioritize?
- Inspect COPY_HISTORY or supported load history and detailed COPY results.
- Inspect Snowflake load metadata and avoid forcing duplicates unless intentional.
- Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases.
- Configure the CSV file format with the correct delimiter and enclosure options.
Explanation
Correct Answer
A:Load history provides observable file-level execution and error outcomes for ingestion investigations. The corrective step addresses the missing requirement: An administrator needs to troubleshoot a historical load failure from a particular staged file. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards. That explains the role of “Inspect Snowflake load metadata and avoid forcing duplicates unless intentional”, but the present requirement calls for “Inspect COPY_HISTORY or supported load history and detailed COPY results”: Load history provides observable file-level execution and error outcomes for ingestion investigations.
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 “Inspect COPY_HISTORY or supported load history and detailed COPY results”: Load history provides observable file-level execution and error outcomes for ingestion investigations.
D: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 “Inspect COPY_HISTORY or supported load history and detailed COPY results”: Load history provides observable file-level execution and error outcomes for ingestion investigations.
Question 742
During a pilot, engineers pursued an unrelated workaround: Compare search optimization and targeted materialized views against actual filter patterns. The required outcome remained unsatisfied: A benchmark used a single cached query to claim a warehouse resize delivered a tenfold performance improvement. Which correction should the team prioritize?
- Compare search optimization and targeted materialized views against actual filter patterns.
- 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.
- Inspect join cardinality, join keys and query plan before simply adding compute.
Explanation
Correct Answer
B:A fair warehouse performance test must separate cache effects from the resource configuration change. The corrective step addresses the missing requirement: A benchmark used a single cached query to claim a warehouse resize delivered a tenfold performance improvement. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes”: A fair warehouse performance test must separate cache effects from the resource configuration change.
C: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 “Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes”: A fair warehouse performance test must separate cache effects from the resource configuration change.
D: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 “Control for result cache, cold starts, query text and comparable input data before comparing warehouse sizes”: A fair warehouse performance test must separate cache effects from the resource configuration change.
Question 743
During a pilot, engineers pursued an unrelated workaround: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. The required outcome remained unsatisfied: An administrator shared a secure view but the recipient cannot see it in the imported database. Which correction should the team prioritize?
- Use separate secured listings or shares with scoped recipients and approved views.
- Verify share grants and the required database and schema object privileges in the provider account.
- Create a Secure Data Share with authorized objects and add the approved consumer account.
- Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
Explanation
Correct Answer
B:Cross-account access requires the provider to grant the intended objects and containing namespace appropriately. The corrective step addresses the missing requirement: An administrator shared a secure view but the recipient cannot see it in the imported database. 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 “Verify share grants and the required database and schema object privileges in the provider account”: Cross-account access requires the provider to grant the intended objects and containing namespace appropriately.
C:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. That explains the role of “Create a Secure Data Share with authorized objects and add the approved consumer account”, but the present requirement calls for “Verify share grants and the required database and schema object privileges in the provider account”: Cross-account access requires the provider to grant the intended objects and containing namespace appropriately.
D:Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model. That explains the role of “Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options”, but the present requirement calls for “Verify share grants and the required database and schema object privileges in the provider account”: Cross-account access requires the provider to grant the intended objects and containing namespace appropriately.
Question 744
During a pilot, engineers pursued an unrelated workaround: Allocate distinct warehouses to the jobs and use the same authorized database storage objects. The required outcome remained unsatisfied: A workload slows after many expensive joins even though the metadata service responds normally. Which correction should the team prioritize?
- Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
- Explain that suspending compute does not delete persisted Snowflake table data.
- Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization.
- Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage.
Explanation
Correct Answer
D:Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution. The corrective step addresses the missing requirement: A workload slows after many expensive joins even though the metadata service responds normally. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data. That explains the role of “Allocate distinct warehouses to the jobs and use the same authorized database storage objects”, but the present requirement calls for “Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage”: Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution.
B:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “Explain that suspending compute does not delete persisted Snowflake table data”, but the present requirement calls for “Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage”: Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution.
C:Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution. That explains the role of “Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization”, but the present requirement calls for “Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage”: Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution.
Question 745
During a pilot, engineers pursued an unrelated workaround: Configure a supported OAuth security integration and validate granted session role behavior. The required outcome remained unsatisfied: A team wants shared query permissions without giving every analyst the ability to change the security model. 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.
- Revoke their assigned access roles or object grants through the controlled role hierarchy.
- Configure a supported OAuth security integration and validate granted session role behavior.
Explanation
Correct Answer
B:Read-only business access should be separated from grant management and object modification privileges. The corrective step addresses the missing requirement: A team wants shared query permissions without giving every analyst the ability to change the security model. 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 “Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority”: Read-only business access should be separated from grant management and object modification privileges.
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 “Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority”: Read-only business access should be separated from grant management and object modification privileges.
D: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 “Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority”: Read-only business access should be separated from grant management and object modification privileges.
Question 746
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: An engineer must load from a restricted internal stage before the source files are copied into an external bucket. Which correction should the team prioritize?
- Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema.
- Use COPY INTO a target table from a configured external stage and CSV file format.
- Inspect COPY_HISTORY or supported load history and detailed COPY results.
- Create or use a supported internal Snowflake stage with appropriate file format and grants.
Explanation
Correct Answer
D:Internal stages allow Snowflake-managed file staging without direct external cloud bucket access. The corrective step addresses the missing requirement: An engineer must load from a restricted internal stage before the source files are copied into an external bucket. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A: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 “Create or use a supported internal Snowflake stage with appropriate file format and grants”: Internal stages allow Snowflake-managed file staging without direct external cloud bucket access.
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 “Create or use a supported internal Snowflake stage with appropriate file format and grants”: Internal stages allow Snowflake-managed file staging without direct external cloud bucket access.
C:Load history provides observable file-level execution and error outcomes for ingestion investigations. That explains the role of “Inspect COPY_HISTORY or supported load history and detailed COPY results”, but the present requirement calls for “Create or use a supported internal Snowflake stage with appropriate file format and grants”: Internal stages allow Snowflake-managed file staging without direct external cloud bucket access.
Question 747
During a pilot, engineers pursued an unrelated workaround: Configure multi-cluster auto-scale within supported edition limits. The required outcome remained unsatisfied: A single complex SQL query needs more processing power, but the warehouse has no significant concurrency queue. Which correction should the team prioritize?
- Compare warehouse load, credits and query profile statistics before and after configuration changes.
- Configure multi-cluster auto-scale within supported edition limits.
- Benchmark increasing warehouse size rather than adding multi-cluster capacity first.
- Enable AUTO_RESUME after verifying user role USAGE and operational expectations.
Explanation
Correct Answer
C:Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries. The corrective step addresses the missing requirement: A single complex SQL query needs more processing power, but the warehouse has no significant concurrency queue. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Capacity should be evaluated against actual queue time, execution time and consumed credits. That explains the role of “Compare warehouse load, credits and query profile statistics before and after configuration changes”, but the present requirement calls for “Benchmark increasing warehouse size rather than adding multi-cluster capacity first”: Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries.
B:Scaling out adds active clusters as workload concurrency rises to reduce queued requests. That explains the role of “Configure multi-cluster auto-scale within supported edition limits”, but the present requirement calls for “Benchmark increasing warehouse size rather than adding multi-cluster capacity first”: Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries.
D:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. That explains the role of “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”, but the present requirement calls for “Benchmark increasing warehouse size rather than adding multi-cluster capacity first”: Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries.
Question 748
During a pilot, engineers pursued an unrelated workaround: Create an approved Snowflake Marketplace listing for the supported data product. The required outcome remained unsatisfied: A provider wants to stop a former partner from accessing a shared dataset without deleting source tables. Which correction should the team prioritize?
- Remove that consumer from the authorized share or revoke the relevant shared object grants.
- Create an approved Snowflake Marketplace listing for the supported data product.
- Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
- Expose a governed secure view through a direct share rather than granting raw base-table access.
Explanation
Correct Answer
A:Provider-owned grants control consumer access independently of data persistence. The corrective step addresses the missing requirement: A provider wants to stop a former partner from accessing a shared dataset without deleting source tables. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
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 “Remove that consumer from the authorized share or revoke the relevant shared object grants”: Provider-owned grants control consumer access independently of data persistence.
C: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 “Remove that consumer from the authorized share or revoke the relevant shared object grants”: Provider-owned grants control consumer access independently of data persistence.
D: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 “Remove that consumer from the authorized share or revoke the relevant shared object grants”: Provider-owned grants control consumer access independently of data persistence.
Question 749
During a pilot, engineers pursued an unrelated workaround: Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile. The required outcome remained unsatisfied: A BI tool reports inconsistent object resolution after changing the selected database and schema in a session. Which correction should the team prioritize?
- Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
- Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile.
- Verify the active database and schema context used for unqualified object references.
- Investigate authentication and authorization in the cloud services control path and the selected role.
Explanation
Correct Answer
C:Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions. The corrective step addresses the missing requirement: A BI tool reports inconsistent object resolution after changing the selected database and schema in a session. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. That explains the role of “Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work”, but the present requirement calls for “Verify the active database and schema context used for unqualified object references”: Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions.
B:Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans. That explains the role of “Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile”, but the present requirement calls for “Verify the active database and schema context used for unqualified object references”: Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions.
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 “Verify the active database and schema context used for unqualified object references”: Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions.
Question 750
During a pilot, engineers pursued an unrelated workaround: Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships. The required outcome remained unsatisfied: A security policy mandates that user permissions never depend on an undocumented PUBLIC role grant for sensitive tables. Which correction should the team prioritize?
- Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships.
- 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.
- Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
Explanation
Correct Answer
C:Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access. The corrective step addresses the missing requirement: A security policy mandates that user permissions never depend on an undocumented PUBLIC role grant for sensitive tables. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. That explains the role of “Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships”, but the present requirement calls for “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
B:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition”, but the present requirement calls for “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
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 “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.