Snowflake SnowPro Core COF-C03 Practice Test 27
Question 260
[Collaboration operating audit] A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Create and govern a suitable Snowflake Marketplace listing with the intended visibility, terms, and fulfillment model.
- Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
- Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
- Choose a cross-region or cross-cloud listing and fulfillment configuration supported by their accounts and Snowflake edition.
Explanation
Correct Answer
D:Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access. In this collaboration operating audit setting, the intended validation is: The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
Incorrect Answers
A:That action is relevant when A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
B: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. It is not the primary action for the stated cross-region data listing fulfillment need.
C:That action is relevant when Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. It is not the primary action for the stated cross-region data listing fulfillment need.
Question 261
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. 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?
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
Explanation
Correct Answer
A:The discriminating technical reason is: Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted. The supportable direction is: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, CURRENT_ROLE, and session context before resolving or qualifying the table.
Incorrect Answers
B: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 architecture planning workshop conditions, Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
C: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.
D:Under architecture planning workshop conditions, Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
Question 262
[Ingestion design acceptance] The team proposes: Use the table's built-in stage where suitable and load into the target using supported commands. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. 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. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- 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.
- The exported object files have the expected schema, row counts, and authorized destination path.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Explanation
Correct Answer
B:A staged file is visible through the table-stage reference and a controlled COPY loads the intended table. This is an outcome test of the specified table stage file landing action under the ingestion design acceptance conditions. A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
Incorrect Answers
A: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 table stage file landing action; the appropriate test is: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
C:In this ingestion design acceptance context, 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 table stage file landing action; the appropriate test is: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
D:Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh. This is an outcome for a different requirement: A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It cannot by itself validate the proposed table stage file landing action; the appropriate test is: A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
Question 263
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Manually edit Snowflake-managed micro-partition files in object storage to force the desired predicate order.
- Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
- Enable clustering on every tiny scratch table because all tables benefit equally without additional compute charges.
- Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
Explanation
Correct Answer
C:The discriminating technical reason is: Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table. This directly undermines automatic clustering cost tradeoff in the specified context.
Incorrect Answers
A:That is a mistake for a different micro-partition pruning metadata task, where A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. Under optimization regression test conditions, Manually edit Snowflake-managed micro-partition files in object storage to force the desired predicate order.
B:That is a mistake for a different warehouse sizing performance experiment task, where A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. Under optimization regression test conditions, Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
D:Under optimization regression test conditions, Treat the suspended warehouse's local cache as a permanent table copy that must remain available after shutdown.
Question 264
[Ingestion design acceptance] The team proposes: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
- LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
- A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
- TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
Explanation
Correct Answer
D:TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. This is an outcome test of the specified task scheduled orchestration action under the ingestion design acceptance conditions. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
Incorrect Answers
A:In this ingestion design acceptance context, SELECT using the function gives the same result as the underlying expression for a boundary-value test set. This is an outcome for a different requirement: Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
B:In this ingestion design acceptance context, LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows. This is an outcome for a different requirement: A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
C:A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY. This is an outcome for a different requirement: Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
Question 265
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. 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 access to a nonexistent consumer account identifier and assume Snowflake creates a working user interface automatically.
- Assume a database is automatically replicated to every account merely because all accounts share the same organization.
- Email unencrypted copies of all source tables nightly and claim that this is the only supported Snowflake collaboration model.
- Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
Explanation
Correct Answer
A:The discriminating technical reason is: Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls. This directly undermines reader account for external consumer in the specified context.
Incorrect Answers
B:Under partner onboarding review conditions, Assume a database is automatically replicated to every account merely because all accounts share the same organization. That is a mistake for a different cross-region snowflake account planning task, where 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.
C:That is a mistake for a different direct share cross-account access task, where A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. Under partner onboarding review conditions, Email unencrypted copies of all source tables nightly and claim that this is the only supported Snowflake collaboration model.
D:That is a mistake for a different external function api integration task, where A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. Under partner onboarding review conditions, Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
Question 266
[Peak traffic performance incident] The team proposes: Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
- Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
- Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible.
Explanation
Correct Answer
B:Query Acceleration Service can offload eligible query components to shared compute; it does not replace base warehouse execution for every operation. This is an outcome test of the specified query acceleration service suitability action under the peak traffic performance incident conditions.
Incorrect Answers
A:In this peak traffic performance incident context, The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome for a different requirement: A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. It cannot by itself validate the proposed query acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
C: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 acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
D:In this peak traffic performance incident 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 query acceleration service suitability action; the appropriate test is: Query insights and billing show qualifying accelerated query work with net latency benefit at an acceptable credit cost.
Question 267
[Query performance review] A reviewer recommends: Specify a deterministic secondary ordering key in ROW_NUMBER or another suitable window ranking expression. The requirement remains: A performance engineer is benchmarking representative queries before accepting changes. A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries.
- A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
- Window ordering must resolve ties to make latest-record selection reproducible across executions.
- Result reuse depends on strict eligibility and unchanged relevant data; it is distinct from local warehouse data-cache reuse.
Explanation
Correct Answer
C:In this query performance review context, Window ordering must resolve ties to make latest-record selection reproducible across executions. The recommendation is linked to observable evidence for this exact case: A regression test with tied timestamps always chooses the same event according to the documented tie-breaker. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns merge keyed upsert, not the requirement in this case. It does not justify the specific window-function deterministic ranking action or its validation path: A regression test with tied timestamps always chooses the same event according to the documented tie-breaker.
B:That option concerns sql udf reusable expression, not the requirement in this case. It does not justify the specific window-function deterministic ranking action or its validation path: A regression test with tied timestamps always chooses the same event according to the documented tie-breaker.
D:That option concerns persisted result reuse conditions, not the requirement in this case. It does not justify the specific window-function deterministic ranking action or its validation path: A regression test with tied timestamps always chooses the same event according to the documented tie-breaker.
Question 268
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. 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. 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?
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
Explanation
Correct Answer
D:The discriminating technical reason is: Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable. This directly undermines inherited functional role grants in the specified context.
Incorrect Answers
A:That is a mistake for a different custom roles versus system roles task, where A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. Under identity and governance change request conditions, Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
B: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 identity and governance change request conditions, Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
C:Under identity and governance change request conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Question 269
[Optimization regression test] The team proposes: Assess clustering depth and query frequency before assigning a clustering key with ongoing maintenance cost. Its actual requirement is: A team is validating a targeted tuning plan against documented workloads and costs. A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
Explanation
Correct Answer
A:Clustering information and workload-wide latency improve enough to justify the observed maintenance credits. This is an outcome test of the specified automatic clustering cost tradeoff action under the optimization regression test conditions. Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table.
Incorrect Answers
B:In this optimization regression test 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 automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
C: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 automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
D:In this optimization regression test context, Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. This is an outcome for a different requirement: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
Question 270
[Peak traffic performance incident] The team proposes: Assess clustering depth and query frequency before assigning a clustering key with ongoing maintenance cost. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Explanation
Correct Answer
B:Clustering information and workload-wide latency improve enough to justify the observed maintenance credits. This is an outcome test of the specified automatic clustering cost tradeoff action under the peak traffic performance incident conditions. Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table.
Incorrect Answers
A:In this peak traffic performance incident 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 automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
C:In this peak traffic performance incident context, Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. This is an outcome for a different requirement: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
D:The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome for a different requirement: A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.