Snowflake SnowPro Core COF-C03 Practice Test 35
Question 340
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Account for local warehouse data-cache loss across suspension, and test steady-state cost/performance without assuming persistence.
- Attach a suitable resource monitor to supported user-managed warehouse consumption and configure quota triggers.
- Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
- Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence.
Explanation
Correct Answer
D:Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums. In this production migration readiness setting, the intended validation is: Warehouse events show suspension during idle periods and subsequent query-triggered resume without losing stored data.
Incorrect Answers
A:That action is relevant when A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
B:That action is relevant when A sandbox warehouse is used for unpredictable experiments and a manager needs credit alerts and a suspension threshold for that warehouse. It is not the primary action for the stated warehouse auto-suspend economics need.
C: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. Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
Question 341
[Pipeline incident investigation] A reviewer recommends: Select a strict COPY INTO error policy such as ABORT_STATEMENT and reconcile source counts before releasing downstream results. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A financial batch is required to fail atomically when any unexpected malformed source record appears rather than silently omit data. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- COPY error behavior determines whether load execution aborts or continues past bad rows; strict policy fits completeness-sensitive feeds.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
- Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
Explanation
Correct Answer
A:In this pipeline incident investigation context, COPY error behavior determines whether load execution aborts or continues past bad rows; strict policy fits completeness-sensitive feeds. The recommendation is linked to observable evidence for this exact case: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:For the pipeline incident investigation conditions, Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. That explanation applies to a different load idempotence and history problem: A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It does not justify the specific copy into error-handling choice action or its validation path: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
C:For the pipeline incident investigation conditions, Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption. That explanation applies to a different zero-copy clone lifecycle in collaboration problem: A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. It does not justify the specific copy into error-handling choice action or its validation path: The malformed test file causes the controlled load to abort without accepting an incomplete batch of financial rows.
D:Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
Question 342
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
- Grant every user elevated SQL privileges and call it a replacement for identity federation.
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
Explanation
Correct Answer
B:The discriminating technical reason is: System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority. This directly undermines custom roles versus system roles in the specified context.
Incorrect Answers
A:Under identity and governance change request conditions, Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected. That is a mistake for a different inherited functional role grants task, where 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.
C:That is a mistake for a different federated single sign-on task, where An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. Under identity and governance change request conditions, Grant every user elevated SQL privileges and call it a replacement for identity federation.
D:Under identity and governance change request conditions, Resize the warehouse without checking session role activation because compute can substitute for a dormant access role. It does not directly defeat the present custom roles versus system roles requirement, whose proper treatment is: Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
Question 343
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Use a suitable supported Snowflake Cortex AI text function or model API and govern its input and output.
- Configure an authorized storage integration and external stage with the required cloud trust and path restrictions.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
- Evaluate and provision a Snowflake reader account with authorized shares and documented provider billing responsibilities.
Explanation
Correct Answer
C:API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement. In this ingestion design acceptance setting, the intended validation is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
Incorrect Answers
A:That action is relevant when A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. It is not the primary action for the stated external function api integration need.
B:That action is relevant when A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. It is not the primary action for the stated external function api integration need.
D:That action is relevant when A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It is not the primary action for the stated external function api integration need.
Question 344
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
- Change the result cache setting and assume it will switch the current schema for both sessions.
Explanation
Correct Answer
D:The discriminating technical reason is: Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted. Change the result cache setting and assume it will switch the current schema for both sessions.
Incorrect Answers
A:That is a mistake for a different least-privilege read role task, where A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. Under production migration readiness conditions, Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
B:Under production migration readiness conditions, Resize the warehouse without checking session role activation because compute can substitute for a dormant access role. It does not directly defeat the present session database and role context requirement, whose proper treatment is: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, CURRENT_ROLE, and session context before resolving or qualifying the table.
C:That is a mistake for a different snowsight analyst interface task, where An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. Under production migration readiness conditions, Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
Question 345
[Peak traffic performance incident] The team proposes: Open the query's profile and compare execution operators, partitions scanned, bytes processed, and spill indicators before tuning. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. A 70-second analytics query has become slow after a schema change, and the team wants to find whether scanning, joining, or spilling dominates its runtime. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
- Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
- Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
Explanation
Correct Answer
A:A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data. This is an outcome test of the specified query profile bottleneck localization action under the peak traffic performance incident conditions. Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause.
Incorrect Answers
B:In this peak traffic performance incident context, Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions. This is an outcome for a different requirement: A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It cannot by itself validate the proposed query profile bottleneck localization action; the appropriate test is: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
C:In this peak traffic performance incident context, Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost. This is an outcome for a different requirement: Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. It cannot by itself validate the proposed query profile bottleneck localization action; the appropriate test is: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
D:In this peak traffic performance incident context, Remote spill bytes and elapsed time decrease on a representative workload after the targeted change. This is an outcome for a different requirement: A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. It cannot by itself validate the proposed query profile bottleneck localization action; the appropriate test is: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
Question 346
[Production compliance review] A reviewer recommends: Enforce and verify appropriate Snowflake MFA or federated IdP MFA controls according to the active policy. The requirement remains: A compliance reviewer is checking which safeguard actually enforces the stated boundary. A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
- 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.
- Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy.
Explanation
Correct Answer
B:In this production compliance review 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:Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
C:That option concerns row access policy filtering, 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.
D:That option concerns network policy address restrictions, 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.
Question 347
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Assume a database is automatically replicated to every account merely because all accounts share the same organization.
- Copy an engineer's browser cookies into CI and expect them to behave like a supported noninteractive Snowflake CLI identity.
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
Explanation
Correct Answer
C:The supportable direction is: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials. The discriminating technical reason is: Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
Incorrect Answers
A:That is a mistake for a different account and schema object hierarchy task, where A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. Under post-rollout service review conditions, Create new warehouses until a table appears, without specifying or checking its database and schema context.
B:Under post-rollout service review conditions, Assume a database is automatically replicated to every account merely because all accounts share the same organization.
D:It does not directly defeat the present snowflake cli reproducible developer work requirement, whose proper treatment is: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials.
Question 348
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. 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 explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
- Inspect the active role's grants and cloud-services authorization path instead of resizing compute.
- Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
- Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials.
Explanation
Correct Answer
D:Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles. In this architecture planning workshop setting, the intended validation is: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
Incorrect Answers
A:That action is relevant when A company operates accounts on two clouds and wants to access a dataset from the second account without assuming storage instantly appears in both regions. Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
B:It is not the primary action for the stated snowflake cli reproducible developer work need. Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
C:That action is relevant when A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It is not the primary action for the stated snowflake cli reproducible developer work need.
Question 349
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
- Assume labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
- Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
Explanation
Correct Answer
A:The discriminating technical reason is: Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value. The supportable direction is: Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model.
Incorrect Answers
B:That is a mistake for a different dynamic table downstream freshness task, where A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. Under production compliance review conditions, Call a standard read-only view a continuously materialized table with guaranteed five-second refresh history.
C:Under production compliance review conditions, Assume labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
D:That is a mistake for a different network policy address restrictions task, where An organization must restrict logins to approved corporate egress ranges even when credentials are correct. Under production compliance review conditions, Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
Question 350
[Query performance review] A performance engineer is benchmarking representative queries before accepting changes. A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Specify a deterministic secondary ordering key in ROW_NUMBER or another suitable window ranking expression.
- Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
- Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow.
Explanation
Correct Answer
B:MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries. In this query performance review setting, the intended validation is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
Incorrect Answers
A:That action is relevant when A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
C:That action is relevant when A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. It is not the primary action for the stated merge keyed upsert need.
D:That action is relevant when An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.