Snowflake SnowPro Core COF-C03 Practice Test 47
Question 460
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Inspect pruning and the overlap of the filter column's values, then tune a supported clustering strategy if warranted.
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
- Evaluate Search Optimization Service for the supported predicate pattern and account edition after reviewing query profile.
Explanation
Correct Answer
D:Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency. In this peak traffic performance incident setting, the intended validation is: The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
Incorrect Answers
A:That action is relevant when Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
B: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. Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency.
C:That action is relevant when A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It is not the primary action for the stated search optimization selective lookup need.
Question 461
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
Explanation
Correct Answer
A:Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model. In this post-rollout service review setting, the intended validation is: A compatible engine discovers the expected Iceberg metadata and Snowflake queries return reconciled rows under documented catalog settings.
Incorrect Answers
B:That action is relevant when A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It is not the primary action for the stated iceberg interoperability decision need.
C:That action is relevant when A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It is not the primary action for the stated iceberg interoperability decision need.
D:That action is relevant when A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. Iceberg tables provide an open-format table metadata layer; catalog integration and write permissions depend on their chosen management model.
Question 462
[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 Snowflake action best meets this specific requirement?
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
- Configure appropriate future grants for the required schema scope while preserving narrowly defined access roles.
Explanation
Correct Answer
B:Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable. In this identity and governance change request setting, the intended validation is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Incorrect Answers
A:That action is relevant when 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 is not the primary action for the stated inherited functional role grants need.
C:That action is relevant when A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It is not the primary action for the stated inherited functional role grants need.
D:That action is relevant when Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. It is not the primary action for the stated inherited functional role grants need.
Question 463
[Partner onboarding review] A reviewer recommends: Create and govern a suitable Snowflake Marketplace listing with the intended visibility, terms, and fulfillment model. The requirement remains: A privacy reviewer checks a collaboration rollout before new partner access is granted. A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
- Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication.
- Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
- Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone.
Explanation
Correct Answer
C:In this partner onboarding review context, Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts. The recommendation is linked to observable evidence for this exact case: An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific marketplace listing discovery action or its validation path: An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
B:For the partner onboarding review conditions, Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication. That explanation applies to a different direct share cross-account access problem: A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. It does not justify the specific marketplace listing discovery action or its validation path: An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
D:For the partner onboarding review conditions, Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone. That explanation applies to a different replication across regions for availability problem: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It does not justify the specific marketplace listing discovery action or its validation path: An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
Question 464
[Provider and consumer workshop] A data collaboration team is defining the permitted provider and consumer relationship. 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 reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection.
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
- Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
- Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort.
Explanation
Correct Answer
D:Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
Incorrect Answers
A:That action is relevant when An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It is not the primary action for the stated time travel versus fail-safe recoverability need.
B:That action is relevant when Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
C:That action is relevant when An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
Question 465
[Architecture planning workshop] The team proposes: Assign ELT and dashboard queries to separate Snowflake virtual warehouses while keeping shared storage. Its actual requirement is: 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 observation most directly validates success?
- Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
- Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions.
Explanation
Correct Answer
A:Warehouses isolate compute and cache resources, so the two teams can query the same persisted data without competing for one active warehouse. This is an outcome test of the specified independent compute for bi and elt action under the architecture planning workshop conditions.
Incorrect Answers
B:In this architecture planning workshop 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 independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
C:In this architecture planning workshop 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 independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
D:In this architecture planning workshop 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 independent compute for bi and elt action; the appropriate test is: Warehouse-specific query and load histories show dashboard queueing remaining low while the ELT warehouse runs at peak load.
Question 466
[Production cutover rehearsal] The team proposes: Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. 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 conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The exported object files have the expected schema, row counts, and authorized destination path.
- A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
- Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
- LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
Explanation
Correct Answer
B:A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows. This is an outcome test of the specified reusable csv file format action under the production cutover rehearsal conditions. A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Incorrect Answers
A:In this production cutover rehearsal 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 reusable csv file format action; the appropriate test is: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
C:In this production cutover rehearsal context, 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 reusable csv file format action; the appropriate test is: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
D:In this production cutover rehearsal 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 reusable csv file format action; the appropriate test is: A staged preview and validation load reconcile embedded delimiter strings and expected column counts across sample rows.
Question 467
[Production migration readiness] The team proposes: Create an appropriate stream on the table and consume its change records transactionally through a downstream process. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
- Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
Explanation
Correct Answer
C:A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome test of the specified stream object change tracking action under the production migration readiness conditions. Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
Incorrect Answers
A:In this production migration readiness context, SELECT against the external table returns staged records after location metadata has been refreshed appropriately. This is an outcome for a different requirement: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
B:In this production migration readiness context, Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. This is an outcome for a different requirement: An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
D:In this production migration readiness context, Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target. This is an outcome for a different requirement: A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Question 468
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure a supported federated SSO security integration and verify identity, certificates, and account routing.
- Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
- Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges.
- Configure the available private connectivity option for the eligible edition and cloud, then validate DNS and routing.
Explanation
Correct Answer
D:Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions. In this production compliance review setting, the intended validation is: Network-path evidence shows traffic using the configured private endpoint and public-route attempts are not used.
Incorrect Answers
A:That action is relevant when An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
B:That action is relevant when A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. It is not the primary action for the stated private network endpoint verification need.
C:That action is relevant when An organization must restrict logins to approved corporate egress ranges even when credentials are correct. Private endpoint routing is an infrastructure-level feature independent of Snowflake object permissions.
Question 469
[Ingestion design acceptance] A reviewer recommends: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications. The requirement remains: A data engineering team is checking the design before promoting a pipeline. Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Explanation
Correct Answer
A:In this ingestion design acceptance context, Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches. The recommendation is linked to observable evidence for this exact case: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B: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 snowpipe file event auto ingest action or its validation path: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
C:Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
D:For the ingestion design acceptance conditions, A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns. That explanation applies to a different reusable csv file format problem: 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 justify the specific snowpipe file event auto ingest action or its validation path: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
Question 470
[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 Snowflake action best meets this specific requirement?
- Create a named CSV file format with the actual FIELD_DELIMITER, SKIP_HEADER, and FIELD_OPTIONALLY_ENCLOSED_BY settings.
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
Explanation
Correct Answer
B:Named internal stages support managed file staging and reusable load references across authorized sessions. In this pipeline incident investigation setting, the intended validation is: LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows. The answer targets the described requirement rather than an unrelated feature.
Incorrect Answers
A: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. It is not the primary action for the stated named internal stage for file reuse need.
C: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. It is not the primary action for the stated named internal stage for file reuse need.
D:That action is relevant when A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. It is not the primary action for the stated named internal stage for file reuse need.