Snowflake SnowPro Core COF-C03 Practice Test 34
Question 330
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A retailer's nightly ELT job saturates compute while an unrelated dashboard must keep predictable query latency; both workloads read the same sales tables. 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?
- Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
- Move the dashboard to a new schema but leave both workloads on one already saturated warehouse.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
Explanation
Correct Answer
B:The supportable direction is: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. The discriminating technical reason is: Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse.
Incorrect Answers
A:That is a mistake for a different warehouse scale-up for complex query task, where A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. Under production migration readiness conditions, Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
C:Under production migration readiness conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
D:That is a mistake for a different durable database storage separation task, where An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It does not directly defeat the present independent compute for bi and elt requirement, whose proper treatment is: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage.
Question 331
[Partner onboarding review] A reviewer recommends: Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort. The requirement remains: A privacy reviewer checks a collaboration rollout before new partner access is granted. A production permanent table was dropped within its configured retention period, and an operator needs a self-service recovery plan rather than a support escalation. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
Explanation
Correct Answer
C:In this partner onboarding review context, Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store. The recommendation is linked to observable evidence for this exact case: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the partner onboarding review conditions, Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster. That explanation applies to a different multi-cluster scale out versus scale up problem: Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. It does not justify the specific time travel versus fail-safe recoverability action or its validation path: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
B:Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
D:For the partner onboarding review conditions, Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. That explanation applies to a different time travel historical query problem: An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. It does not justify the specific time travel versus fail-safe recoverability action or its validation path: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
Question 332
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. 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?
- Set a masking policy on a table column and assume that supplies a second authentication factor at login.
- Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
- Assume a database is automatically replicated to every account merely because all accounts share the same organization.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
Explanation
Correct Answer
D:The supportable direction is: Inspect the active role's grants and cloud-services authorization path instead of resizing compute. This directly undermines cloud services authentication boundary in the specified context.
Incorrect Answers
A:That is a mistake for a different multifactor authentication enrollment task, where A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. Under production migration readiness conditions, Set a masking policy on a table column and assume that supplies a second authentication factor at login.
B:That is a mistake for a different external stage cloud identity integration task, where A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. Under production migration readiness conditions, Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
C:Under production migration readiness conditions, Assume a database is automatically replicated to every account merely because all accounts share the same organization.
Question 333
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.
- Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations.
Explanation
Correct Answer
A:The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown. In this pipeline incident investigation setting, the intended validation is: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials.
Incorrect Answers
B: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 spark connector distributed read need.
C:That action is relevant when A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. It is not the primary action for the stated spark connector distributed read need.
D:That action is relevant when A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. It is not the primary action for the stated spark connector distributed read need.
Question 334
[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 specific design mistake would most directly defeat the intended result?
- Set a masking policy on a table column and assume that supplies a second authentication factor at login.
- Assume labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
- Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
Explanation
Correct Answer
B:The discriminating technical reason is: Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping. The supportable direction is: Run supported Snowflake data-classification capabilities and review resulting tags or classification metadata before policy assignment.
Incorrect Answers
A:That is a mistake for a different multifactor authentication enrollment task, where A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. Under security control assessment conditions, Set a masking policy on a table column and assume that supplies a second authentication factor at login.
C:That is a mistake for a different row access policy filtering task, where Regional managers share a table but must see only the geographic rows permitted by their assigned region. Under security control assessment conditions, Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
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. Under security control assessment conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
Question 335
[Query performance review] The team proposes: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity. Its actual requirement is: A performance engineer is benchmarking representative queries before accepting changes. A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
- A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
Explanation
Correct Answer
C:Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. This is an outcome test of the specified query queueing load analysis action under the query performance review conditions. A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
Incorrect Answers
A:In this query performance review context, Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable. This is an outcome for a different requirement: During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It cannot by itself validate the proposed query queueing load analysis action; the appropriate test is: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
B:A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed query queueing load analysis action; the appropriate test is: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
D:In this query performance review 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 queueing load analysis action; the appropriate test is: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
Question 336
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. 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 managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
Explanation
Correct Answer
D:Ownership is a distinct powerful privilege; transferring it can affect existing grants and operational control. In this security control assessment setting, the intended validation is: SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
Incorrect Answers
A:That action is relevant when A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. It is not the primary action for the stated ownership transfer safety need.
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. It is not the primary action for the stated ownership transfer safety need.
C:That action is relevant when A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It is not the primary action for the stated ownership transfer safety need.
Question 337
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files.
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
- Run COPY INTO with an appropriate VALIDATION_MODE or targeted preflight to inspect errors before committing the production load.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
Explanation
Correct Answer
A:Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. In this pipeline incident investigation setting, the intended validation is: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
Incorrect Answers
B:That action is relevant when One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
C:That action is relevant when A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. It is not the primary action for the stated load idempotence and history need.
D:That action is relevant when A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
Question 338
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions.
- Create a stream and expect it to wake up hourly and execute the cleanup procedure without a task or consumer.
- Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
Explanation
Correct Answer
B:The discriminating technical reason is: Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently. The supportable direction is: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
Incorrect Answers
A:That is a mistake for a different named internal stage for file reuse task, where A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. Under production cutover rehearsal conditions, Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions.
C:It does not directly defeat the present task scheduled orchestration requirement, whose proper treatment is: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
D:That is a mistake for a different stream cdc consumption task, where An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. Under production cutover rehearsal conditions, Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
Question 339
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Explanation
Correct Answer
C:OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance. In this identity and governance change request setting, the intended validation is: The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
Incorrect Answers
A:That action is relevant when A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It is not the primary action for the stated oauth delegated client access need.
B:That action is relevant when Regional managers share a table but must see only the geographic rows permitted by their assigned region. OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
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. It is not the primary action for the stated oauth delegated client access need.
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.