Snowflake SnowPro Core COF-C03 Practice Test 108
Question 1070
[Query performance review] A performance engineer is benchmarking representative queries before accepting changes. A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Inspect pruning and the overlap of the filter column's values, then tune a supported clustering strategy if warranted.
- Load the payload into a VARIANT column and use supported path extraction and casts for downstream typed calculations.
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
- Use Snowflake PIVOT on the supported aggregation and quarter categories or an equivalent conditional aggregate.
Explanation
Correct Answer
B:VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data. In this query performance review setting, the intended validation is: SELECT of nested attributes returns expected scalar values and missing optional fields are handled according to the SQL logic.
Incorrect Answers
A:That action is relevant when A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table. VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
C:That action is relevant when Regional managers share a table but must see only the geographic rows permitted by their assigned region. VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
D:That action is relevant when A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. VARIANT supports semi-structured values and path access, unlike a single plain numeric column for arbitrarily nested data.
Question 1071
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. 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?
- Use a plain view with an identical SELECT and assume it stores refreshed aggregate rows permanently at no cost.
- Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
- Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse.
Explanation
Correct Answer
C:The discriminating technical reason is: A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized. Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
Incorrect Answers
A:That is a mistake for a different materialized view precomputation task, where A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. Under ingestion design acceptance conditions, Use a plain view with an identical SELECT and assume it stores refreshed aggregate rows permanently at no cost.
B:That is a mistake for a different stream object change tracking task, where A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. Under ingestion design acceptance conditions, Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
D:Under ingestion design acceptance conditions, Use an unrelated Snowflake warehouse as a file-storage namespace and assume tables automatically locate files by warehouse. That is a mistake for a different table stage file landing task, where 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 does not directly defeat the present stream cdc consumption requirement, whose proper treatment is: Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow.
Question 1072
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Use Snowflake Time Travel AT or BEFORE syntax with a valid historical reference for the affected table.
- Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
- Create an appropriate stream on the table and consume its change records transactionally through a downstream process.
Explanation
Correct Answer
D:Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves. In this post-rollout service review setting, the intended validation is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Incorrect Answers
A:It is not the primary action for the stated stream object change tracking need.
B:That action is relevant when An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
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 stream object change tracking need.
Question 1073
[Peak traffic performance incident] A reviewer recommends: Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size. The requirement remains: A BI engineer is investigating the exact bottleneck observed under production-like load. Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. 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.
- Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
Explanation
Correct Answer
A:In this peak traffic performance incident context, Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster. The recommendation is linked to observable evidence for this exact case: The cluster count rises during bursts and query queue duration falls in matched concurrency tests. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns multi-cluster concurrency scaling, not the requirement in this case. It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
C:It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
D:That option concerns query queueing load analysis, not the requirement in this case. It does not justify the specific multi-cluster scale out versus scale up action or its validation path: The cluster count rises during bursts and query queue duration falls in matched concurrency tests.
Question 1074
[Production migration readiness] The team proposes: Create a supported zero-copy clone of the database or selected schema and track later divergence. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Replication status and a controlled secondary-account query confirm the expected dataset and documented lag.
- The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
- Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
- The exported object files have the expected schema, row counts, and authorized destination path.
Explanation
Correct Answer
B:Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time. This is an outcome test of the specified zero-copy clone for sandbox action under the production migration readiness conditions.
Incorrect Answers
A:In this production migration readiness context, Replication status and a controlled secondary-account query confirm the expected dataset and documented lag. This is an outcome for a different requirement: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It cannot by itself validate the proposed zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
C:In this production migration readiness context, Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. This is an outcome for a different requirement: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It cannot by itself validate the proposed zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
D:In this production migration readiness 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 zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
Question 1075
[Provider and consumer workshop] A data collaboration team is defining the permitted provider and consumer relationship. A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
- Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
- Use zero-copy cloning for an authorized internal copy and distinguish it from a cross-account secure share.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
Explanation
Correct Answer
C:Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption. In this provider and consumer workshop setting, the intended validation is: After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
Incorrect Answers
A:That action is relevant when Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
B:That action is relevant when A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
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. Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
Question 1076
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. The conclusion must be justified with observable verification rather than an undocumented assumption. 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.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
- 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.
Explanation
Correct Answer
D:API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement. In this production cutover rehearsal 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. API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
B: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. API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
C: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. API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
Question 1077
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. 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?
- Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions.
- Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
- Assume every syntactically similar SELECT always reuses cached results even after source tables are modified.
- Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
Explanation
Correct Answer
A:The supportable direction is: Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files. Rely on one engineer's user stage as a durable team-owned contract without assigning the required permissions.
Incorrect Answers
B:Under pipeline incident investigation conditions, Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract. That is a mistake for a different reusable csv file format task, where 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 does not directly defeat the present named internal stage for file reuse requirement, whose proper treatment is: Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
C:That is a mistake for a different persisted result reuse conditions task, where A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. Under pipeline incident investigation conditions, Assume every syntactically similar SELECT always reuses cached results even after source tables are modified.
D:That is a mistake for a different directory table unstructured metadata task, where A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. Under pipeline incident investigation conditions, Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
Question 1078
[Partner onboarding review] A reviewer recommends: Evaluate the Snowflake Native App Framework and supported listing or package deployment lifecycle for consumers. The requirement remains: A privacy reviewer checks a collaboration rollout before new partner access is granted. A software vendor needs to package governed application logic with Snowflake-integrated deployment instead of sending a collection of ad hoc scripts. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Private collaboration environments govern which organizations can discover and share listings beyond simple public marketplace exposure.
- Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
- Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
Explanation
Correct Answer
B:In this partner onboarding review context, Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model. The recommendation is linked to observable evidence for this exact case: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific native app distribution to consumers action or its validation path: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
C:That option concerns streamlit app inside snowflake, not the requirement in this case. It does not justify the specific native app distribution to consumers action or its validation path: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
D:That option concerns cross-region data listing fulfillment, not the requirement in this case. It does not justify the specific native app distribution to consumers action or its validation path: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
Question 1079
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A sandbox warehouse is used for unpredictable experiments and a manager needs credit alerts and a suspension threshold for that warehouse. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Configure a suitable AUTO_SUSPEND interval and AUTO_RESUME for the development warehouse after assessing startup cadence.
- 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 managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS.
Explanation
Correct Answer
C:Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges. In this security control assessment setting, the intended validation is: Monitor usage and alert/suspension events track the warehouse's consumed credits around configured thresholds.
Incorrect Answers
A:That action is relevant when A development warehouse completes a short test query and then remains idle for hours because the team left its suspend behavior unmanaged. It is not the primary action for the stated resource monitor warehouse budgeting need.
B:It is not the primary action for the stated resource monitor warehouse budgeting need.
D:Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges.
Question 1080
[Ingestion design acceptance] A reviewer recommends: Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings. The requirement remains: A data engineering team is checking the design before promoting a pipeline. One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves.
- A table stage gives a convenient table-associated internal landing location without creating a separate named stage.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Explanation
Correct Answer
D:In this ingestion design acceptance context, A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns. The recommendation is linked to observable evidence for this exact case: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns directory table unstructured metadata, not the requirement in this case. It does not justify the specific reusable csv file format action or its validation path: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
B:It does not justify the specific reusable csv file format action or its validation path: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
C:For the ingestion design acceptance 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 reusable csv file format action or its validation path: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.