Snowflake SnowPro Core COF-C03 Practice Test 63 - 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 63

Question 620

In factory telemetry and supplier quality dashboards at a manufacturing group, a validated correction is proposed: Inspect query planning, object statistics, metadata and query shape before changing compute sizing. It responds to: A dashboard experiences long compilation times but engineers keep increasing its warehouse size without changing query planning. Choose the best measurable success criterion.

  1. Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies.
  2. Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes.
  3. A representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.
  4. A controlled account check demonstrates that the chosen production configuration actually enforces the documented control.

Correct Answer: C

Explanation

A.

Morning queries meet agreed latency while batch jobs retain controlled throughput without new unauthorized data copies. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Verify that a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.

B.

Retained datasets meet business recovery requirements and storage growth falls independently of warehouse performance changes. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Verify that a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.

C.

A representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Cloud services coordinate SQL compilation and metadata separately from virtual warehouse execution. To address this, inspect query planning, object statistics, metadata and query shape before changing compute sizing.

D.

A controlled account check demonstrates that the chosen production configuration actually enforces the documented control. This choice does not explain the observed failure mechanism. For factory telemetry and supplier quality dashboards at a manufacturing group, query History attributes most elapsed time to compilation rather than execution and warehouse resources remain underutilized. Verify that a representative dashboard query compiles faster after a targeted approved change while result correctness is unchanged.

Question 621

The Snowflake data engineering case at a publishing group concerns subscription events and finance reporting. Problem: A report team expects a repeated SELECT to use the persisted result cache but keeps modifying the SQL text and underlying data. Evidence: Query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Which paired corrective action and verification is best?

  1. Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results. — verification: Repeated qualified queries show understood result-cache behavior with authorization preserved.
  2. Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. — verification: An unchanged eligible repeated query demonstrates the expected cache behavior without stale results.
  3. Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. — verification: The count respects row-level security and meets the approved performance target.
  4. Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. — verification: Peak reports complete within queue wait targets while isolated query execution time stays stable.

Correct Answer: B

Explanation

A.

Benchmark cache eligibility using consistent authorized roles, parameter settings and unchanged data without exposing protected results. Verify that Repeated qualified queries show understood result-cache behavior with authorization preserved. Query result reuse depends on relevant session and security conditions as well as SQL text. For subscription events and finance reporting at a publishing group, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The appropriate correction is to inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Confirm that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results.

B.

Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Verify that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results. For subscription events and finance reporting at a publishing group, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. Snowflake persisted query results are reused only when the required consistency and context conditions are met.

C.

Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Verify that the count respects row-level security and meets the approved performance target. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. For subscription events and finance reporting at a publishing group, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The appropriate correction is to inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Confirm that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results.

D.

Tune workload concurrency with suitable warehouse isolation or multi-cluster scaling before altering correct query SQL. Verify that Peak reports complete within queue wait targets while isolated query execution time stays stable. Total query latency includes queue time as well as execution and compilation. For subscription events and finance reporting at a publishing group, query history shows new execution work and source-table modification timestamps between otherwise similar report runs. The appropriate correction is to inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Confirm that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results.

Question 622

During a change review for claims actuarial datasets and policy renewal models at an insurance company, the team finds: A team publishes a sensitive metric without being able to show which raw tables and transformations contributed to it. Investigation shows: The dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. What is the most appropriate next Snowflake action?

  1. Apply supported sensitive-data classification and governed object tags with review and ownership of findings.
  2. Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers.
  3. Enable appropriate supported lineage collection and document governed source-to-target transformation ownership.
  4. Route the access change through a documented object owner or authorized security role with approval and minimal privileges.

Correct Answer: C

Explanation

A.

Apply supported sensitive-data classification and governed object tags with review and ownership of findings. Metadata tags provide governance value only when classification and lifecycle controls are reliable. For claims actuarial datasets and policy renewal models at an insurance company, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The better-matched action is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership.

B.

Attach an approved dynamic data masking policy and verify role-aware evaluation for intended consumers. Dynamic masking can enforce column-value protection according to access context. For claims actuarial datasets and policy renewal models at an insurance company, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The better-matched action is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership.

C.

Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. For claims actuarial datasets and policy renewal models at an insurance company, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. Data lineage supports governed interpretation and change impact beyond final result values. A suitable check should show that an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

D.

Route the access change through a documented object owner or authorized security role with approval and minimal privileges. Reading data and delegating object privileges are separate capabilities in Snowflake DAC and RBAC. For claims actuarial datasets and policy renewal models at an insurance company, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The better-matched action is to enable appropriate supported lineage collection and document governed source-to-target transformation ownership.

Question 623

The instrument results and governed case metadata team at a medical testing laboratory records: A team publishes a sensitive metric without being able to show which raw tables and transformations contributed to it. Logs confirm: The dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The recommended action is: Enable appropriate supported lineage collection and document governed source-to-target transformation ownership. What underlying Snowflake solution principle applies?

  1. Metadata tags provide governance value only when classification and lifecycle controls are reliable.
  2. Data lineage supports governed interpretation and change impact beyond final result values.
  3. Dynamic masking can enforce column-value protection according to access context.
  4. Snowflake role authorization must cover both referenced data and chosen execution warehouse.

Correct Answer: B

Explanation

A.

Metadata tags provide governance value only when classification and lifecycle controls are reliable. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The controlling principle is that data lineage supports governed interpretation and change impact beyond final result values.

B.

Data lineage supports governed interpretation and change impact beyond final result values. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. To correct it, enable appropriate supported lineage collection and document governed source-to-target transformation ownership. A successful test shows an auditor traces a seeded metric to the approved source and transformation path without granting unrelated data access.

C.

Dynamic masking can enforce column-value protection according to access context. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The controlling principle is that data lineage supports governed interpretation and change impact beyond final result values.

D.

Snowflake role authorization must cover both referenced data and chosen execution warehouse. This choice does not explain the observed failure mechanism. For instrument results and governed case metadata at a medical testing laboratory, the dashboard's numeric output exists but approved traceability tooling and source-to-target lineage are incomplete. The controlling principle is that data lineage supports governed interpretation and change impact beyond final result values.

Question 624

The Snowflake data engineering case at a municipal authority concerns citizen service reporting and licensed contractor data. Problem: A reporting team expects a fast metadata count on a filtered secured view but the query scans underlying protected rows. Evidence: Query Profile shows a data scan and row access predicates, not a metadata-only computation. Which paired corrective action and verification is best?

  1. Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. — verification: The count respects row-level security and meets the approved performance target.
  2. Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. — verification: An unchanged eligible repeated query demonstrates the expected cache behavior without stale results.
  3. Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. — verification: A repeat benchmark documents expected cold-start cost and maintains the agreed total workload SLA.
  4. Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements. — verification: A three-element test array produces three authorized item rows with correct parent identifiers.

Correct Answer: A

Explanation

A.

Use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Verify that the count respects row-level security and meets the approved performance target. For citizen service reporting and licensed contractor data at a municipal authority, query Profile shows a data scan and row access predicates, not a metadata-only computation. Metadata-derived results cannot bypass filters needed for correct authorized query semantics.

B.

Inspect result-cache eligibility and query/data context before redesigning warehouse sizing based on assumed reuse. Verify that an unchanged eligible repeated query demonstrates the expected cache behavior without stale results. Snowflake persisted query results are reused only when the required consistency and context conditions are met. For citizen service reporting and licensed contractor data at a municipal authority, query Profile shows a data scan and row access predicates, not a metadata-only computation. The appropriate correction is to use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Confirm that the count respects row-level security and meets the approved performance target.

C.

Compare warm and cold warehouse cache behavior and adjust approved suspend timing only when overall cost and latency justify it. Verify that a repeat benchmark documents expected cold-start cost and maintains the agreed total workload SLA. Virtual warehouse local data cache behavior differs from the persisted query result cache. For citizen service reporting and licensed contractor data at a municipal authority, query Profile shows a data scan and row access predicates, not a metadata-only computation. The appropriate correction is to use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Confirm that the count respects row-level security and meets the approved performance target.

D.

Use the appropriate LATERAL FLATTEN and reviewed join grain to expand the intended nested elements. Verify that a three-element test array produces three authorized item rows with correct parent identifiers. Flattening nested semi-structured arrays changes row granularity and requires cardinality awareness. For citizen service reporting and licensed contractor data at a municipal authority, query Profile shows a data scan and row access predicates, not a metadata-only computation. The appropriate correction is to use an authorized query plan and accepted count strategy for the security-filtered dataset rather than assuming global metadata applies. Confirm that the count respects row-level security and meets the approved performance target.

Question 625

For network event logs and account churn models at a telecommunications provider, an engineer diagnoses: An on-call engineer promises instant SQL access to data beyond Time Travel because permanent tables have Fail-safe. The observation is: UNDELETE or historical query attempts exceed Time Travel and Fail-safe is a separate Snowflake-managed recovery stage. The response is: Document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. Which principle best explains the decision?

  1. Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.
  2. Time Travel provides configurable historical recovery only within supported object retention limits.
  3. Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence.
  4. Clean rooms can support collaboration on sensitive data under controlled computations and output rules.

Correct Answer: A

Explanation

A.

Fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery. 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 corresponding fix is to document emergency vendor-assisted recovery limits and implement practical restore procedures within available Time Travel or backups. A successful test shows the recovery runbook gives correct operator actions and timings without claiming direct Fail-safe SQL restore.

B.

Time Travel provides configurable historical recovery only within supported object retention limits. 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 controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

C.

Snowflake zero-copy cloning initially shares immutable micro-partitions while preserving logical object independence. 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 controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

D.

Clean rooms can support collaboration on sensitive data under controlled computations and output rules. 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 controlling principle is that fail-safe is distinct from normal user-controlled Time Travel querying and undrop recovery.

Question 626

In citizen service reporting and licensed contractor data at a municipal authority, a validated correction is proposed: Grant the database role to an appropriate account role and grant that account role to approved users. It responds to: A security team grants a database role to a user and expects the user to choose it directly as their active session role. Choose the best measurable success criterion.

  1. The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.
  2. The user loses unauthorized read access in all permitted role combinations while approved data remains accessible.
  3. A query runs on the specified warehouse without granting access to unrelated compute resources.
  4. Positive and negative tenant tests return only authorized records for each role.

Correct Answer: A

Explanation

A.

The user's supported active account role inherits authorized database object privileges but no unrelated account-wide access. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. Database roles scope database privileges and are activated through account-role inheritance. The documented change is to grant the database role to an appropriate account role and grant that account role to approved users.

B.

The user loses unauthorized read access in all permitted role combinations while approved data remains accessible. This choice does not explain the observed failure mechanism. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The outcome should establish that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

C.

A query runs on the specified warehouse without granting access to unrelated compute resources. This choice does not explain the observed failure mechanism. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The outcome should establish that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

D.

Positive and negative tenant tests return only authorized records for each role. This choice does not explain the observed failure mechanism. For citizen service reporting and licensed contractor data at a municipal authority, role hierarchy records show the database role is not granted through an account role with supported activation. The outcome should establish that the user's supported active account role inherits authorized database object privileges but no unrelated account-wide access.

Question 627

The Snowflake data engineering case at an insurance company concerns claims actuarial datasets and policy renewal models. Problem: A team creates a pipe with a valid COPY statement but new cloud files never load automatically. Evidence: The cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Which paired corrective action and verification is best?

  1. Evaluate supported Snowpipe Streaming ingestion for the event stream with approved connector identity and latency testing. — verification: A controlled event arrives at the target within agreed low-latency limits without a file-staging dependency.
  2. Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. — verification: A newly uploaded sample file appears in the target table once without a manual COPY command.
  3. Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. — verification: A seeded data change appears in the published table within the approved achievable freshness window.
  4. Review compatible schema-evolution or explicit column-mapping behavior and add preflight validation rather than blindly skipping errors. — verification: Representative old and new files load into correct columns and invalid fields raise reviewed exceptions.

Correct Answer: B

Explanation

A.

Evaluate supported Snowpipe Streaming ingestion for the event stream with approved connector identity and latency testing. Verify that a controlled event arrives at the target within agreed low-latency limits without a file-staging dependency. Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. For claims actuarial datasets and policy renewal models at an insurance company, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The appropriate correction is to configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. Confirm that a newly uploaded sample file appears in the target table once without a manual COPY command.

B.

Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. Verify that a newly uploaded sample file appears in the target table once without a manual COPY command. For claims actuarial datasets and policy renewal models at an insurance company, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition.

C.

Inspect dynamic table target lag, dependency graph, compute configuration and refresh policies under representative workload. Verify that a seeded data change appears in the published table within the approved achievable freshness window. Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. For claims actuarial datasets and policy renewal models at an insurance company, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The appropriate correction is to configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. Confirm that a newly uploaded sample file appears in the target table once without a manual COPY command.

D.

Review compatible schema-evolution or explicit column-mapping behavior and add preflight validation rather than blindly skipping errors. Verify that 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 claims actuarial datasets and policy renewal models at an insurance company, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. The appropriate correction is to configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. Confirm that a newly uploaded sample file appears in the target table once without a manual COPY command.

Question 628

Administrators at an identity verification firm plan: Configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges. They are addressing the following problem in verification logs and service risk scoring: A team creates a pipe with a valid COPY statement but new cloud files never load automatically. Which test demonstrates resolution?

  1. A controlled event arrives at the target within agreed low-latency limits without a file-staging dependency.
  2. A seeded data change appears in the published table within the approved achievable freshness window.
  3. A newly uploaded sample file appears in the target table once without a manual COPY command.
  4. A controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible.

Correct Answer: C

Explanation

A.

A controlled event arrives at the target within agreed low-latency limits without a file-staging dependency. Snowpipe Streaming handles row or event ingestion differently from file-oriented Snowpipe. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Verify that a newly uploaded sample file appears in the target table once without a manual COPY command.

B.

A seeded data change appears in the published table within the approved achievable freshness window. Dynamic tables maintain derived data through managed refresh behavior subject to supported target lag and compute. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Verify that a newly uploaded sample file appears in the target table once without a manual COPY command.

C.

A newly uploaded sample file appears in the target table once without a manual COPY command. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Snowpipe file ingestion depends on event notification or an explicit REST request, not simply a stored pipe definition. To address this, configure supported Snowpipe auto-ingest notifications and validate storage events and pipe privileges.

D.

A controlled staged-file list succeeds for approved prefixes and a disallowed prefix remains inaccessible. Snowflake connectivity spans internal roles and external provider identity policy. For verification logs and service risk scoring at an identity verification firm, the cloud storage path contains fresh files and the pipe is running, yet notification integration or event subscription is missing. Verify that a newly uploaded sample file appears in the target table once without a manual COPY command.

Question 629

A Snowflake analyst supporting reservation changes and partner analytics at a travel booking platform intends: Grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. The reported condition is: A team grants usage on a database but expects that grant to permit a reporting role to read all tables inside a schema. Identify the most decisive diagnostic record.

  1. The role can resolve the database name but lacks schema usage and SELECT privileges on the required table.
  2. Privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation.
  3. The proposed UDF contract expects state-changing workflow control rather than a per-row returned value.
  4. Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct.

Correct Answer: A

Explanation

A.

The role can resolve the database name but lacks schema usage and SELECT privileges on the required table. Object visibility and data access depend on privileges at multiple securable-object hierarchy levels. The corresponding fix is to grant only necessary USAGE on parent database and schema plus table SELECT through an approved role. A successful test should show that an authorized report reads the target table and cannot access an unrelated schema; the reported setting is: a snowflake analyst supporting reservation changes and partner analytics at a travel booking platform intends: grant only necessary usage on parent database and schema plus table select through an approved.

B.

Privilege inspection shows the pipe is a separate schema object and the user cannot run its designated management operation. This choice does not explain the observed failure mechanism. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. To address this, grant only necessary USAGE on parent database and schema plus table SELECT through an approved role.

C.

The proposed UDF contract expects state-changing workflow control rather than a per-row returned value. This choice does not explain the observed failure mechanism. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. To address this, grant only necessary USAGE on parent database and schema plus table SELECT through an approved role.

D.

Notebook execution context points to an inactive or unauthorized warehouse while role grants to the data objects are already correct. This choice does not explain the observed failure mechanism. For reservation changes and partner analytics at a travel booking platform, the role can resolve the database name but lacks schema usage and SELECT privileges on the required table. To address this, grant only necessary USAGE on parent database and schema plus table SELECT through an approved role.

Question 630

To correct this issue at a hospitality chain involving booking data marts and occupancy forecasts: An analyst enables search optimization on a huge table to speed a report that aggregates most records every night. The team applies: Choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking. What outcome should close the incident?

  1. The lookup remains within SLA and extraneous clustering maintenance costs disappear.
  2. A validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime.
  3. The aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.
  4. The count respects row-level security and meets the approved performance target.

Correct Answer: C

Explanation

A.

The lookup remains within SLA and extraneous clustering maintenance costs disappear. Clustering keys are workload-specific optimizations and are not universally beneficial. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The outcome should establish that the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.

B.

A validated query produces correct row counts and any enabled acceleration demonstrably improves measured runtime. Extra query compute cannot correct incorrect SQL semantics. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The outcome should establish that the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.

C.

The aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. Search optimization is designed for selective access patterns, not all-table analytic scans. The documented change is to choose an optimization suited to large aggregate access, such as SQL restructuring or appropriate precomputation, after benchmarking.

D.

The count respects row-level security and meets the approved performance target. Metadata-derived results cannot bypass filters needed for correct authorized query semantics. For booking data marts and occupancy forecasts at a hospitality chain, query Profile shows broad scans with few selective equality or point lookup predicates. The outcome should establish that the aggregate meets target runtime with a documented cost tradeoff and no unnecessary search-index expense.

SnowPro Core COF-C03 Practice Tests