Snowflake SnowPro Core COF-C03 Practice Test 24 - Prepaway
Practice Exams:

Pass Snowflake SnowPro Core COF-C03 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$14.99
$74.99 $89.98

SnowPro Core COF-C03 Premium Bundle


  • Premium File 116 Questions & Answers. Last update: Nov 17, 2026
  • Study Guide 222 Pages

Snowflake SnowPro Core COF-C03 Practice Test 24

Question 230

In network event logs and account churn models at a telecommunications provider, a validated correction is proposed: Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. It responds to: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. Choose the best measurable success criterion.

  1. The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.
  2. An allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated.
  3. A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle.
  4. A staged app installs under approved necessary privileges and cannot query unrelated protected objects.

Correct Answer: A

Explanation

A.

The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. The documented change is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups.

B.

An allowed test drop is recoverable within the documented approved window and out-of-window limits are clearly stated. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

C.

A governed clone supports testing without an initial full data rewrite and has a documented storage-cost lifecycle. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

D.

A staged app installs under approved necessary privileges and cannot query unrelated protected objects. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, uNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The outcome should establish that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

Question 231

The Snowflake data engineering team at a food distribution cooperative plans to: Pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution. The issue affecting supplier pricing and regional inventory models is: A deployment pipeline runs Snowflake SQL from a repository but pulls an unreviewed experimental branch in production. Which finding best distinguishes this cause from other Snowflake failures?

  1. Integration inventory shows an allowed destination list much wider than the program's documented business requirement.
  2. Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal.
  3. Resolved Git repository stage or branch reference differs from the approved tagged release.
  4. Resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary.

Correct Answer: C

Explanation

A.

Integration inventory shows an allowed destination list much wider than the program's documented business requirement. External network and API integrations should constrain egress destinations and execution privileges. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. For this incident, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

B.

Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. Snowflake connectivity spans internal roles and external provider identity policy. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. For this incident, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

C.

Resolved Git repository stage or branch reference differs from the approved tagged release. Source integration needs version control and approval just like any other production schema deployment. To correct it, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution. Verification should establish that a controlled release executes only reviewed SQL and rejects unapproved branch changes; the reported setting is: the snowflake data engineering team at a food distribution cooperative plans to: pin supported git integration workflow to approved repository paths and immutable reviewed versions before execution.

D.

Resolved stage URL and storage role inventory show the target path is outside the approved recipient boundary. Unloading data creates an outbound data-governance boundary that requires destination authorization. For supplier pricing and regional inventory models at a food distribution cooperative, resolved Git repository stage or branch reference differs from the approved tagged release. For this incident, pin supported Git integration workflow to approved repository paths and immutable reviewed versions before execution.

Question 232

During a change review for loan servicing analytics and audit trails at a cooperative credit union, the team finds: Two analysts compare query cache savings using different roles and assume an exact result cache hit is universally shareable. Investigation shows: Query contexts differ in security and session conditions and tests do not control source change timing. What is the most appropriate next Snowflake action?

  1. Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse.
  2. Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it.
  3. Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys.
  4. Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

Correct Answer: D

Explanation

A.

Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Snowflake persisted query results are reused only when the required consistency and context conditions are met. For loan servicing analytics and audit trails at a cooperative credit union, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

B.

Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. Virtual warehouse local data cache behavior differs from the persisted query result cache. For loan servicing analytics and audit trails at a cooperative credit union, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

C.

Review join/sort memory needs, SQL shape and approved warehouse capacity before changing clustering keys. Query Profile distinguishes memory spill from excessive table scans and pruning inefficiency. For loan servicing analytics and audit trails at a cooperative credit union, query contexts differ in security and session conditions and tests do not control source change timing. Instead, benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results.

D.

Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results. For loan servicing analytics and audit trails at a cooperative credit union, query contexts differ in security and session conditions and tests do not control source change timing. Query result reuse depends on relevant session and security conditions as well as SQL text. A confirming result should show that repeated qualified queries show understood result-cache behavior with authorization preserved.

Question 233

The cargo scans and berth utilization reports environment at a container port operator has an incident: An application creates an intermediate dataset as a temporary table then expects another session to retrieve it the following morning. The difference-making observation is: The second session cannot resolve the temporary object although the creator session could query it earlier. Choose the most defensible corrective response.

  1. Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.
  2. Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production.
  3. Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences.
  4. Inspect parameter hierarchy and reset or adjust the session-level override with a controlled application test.

Correct Answer: A

Explanation

A.

Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. Temporary tables are scoped to sessions and should not be treated as persistent shared datasets. The expected outcome is that a new authorized session retrieves the intended prepared dataset after the original session ends.

B.

Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. To address this, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

C.

Select a suitable permanent-table retention and disaster-recovery design after reviewing Time Travel and Fail-safe differences. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. To address this, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

D.

Inspect parameter hierarchy and reset or adjust the session-level override with a controlled application test. This choice does not explain the observed failure mechanism. For cargo scans and berth utilization reports at a container port operator, the second session cannot resolve the temporary object although the creator session could query it earlier. To address this, use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.

Question 234

To correct this issue at a manufacturing group involving factory telemetry and supplier quality dashboards: A warehouse imports a supplier CSV file but amounts appear under the wrong columns while row counts look plausible. The team applies: Correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO. What outcome should close the incident?

  1. A controlled new document appears in the governed directory inventory and is retrievable by approved users.
  2. Representative old and new files load into correct columns and invalid fields raise reviewed exceptions.
  3. A controlled load reads authorized files through approved integration and no plaintext secret is required in the script.
  4. A test batch loads the intended amounts and customer IDs into their correct columns without silent shift.

Correct Answer: D

Explanation

A.

A controlled new document appears in the governed directory inventory and is retrievable by approved users. Directory metadata can require refresh or event configuration independent of files stored externally. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The outcome should establish that a test batch loads the intended amounts and customer IDs into their correct columns without silent shift.

B.

Representative old and new files load into correct columns and invalid fields raise reviewed exceptions. Bulk ingestion correctness requires explicit handling of changing file schema and COPY options. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The outcome should establish that a test batch loads the intended amounts and customer IDs into their correct columns without silent shift.

C.

A controlled load reads authorized files through approved integration and no plaintext secret is required in the script. Storage integrations provide a governed trust boundary for external staged data. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. The outcome should establish that a test batch loads the intended amounts and customer IDs into their correct columns without silent shift.

D.

A test batch loads the intended amounts and customer IDs into their correct columns without silent shift. For factory telemetry and supplier quality dashboards at a manufacturing group, stage preview shows source uses a pipe delimiter and quoted values while the configured file format assumes commas. Snowflake load parsing depends on the staged file format matching the actual source encoding. The documented change is to correct a reusable file format and validate staged sample parsing before rerunning approved COPY INTO.

Question 235

At an environmental institute, a Snowflake analyst supporting monitoring station records and research datasets finds: Two organizations plan a matching analysis but propose exposing raw joined customer identifiers to both parties. They confirm: A trial query returns person-level matching keys instead of allowed aggregate or privacy-controlled results. Select the action and acceptance-test pair best matched to these facts.

  1. Configure a supported secure data share with least privilege and document relevant region/account constraints. — verification: An authorized consumer queries the shared object while no unmanaged full dataset export is required.
  2. Create a supported reader-account collaboration path with scoped shared objects and approved consumer roles. — verification: The partner reads the intended report but cannot enumerate unrelated provider data.
  3. Use supported clean room constraints and approved collaboration templates to restrict outputs and data access. — verification: The approved overlap statistic is available while individual participant records cannot be exported.
  4. Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. — verification: The recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

Correct Answer: C

Explanation

A.

Configure a supported secure data share with least privilege and document relevant region/account constraints. Verify that an authorized consumer queries the shared object while no unmanaged full dataset export is required. Snowflake secure sharing can provide governed access without traditional physical data copying. For monitoring station records and research datasets at an environmental institute, a trial query returns person-level matching keys instead of allowed aggregate or privacy-controlled results. The appropriate correction is to use supported clean room constraints and approved collaboration templates to restrict outputs and data access. Confirm that the approved overlap statistic is available while individual participant records cannot be exported.

B.

Create a supported reader-account collaboration path with scoped shared objects and approved consumer roles. Verify that the partner reads the intended report but cannot enumerate unrelated provider data. Reader accounts enable supported consumption without requiring a separate self-managed Snowflake account, but scope still matters. For monitoring station records and research datasets at an environmental institute, a trial query returns person-level matching keys instead of allowed aggregate or privacy-controlled results. The appropriate correction is to use supported clean room constraints and approved collaboration templates to restrict outputs and data access. Confirm that the approved overlap statistic is available while individual participant records cannot be exported.

C.

Use supported clean room constraints and approved collaboration templates to restrict outputs and data access. Verify that the approved overlap statistic is available while individual participant records cannot be exported. For monitoring station records and research datasets at an environmental institute, a trial query returns person-level matching keys instead of allowed aggregate or privacy-controlled results. Clean rooms can support collaboration on sensitive data under controlled computations and output rules.

D.

Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Verify that the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. For monitoring station records and research datasets at an environmental institute, a trial query returns person-level matching keys instead of allowed aggregate or privacy-controlled results. The appropriate correction is to use supported clean room constraints and approved collaboration templates to restrict outputs and data access. Confirm that the approved overlap statistic is available while individual participant records cannot be exported.

Question 236

The passenger demand and ground service metrics environment at an airport authority has an incident: A large fact table has well-partitioned date values but a report wraps the date in a function and scans most partitions. The difference-making observation is: Query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Choose the most defensible corrective response.

  1. Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage.
  2. Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production.
  3. Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency.
  4. Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

Correct Answer: D

Explanation

A.

Use a supported durable object or persisted transfer appropriate to the business lifecycle rather than session-scoped temporary storage. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

B.

Confirm supported Iceberg table management mode, catalog responsibilities, external-volume access and data retention before production. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

C.

Benchmark a supported larger warehouse size and query optimization before adding clusters intended primarily for concurrency. This choice does not explain the observed failure mechanism. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

D.

Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning. A confirming result should show that a seeded date-range query returns the same records while substantially fewer partitions are scanned.

Question 237

The Snowflake data engineering team at a payments processor plans to: Reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. The issue affecting settlement reconciliation and fraud-monitoring datasets is: An integration user loses the ability to list cloud object files after a cloud IAM role policy change. Which finding best distinguishes this cause from other Snowflake failures?

  1. Integration inventory shows an allowed destination list much wider than the program's documented business requirement.
  2. New sessions use a different default role and warehouse from the earlier connector configuration.
  3. Directory table metadata is stale relative to the cloud object listing after an external upload.
  4. Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal.

Correct Answer: D

Explanation

A.

Integration inventory shows an allowed destination list much wider than the program's documented business requirement. External network and API integrations should constrain egress destinations and execution privileges. For settlement reconciliation and fraud-monitoring datasets at a payments processor, Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. To address this, reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access.

B.

New sessions use a different default role and warehouse from the earlier connector configuration. Snowflake drivers inherit or specify security and execution context separately from successful transport authentication. For settlement reconciliation and fraud-monitoring datasets at a payments processor, Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. To address this, reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access.

C.

Directory table metadata is stale relative to the cloud object listing after an external upload. Directory metadata can require refresh or event configuration independent of files stored externally. For settlement reconciliation and fraud-monitoring datasets at a payments processor, Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. To address this, reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access.

D.

Snowflake storage integration remains defined but external cloud audit logs show denied object reads by the delegated principal. Snowflake connectivity spans internal roles and external provider identity policy. The corresponding fix is to reconcile supported external cloud IAM trust and path permissions for the Snowflake storage integration without adding broad access. A successful test should show that a controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible.

Question 238

For network event logs and account churn models at a telecommunications provider, an engineer diagnoses: Business users ask an AI analyst for net revenue but the semantic model describes gross invoice amount as net revenue. The observation is: Generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The response is: Review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases. Which principle best explains the decision?

  1. Natural language analytics accuracy depends on governed metric definitions and source semantics.
  2. A retrieval service needs its own indexed-data freshness and authorization controls.
  3. Application interfaces do not replace authorization checks at the data and execution boundary.
  4. Independent virtual warehouses support workload isolation over shared centralized data.

Correct Answer: A

Explanation

A.

Natural language analytics accuracy depends on governed metric definitions and source semantics. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The documented change is to review and correct the approved semantic model metric definition and test natural-language-to-SQL outputs against reference cases. A successful test shows the seeded net-revenue query matches a reviewed SQL baseline across sample periods.

B.

A retrieval service needs its own indexed-data freshness and authorization controls. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The controlling principle is that natural language analytics accuracy depends on governed metric definitions and source semantics.

C.

Application interfaces do not replace authorization checks at the data and execution boundary. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The controlling principle is that natural language analytics accuracy depends on governed metric definitions and source semantics.

D.

Independent virtual warehouses support workload isolation over shared centralized data. This choice does not explain the observed failure mechanism. For network event logs and account churn models at a telecommunications provider, generated SQL and semantic-model metrics select the wrong field even though source invoice rows are accurate. The controlling principle is that natural language analytics accuracy depends on governed metric definitions and source semantics.

Question 239

The student analytics and research-grant reporting team at a public university records: An analyst downsizes warehouse compute hoping to reduce a growing table-storage bill caused by duplicate historical records. Logs confirm: Consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. The recommended action is: Separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. What underlying Snowflake solution principle applies?

  1. Snowflake separates independently scalable query compute from persistent managed table storage.
  2. Independent virtual warehouses support workload isolation over shared centralized data.
  3. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution.
  4. Compute-credit consumption and managed storage usage are distinct cost drivers.

Correct Answer: D

Explanation

A.

Snowflake separates independently scalable query compute from persistent managed table storage. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. The controlling principle is that compute-credit consumption and managed storage usage are distinct cost drivers.

B.

Independent virtual warehouses support workload isolation over shared centralized data. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. The controlling principle is that compute-credit consumption and managed storage usage are distinct cost drivers.

C.

Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. This choice does not explain the observed failure mechanism. For student analytics and research-grant reporting at a public university, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. The controlling principle is that compute-credit consumption and managed storage usage are distinct cost drivers.

D.

Compute-credit consumption and managed storage usage are distinct cost drivers. For student analytics and research-grant reporting at a public university, consumption reports show storage bytes rising while warehouse execution credits remain relatively stable. To correct it, separate storage inventory and retention decisions from warehouse sizing and remove only approved redundant data safely. A successful test shows retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes.

Question 240

The Snowflake data engineering team at an airport authority plans to: Rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. The issue affecting passenger demand and ground service metrics is: A large fact table has well-partitioned date values but a report wraps the date in a function and scans most partitions. Which finding best distinguishes this cause from other Snowflake failures?

  1. The second session cannot resolve the temporary object although the creator session could query it earlier.
  2. Query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval.
  3. Governance review finds external catalog or metadata ownership assumptions do not match the configured Iceberg management mode.
  4. Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables.

Correct Answer: B

Explanation

A.

The second session cannot resolve the temporary object although the creator session could query it earlier. Temporary tables are scoped to sessions and should not be treated as persistent shared datasets. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

B.

Query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Snowflake stores columnar micro-partition metadata that can reduce scans when predicates permit pruning. To address this, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it. Confirm that a seeded date-range query returns the same records while substantially fewer partitions are scanned.

C.

Governance review finds external catalog or metadata ownership assumptions do not match the configured Iceberg management mode. Open table format interoperability needs explicit metadata and storage management boundaries. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

D.

Object metadata identifies TRANSIENT storage and recovery assumptions rely on safeguards unavailable to transient tables. Permanent, transient and temporary tables have different lifecycle and data protection characteristics. For passenger demand and ground service metrics at an airport authority, query Profile reports low micro-partition pruning and many scanned partitions despite a selective intended date interval. Instead, rewrite the supported predicate to favor direct filterable ranges and assess clustering only if workload evidence warrants it.

SnowPro Core COF-C03 Practice Tests