Snowflake SnowPro Core COF-C03 Practice Test 119
Question 1180
[Query performance review] The team proposes: Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size. Its actual requirement is: A performance engineer is benchmarking representative queries before accepting changes. Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
Explanation
Correct Answer
D:The cluster count rises during bursts and query queue duration falls in matched concurrency tests. This is an outcome test of the specified multi-cluster scale out versus scale up action under the query performance review conditions. Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
Incorrect Answers
A:In this query performance review context, Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. This is an outcome for a different requirement: A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. It cannot by itself validate the proposed multi-cluster scale out versus scale up action; the appropriate test is: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
B:In this query performance review context, Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. This is an outcome for a different requirement: A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It cannot by itself validate the proposed multi-cluster scale out versus scale up action; the appropriate test is: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
C:In this query performance review context, The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed. This is an outcome for a different requirement: An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It cannot by itself validate the proposed multi-cluster scale out versus scale up action; the appropriate test is: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
Question 1181
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. 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?
- Copy an engineer's browser cookies into CI and expect them to behave like a supported noninteractive Snowflake CLI identity.
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
Explanation
Correct Answer
A:The supportable direction is: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials. Copy an engineer's browser cookies into CI and expect them to behave like a supported noninteractive Snowflake CLI identity.
Incorrect Answers
B:Under production migration readiness conditions, Create new warehouses until a table appears, without specifying or checking its database and schema context. 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. 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.
C:That is a mistake for a different cloud services authentication boundary task, where An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. Under production migration readiness conditions, Increase warehouse size repeatedly without checking role grants or the denied object privilege.
D:Under production migration readiness conditions, Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference. That is a mistake for a different time travel historical query task, where 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 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 1182
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. 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?
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- 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.
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Explanation
Correct Answer
B:This directly undermines custom roles versus system roles in the specified context.
Incorrect Answers
A: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.
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. 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.
D:That is a mistake for a different future grants in new schema task, where Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. Under security control assessment conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Question 1183
[Query performance review] A performance engineer is benchmarking representative queries before accepting changes. 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 reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
- Open the query's profile and compare execution operators, partitions scanned, bytes processed, and spill indicators before tuning.
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
Explanation
Correct Answer
C:Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause. In this query performance review setting, the intended validation is: A before-and-after profile identifies the operator that improved and shows lower elapsed execution time on comparable data.
Incorrect Answers
A:That action is relevant when A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
B:It is not the primary action for the stated query profile bottleneck localization need.
D:That action is relevant when Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. It is not the primary action for the stated query profile bottleneck localization need.
Question 1184
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. 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 conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Assume switching on the service guarantees every simple SELECT is accelerated without checking eligibility.
- Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
- Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
- Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
Explanation
Correct Answer
D:The discriminating technical reason is: Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause. Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
Incorrect Answers
A:Under optimization regression test conditions, Assume switching on the service guarantees every simple SELECT is accelerated without checking eligibility.
B:Under optimization regression test conditions, Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
C:Under optimization regression test conditions, Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
Question 1185
[Ingestion design acceptance] The team proposes: Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
Explanation
Correct Answer
A:End-to-end event timestamps show data arriving within the required streaming latency under peak event load. This is an outcome test of the specified snowpipe streaming low latency action under the ingestion design acceptance conditions. Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
Incorrect Answers
B:In this ingestion design acceptance context, A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome for a different requirement: One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. It cannot by itself validate the proposed snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
C:In this ingestion design acceptance 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 snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
D:Historical usage matches billed and recorded account activity after the documented latency window has elapsed. This is an outcome for a different requirement: Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. It cannot by itself validate the proposed snowpipe streaming low latency action; the appropriate test is: End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
Question 1186
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. 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?
- Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
- Pass an arbitrary object-stage URL as a database hostname and expect it to authenticate like the Snowflake SQL endpoint.
- Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
- Assume ordinary SQL grants automatically create a private cloud endpoint or satisfy infrastructure-level isolation requirements.
Explanation
Correct Answer
B:The supportable direction is: Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role. Pass an arbitrary object-stage URL as a database hostname and expect it to authenticate like the Snowflake SQL endpoint.
Incorrect Answers
A:It does not directly defeat the present jdbc or odbc application connection requirement, whose proper treatment is: Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role.
C:That is a mistake for a different streamlit app inside snowflake task, where An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. Under pipeline incident investigation conditions, Assume deploying the app bypasses database grants and makes every protected table readable to all anonymous visitors.
D:That is a mistake for a different business critical private connectivity task, where A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. Under pipeline incident investigation conditions, Assume ordinary SQL grants automatically create a private cloud endpoint or satisfy infrastructure-level isolation requirements.
Question 1187
[Query performance review] The team proposes: Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches. Its actual requirement is: 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 observation most directly validates success?
- Two eligible unchanged executions show a reuse indicator, while changed data causes fresh evaluation under documented conditions.
- A regression test with tied timestamps always chooses the same event according to the documented tie-breaker.
- A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
- A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured.
Explanation
Correct Answer
C:A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys. This is an outcome test of the specified merge keyed upsert action under the query performance review conditions. MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
Incorrect Answers
A:Two eligible unchanged executions show a reuse indicator, while changed data causes fresh evaluation under documented conditions. This is an outcome for a different requirement: A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. It cannot by itself validate the proposed merge keyed upsert action; the appropriate test is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
B:In this query performance review context, A regression test with tied timestamps always chooses the same event according to the documented tie-breaker. This is an outcome for a different requirement: A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. It cannot by itself validate the proposed merge keyed upsert action; the appropriate test is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
D:A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured. This is an outcome for a different requirement: An unattended ingestion service needs noninteractive authentication without embedding an employee's reusable password into scripts. It cannot by itself validate the proposed merge keyed upsert action; the appropriate test is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
Question 1188
[Security control assessment] The team proposes: Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user. Its actual requirement is: 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 observation most directly validates success?
- SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
- A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
- The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
Explanation
Correct Answer
D:SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied. This is an outcome test of the specified least-privilege read role action under the security control assessment conditions. Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
Incorrect Answers
A:In this security control assessment context, SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations. This is an outcome for a different requirement: A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It cannot by itself validate the proposed least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
B:In this security control assessment context, A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
C:The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges. This is an outcome for a different requirement: A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It cannot by itself validate the proposed least-privilege read role action; the appropriate test is: SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
Question 1189
[Production compliance review] The team proposes: Use an appropriately supported programmatic identity with managed key-pair authentication and rotation controls. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. An unattended ingestion service needs noninteractive authentication without embedding an employee's reusable password into scripts. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured.
- Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
- The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
- A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
Explanation
Correct Answer
A:A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured. This is an outcome test of the specified workload identity key-pair authentication action under the production compliance review conditions. Key-pair authentication supports service access while avoiding hard-coded interactive user passwords, subject to secure private-key handling.
Incorrect Answers
B:In this production compliance review context, Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities. This is an outcome for a different requirement: A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. It cannot by itself validate the proposed workload identity key-pair authentication action; the appropriate test is: A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured.
C:In this production compliance review context, The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged. This is an outcome for a different requirement: An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. It cannot by itself validate the proposed workload identity key-pair authentication action; the appropriate test is: A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured.
D:In this production compliance review context, A test user signs in through the approved identity provider and receives only the expected Snowflake role access. This is an outcome for a different requirement: An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. It cannot by itself validate the proposed workload identity key-pair authentication action; the appropriate test is: A pipeline authenticates with its approved public-key registration and fails when the key is revoked or misconfigured.
Question 1190
[Architecture planning workshop] A reviewer recommends: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. The requirement remains: An internal platform architecture group is assessing the initial design. 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 reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse.
- Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage.
- Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
Explanation
Correct Answer
B:In this architecture planning workshop context, Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse. The recommendation is linked to observable evidence for this exact case: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the architecture planning workshop conditions, Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog. That explanation applies to a different account and schema object hierarchy problem: A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It does not justify the specific independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
C:For the architecture planning workshop conditions, Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage. That explanation applies to a different warehouse local data cache problem: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It does not justify the specific independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
D:For the architecture planning workshop conditions, Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count. That explanation applies to a different multi-cluster concurrency scaling problem: During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. It does not justify the specific independent compute for bi and elt action or its validation path: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.