SnowPro Core COF-C03 Practice Test 74
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.
Question 731
During a pilot, engineers pursued an unrelated workaround: Define the correct PARQUET file format and compatible target column mapping. The required outcome remained unsatisfied: A staged data file contains a header row and the table receives that header as ordinary data. Which correction should the team prioritize?
- Set the correct CSV header-handling option in the file format.
- Choose an appropriate COPY INTO ON_ERROR setting and inspect load results.
- Define the correct PARQUET file format and compatible target column mapping.
- Tune staged file sizing and compression based on Snowflake loading best practices.
Explanation
Correct Answer
A:The loader needs explicit format rules to distinguish metadata rows from data records. The corrective step addresses the missing requirement: A staged data file contains a header row and the table receives that header as ordinary data. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B: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 “Set the correct CSV header-handling option in the file format”: The loader needs explicit format rules to distinguish metadata rows from data records.
C:Parquet carries structured column data and should not be parsed as plain delimited text. That explains the role of “Define the correct PARQUET file format and compatible target column mapping”, but the present requirement calls for “Set the correct CSV header-handling option in the file format”: The loader needs explicit format rules to distinguish metadata rows from data records.
D:File granularity and format affect parallelism and parsing overhead for warehouse-based loads. That explains the role of “Tune staged file sizing and compression based on Snowflake loading best practices”, but the present requirement calls for “Set the correct CSV header-handling option in the file format”: The loader needs explicit format rules to distinguish metadata rows from data records.
Question 732
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 developer assumes raising warehouse size fixes an accidentally explosive many-to-many join. Which correction should the team prioritize?
- 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.
- Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
- Inspect join cardinality, join keys and query plan before simply adding compute.
Explanation
Correct Answer
D:Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size. The corrective step addresses the missing requirement: A developer assumes raising warehouse size fixes an accidentally explosive many-to-many join. 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 “Inspect join cardinality, join keys and query plan before simply adding compute”: Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size.
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 “Inspect join cardinality, join keys and query plan before simply adding compute”: Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size.
C:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. That explains the role of “Investigate local warehouse cache warm-up before attributing the slowdown solely to query text”, but the present requirement calls for “Inspect join cardinality, join keys and query plan before simply adding compute”: Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size.
Question 733
During a pilot, engineers pursued an unrelated workaround: Remove that consumer from the authorized share or revoke the relevant shared object grants. The required outcome remained unsatisfied: A data vendor wants a published dataset discoverable through the Snowflake Marketplace with documented terms. Which correction should the team prioritize?
- Remove that consumer from the authorized share or revoke the relevant shared object grants.
- Use an approved Snowflake Reader Account managed through the provider's sharing workflow.
- Create an approved Snowflake Marketplace listing for the supported data product.
- Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
Explanation
Correct Answer
C:Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share. The corrective step addresses the missing requirement: A data vendor wants a published dataset discoverable through the Snowflake Marketplace with documented terms. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Provider-owned grants control consumer access independently of data persistence. That explains the role of “Remove that consumer from the authorized share or revoke the relevant shared object grants”, but the present requirement calls for “Create an approved Snowflake Marketplace listing for the supported data product”: Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share.
B:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. That explains the role of “Use an approved Snowflake Reader Account managed through the provider's sharing workflow”, but the present requirement calls for “Create an approved Snowflake Marketplace listing for the supported data product”: Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share.
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 “Create an approved Snowflake Marketplace listing for the supported data product”: Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share.
Question 734
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: An auditor asks which Snowflake layer holds compressed columnar micro-partitions after a table is loaded. Which correction should the team prioritize?
- Check the cloud services authentication and network access path before tuning warehouse size.
- Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
- Query the committed Snowflake table from the second warehouse under an authorized role.
- Identify managed database storage as the persistence layer for compressed columnar table data.
Explanation
Correct Answer
D:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. The corrective step addresses the missing requirement: An auditor asks which Snowflake layer holds compressed columnar micro-partitions after a table is loaded. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity. That explains the role of “Check the cloud services authentication and network access path before tuning warehouse size”, but the present requirement calls for “Identify managed database storage as the persistence layer for compressed columnar table data”: Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute.
B: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 “Identify managed database storage as the persistence layer for compressed columnar table data”: Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute.
C: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 managed database storage as the persistence layer for compressed columnar table data”: Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute.
Question 735
During a pilot, engineers pursued an unrelated workaround: Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority. The required outcome remained unsatisfied: A junior administrator should create user accounts but must not assume unrestricted business data ownership. Which correction should the team prioritize?
- Grant USAGE and SELECT through reader roles while limiting MANAGE GRANTS and ownership authority.
- Use user-management privileges or the appropriate system administration role without broad data 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.
Explanation
Correct Answer
B:Managing identities and accessing all customer tables are distinct authorization duties. The corrective step addresses the missing requirement: A junior administrator should create user accounts but must not assume unrestricted business data ownership. 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 “Use user-management privileges or the appropriate system administration role without broad data grants”: Managing identities and accessing all customer tables are distinct authorization duties.
C: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 “Use user-management privileges or the appropriate system administration role without broad data grants”: Managing identities and accessing all customer tables are distinct authorization duties.
D:Federated SSO centralizes login assurance and deprovisioning for interactive employees. That explains the role of “Configure supported federated single sign-on with the organization's identity provider”, but the present requirement calls for “Use user-management privileges or the appropriate system administration role without broad data grants”: Managing identities and accessing all customer tables are distinct authorization duties.
Question 736
During a pilot, engineers pursued an unrelated workaround: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. The required outcome remained unsatisfied: A reporting table needs file ingestion timestamp and original file name for downstream lineage. Which correction should the team prioritize?
- Configure the CSV file format with the correct delimiter and enclosure options.
- Capture supported METADATA$ filename and load timestamp information during staging ingestion.
- Create or use a supported internal Snowflake stage with appropriate file format and grants.
- Use COPY INTO with a carefully tested PATTERN or specific staged prefix.
Explanation
Correct Answer
B:Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers. The corrective step addresses the missing requirement: A reporting table needs file ingestion timestamp and original file name for downstream lineage. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:File-format parsing rules must match real source encoding and quote conventions. That explains the role of “Configure the CSV file format with the correct delimiter and enclosure options”, but the present requirement calls for “Capture supported METADATA$ filename and load timestamp information during staging ingestion”: Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
C: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 “Capture supported METADATA$ filename and load timestamp information during staging ingestion”: Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
D:Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch. That explains the role of “Use COPY INTO with a carefully tested PATTERN or specific staged prefix”, but the present requirement calls for “Capture supported METADATA$ filename and load timestamp information during staging ingestion”: Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers.
Question 737
During a pilot, engineers pursued an unrelated workaround: Inspect Snowflake persisted query result reuse and conditions that invalidate it. The required outcome remained unsatisfied: Several SQL reports use different filter paths on one large table and a single clustering key cannot efficiently serve them all. Which correction should the team prioritize?
- Investigate local warehouse cache warm-up before attributing the slowdown solely to query text.
- Inspect partition pruning and consider appropriate clustering of the filter key for a large table.
- Compare search optimization and targeted materialized views against actual filter patterns.
- Inspect Snowflake persisted query result reuse and conditions that invalidate it.
Explanation
Correct Answer
C:Clustering optimizes data locality for one key expression, while other services can target distinct access paths. The corrective step addresses the missing requirement: Several SQL reports use different filter paths on one large table and a single clustering key cannot efficiently serve them all. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. That explains the role of “Investigate local warehouse cache warm-up before attributing the slowdown solely to query text”, but the present requirement calls for “Compare search optimization and targeted materialized views against actual filter patterns”: Clustering optimizes data locality for one key expression, while other services can target distinct access paths.
B:Poor data locality can force scans of irrelevant partitions even for selective predicates. That explains the role of “Inspect partition pruning and consider appropriate clustering of the filter key for a large table”, but the present requirement calls for “Compare search optimization and targeted materialized views against actual filter patterns”: Clustering optimizes data locality for one key expression, while other services can target distinct access paths.
D:Result caching can return compatible prior query results without reexecuting a full warehouse scan. That explains the role of “Inspect Snowflake persisted query result reuse and conditions that invalidate it”, but the present requirement calls for “Compare search optimization and targeted materialized views against actual filter patterns”: Clustering optimizes data locality for one key expression, while other services can target distinct access paths.
Question 738
During a pilot, engineers pursued an unrelated workaround: Expose a governed secure view through a direct share rather than granting raw base-table access. The required outcome remained unsatisfied: Two partner organizations want to analyze overlapping customer cohorts without freely exchanging individual-level records. Which correction should the team prioritize?
- Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
- Plan supported cross-region sharing or listing and replication arrangements as required.
- Expose a governed secure view through a direct share rather than granting raw base-table access.
- Remove that consumer from the authorized share or revoke the relevant shared object grants.
Explanation
Correct Answer
A:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. The corrective step addresses the missing requirement: Two partner organizations want to analyze overlapping customer cohorts without freely exchanging individual-level records. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly. That explains the role of “Plan supported cross-region sharing or listing and replication arrangements as required”, but the present requirement calls for “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”: Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data.
C: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 “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”: Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data.
D:Provider-owned grants control consumer access independently of data persistence. That explains the role of “Remove that consumer from the authorized share or revoke the relevant shared object grants”, but the present requirement calls for “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”: Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data.
Question 739
During a pilot, engineers pursued an unrelated workaround: Identify managed database storage as the persistence layer for compressed columnar table data. The required outcome remained unsatisfied: A connection succeeds but users cannot query protected objects because their privileges are insufficient. Which correction should the team prioritize?
- 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.
- Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
- Identify managed database storage as the persistence layer for compressed columnar table data.
Explanation
Correct Answer
B:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. The corrective step addresses the missing requirement: A connection succeeds but users cannot query protected objects because their privileges are insufficient. 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 “Investigate authentication and authorization in the cloud services control path and the selected role”: Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements.
C: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 “Investigate authentication and authorization in the cloud services control path and the selected role”: Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements.
D:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. That explains the role of “Identify managed database storage as the persistence layer for compressed columnar table data”, but the present requirement calls for “Investigate authentication and authorization in the cloud services control path and the selected role”: Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements.
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.