Snowflake SnowPro Core COF-C03 Practice Test 106
Question 1050
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
- Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files.
- Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
Explanation
Correct Answer
B:A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query. In this optimization regression test setting, the intended validation is: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
Incorrect Answers
A:It is not the primary action for the stated query queueing load analysis need.
C:That action is relevant when A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
D:That action is relevant when During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It is not the primary action for the stated query queueing load analysis need.
Question 1051
[Security control assessment] A reviewer recommends: Enforce and verify appropriate Snowflake MFA or federated IdP MFA controls according to the active policy. The requirement remains: A quarterly access-control audit requires an evidence-backed answer. A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Key-pair authentication supports service access while avoiding hard-coded interactive user passwords, subject to secure private-key handling.
- Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
- MFA protects interactive sign-in beyond knowledge of a single password; it is separate from table permissions.
- Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows.
Explanation
Correct Answer
C:In this security control assessment context, MFA protects interactive sign-in beyond knowledge of a single password; it is separate from table permissions. The recommendation is linked to observable evidence for this exact case: Identity logs and a controlled sign-in test show the required second factor before an authorized session starts. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns workload identity key-pair authentication, not the requirement in this case. It does not justify the specific multifactor authentication enrollment action or its validation path: Identity logs and a controlled sign-in test show the required second factor before an authorized session starts.
B:It does not justify the specific multifactor authentication enrollment action or its validation path: Identity logs and a controlled sign-in test show the required second factor before an authorized session starts.
D:For the security control assessment conditions, Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows. That explanation applies to a different row access policy filtering problem: Regional managers share a table but must see only the geographic rows permitted by their assigned region. It does not justify the specific multifactor authentication enrollment action or its validation path: Identity logs and a controlled sign-in test show the required second factor before an authorized session starts.
Question 1052
[Production migration readiness] A reviewer recommends: Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows.
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model.
Explanation
Correct Answer
D:In this production migration readiness context, Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model. The recommendation is linked to observable evidence for this exact case: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the production migration readiness conditions, Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows. That explanation applies to a different micro-partition pruning metadata problem: A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
B:That option concerns account and schema object hierarchy, not the requirement in this case. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
C:For the production migration readiness conditions, Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. That explanation applies to a different transient staging table lifecycle problem: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It does not justify the specific iceberg interoperability decision action or its validation path: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
Question 1053
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Configure appropriate future grants for the required schema scope while preserving narrowly defined access roles.
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Explanation
Correct Answer
A:Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition. In this identity and governance change request setting, the intended validation is: A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
Incorrect Answers
B:That action is relevant when A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
C:That action is relevant when A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It is not the primary action for the stated future grants in new schema need.
D:That action is relevant when A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition.
Question 1054
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
Explanation
Correct Answer
B:The supportable direction is: Keep data in managed database storage and resume compute only when processing is needed. The discriminating technical reason is: The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Incorrect Answers
A:Under post-rollout service review conditions, Change the result cache setting and assume it will switch the current schema for both sessions.
C:It does not directly defeat the present durable database storage separation requirement, whose proper treatment is: Keep data in managed database storage and resume compute only when processing is needed.
D:That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not directly defeat the present durable database storage separation requirement, whose proper treatment is: Keep data in managed database storage and resume compute only when processing is needed.
Question 1055
[Ingestion design acceptance] The team proposes: Run COPY INTO with an appropriate VALIDATION_MODE or targeted preflight to inspect errors before committing the production load. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- The exported object files have the expected schema, row counts, and authorized destination path.
- After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
- Validation output identifies the same malformed records that can be corrected before the final committed load.
- The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
Explanation
Correct Answer
C:Validation output identifies the same malformed records that can be corrected before the final committed load. This is an outcome test of the specified copy into validation preflight action under the ingestion design acceptance conditions. Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
Incorrect Answers
A:The exported object files have the expected schema, row counts, and authorized destination path. This is an outcome for a different requirement: A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. It cannot by itself validate the proposed copy into validation preflight action; the appropriate test is: Validation output identifies the same malformed records that can be corrected before the final committed load.
B:In this ingestion design acceptance context, After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions. This is an outcome for a different requirement: A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. It cannot by itself validate the proposed copy into validation preflight action; the appropriate test is: Validation output identifies the same malformed records that can be corrected before the final committed load.
D:The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows. This is an outcome for a different requirement: A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. It cannot by itself validate the proposed copy into validation preflight action; the appropriate test is: Validation output identifies the same malformed records that can be corrected before the final committed load.
Question 1056
[Production cutover rehearsal] The team proposes: Enable or refresh an appropriate directory table on a supported stage and query its file metadata. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change.
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- Load history and target counts confirm expected files were not ingested twice after simulated network retry.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Explanation
Correct Answer
D:Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh. This is an outcome test of the specified directory table unstructured metadata action under the production cutover rehearsal conditions. Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves.
Incorrect Answers
A:Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change. This is an outcome for a different requirement: A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
B:In this production cutover rehearsal context, A staged file is visible through the table-stage reference and a controlled COPY loads the intended table. This is an outcome for a different requirement: An analyst must stage a small support file used only to load one existing target table, with no need for a shared named-stage contract. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
C:In this production cutover rehearsal context, Load history and target counts confirm expected files were not ingested twice after simulated network retry. This is an outcome for a different requirement: A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It cannot by itself validate the proposed directory table unstructured metadata action; the appropriate test is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Question 1057
[Post-rollout service review] A reviewer recommends: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
Explanation
Correct Answer
A:In this post-rollout service review context, Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. The recommendation is linked to observable evidence for this exact case: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns durable database storage separation, not the requirement in this case. It does not justify the specific transient staging table lifecycle action or its validation path: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
C:For the post-rollout service review conditions, External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table. That explanation applies to a different external table over data lake problem: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not justify the specific transient staging table lifecycle action or its validation path: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
D:That option concerns permanent table recovery choice, not the requirement in this case. It does not justify the specific transient staging table lifecycle action or its validation path: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
Question 1058
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
- Run supported Snowflake data-classification capabilities and review resulting tags or classification metadata before policy assignment.
- Configure the available private connectivity option for the eligible edition and cloud, then validate DNS and routing.
- Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges.
Explanation
Correct Answer
B:Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping. In this security control assessment setting, the intended validation is: Classification reports flag representative PII columns, and subsequent policy checks demonstrate intended protection.
Incorrect Answers
A:It is not the primary action for the stated automated sensitive-data classification need.
C:That action is relevant when A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
D:That action is relevant when An organization must restrict logins to approved corporate egress ranges even when credentials are correct. Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
Question 1059
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
Explanation
Correct Answer
C:Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading. In this security control assessment setting, the intended validation is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
Incorrect Answers
A:That action is relevant when A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
B:That action is relevant when A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
D:That action is relevant when A user has an approved reporting role and a separate engineering role but a worksheet unexpectedly lacks SELECT even though the second role has the grant. Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
Question 1060
[Identity and governance change request] A reviewer recommends: Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges. The requirement remains: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. An organization must restrict logins to approved corporate egress ranges even when credentials are correct. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
- Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
- Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
- Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
Explanation
Correct Answer
D:In this identity and governance change request context, Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy. The recommendation is linked to observable evidence for this exact case: An approved corporate source can connect while a test connection from an excluded source is rejected. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the identity and governance change request conditions, Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value. That explanation applies to a different dynamic data masking policy problem: A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It does not justify the specific network policy address restrictions action or its validation path: An approved corporate source can connect while a test connection from an excluded source is rejected.
B:Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping.
C:That option concerns inherited functional role grants, not the requirement in this case. It does not justify the specific network policy address restrictions action or its validation path: An approved corporate source can connect while a test connection from an excluded source is rejected.