SnowPro Core COF-C03 Practice Test 92
Question 910
A deployment team has configured this Snowflake capability: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- End-to-end test rows become queryable at the required latency without staging files.
- The rejected-record count and load outcome reconcile with the source batch manifest.
- The monitoring report includes a seeded failed refresh and the measured lag for each table.
- A controlled update produces expected change records that can be consumed in one transaction.
Explanation
Correct Answer
B:COPY loading error behavior is configurable; silent skipping without review can hide data loss. The stated acceptance evidence is: The rejected-record count and load outcome reconcile with the source batch manifest. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive. That explains the role of “End-to-end test rows become queryable at the required latency without staging files”, but the present requirement calls for “The rejected-record count and load outcome reconcile with the source batch manifest”: COPY loading error behavior is configurable; silent skipping without review can hide data loss.
C:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. That explains the role of “The monitoring report includes a seeded failed refresh and the measured lag for each table”, but the present requirement calls for “The rejected-record count and load outcome reconcile with the source batch manifest”: COPY loading error behavior is configurable; silent skipping without review can hide data loss.
D:Streams track the table changes visible between transactional consumption points without cloning the full table each time. That explains the role of “A controlled update produces expected change records that can be consumed in one transaction”, but the present requirement calls for “The rejected-record count and load outcome reconcile with the source batch manifest”: COPY loading error behavior is configurable; silent skipping without review can hide data loss.
Question 911
A deployment team has configured this Snowflake capability: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The resulting DataFrame writes expected rows to an approved table without unrestricted exports.
- The tuned query shows reduced remote spill and correct output rows.
- Usage history shows no long idle runtime and morning queries resume automatically.
- Measured credit use falls within budget while average queueing remains acceptable.
Explanation
Correct Answer
B:Large intermediate joins that exceed memory can create costly remote spill and longer runtimes. The stated acceptance evidence is: The tuned query shows reduced remote spill and correct output rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. That explains the role of “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”, but the present requirement calls for “The tuned query shows reduced remote spill and correct output rows”: Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
C:Suspension releases active compute after an idle period rather than relying on staff to stop it. That explains the role of “Usage history shows no long idle runtime and morning queries resume automatically”, but the present requirement calls for “The tuned query shows reduced remote spill and correct output rows”: Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
D:ECONOMY prioritizes fuller use of existing clusters before starting more compute. That explains the role of “Measured credit use falls within budget while average queueing remains acceptable”, but the present requirement calls for “The tuned query shows reduced remote spill and correct output rows”: Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
Question 912
A deployment team has configured this Snowflake capability: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The consumer creates a database from the share and sees only the granted objects.
- A disaster-recovery drill can access the replicated secondary account after loss of the primary region.
- The consumer queries only the approved projection and cannot read the underlying protected table.
- Historical query output matches the expected pre-change or post-change rows around the recorded statement.
Explanation
Correct Answer
D:Statement-based history offers precise temporal reference points for eligible Snowflake objects. The stated acceptance evidence is: Historical query output matches the expected pre-change or post-change rows around the recorded statement. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. That explains the role of “The consumer creates a database from the share and sees only the granted objects”, but the present requirement calls for “Historical query output matches the expected pre-change or post-change rows around the recorded statement”: Statement-based history offers precise temporal reference points for eligible Snowflake objects.
B:Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience. That explains the role of “A disaster-recovery drill can access the replicated secondary account after loss of the primary region”, but the present requirement calls for “Historical query output matches the expected pre-change or post-change rows around the recorded statement”: Statement-based history offers precise temporal reference points for eligible Snowflake objects.
C:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. That explains the role of “The consumer queries only the approved projection and cannot read the underlying protected table”, but the present requirement calls for “Historical query output matches the expected pre-change or post-change rows around the recorded statement”: Statement-based history offers precise temporal reference points for eligible Snowflake objects.
Question 913
A deployment team has configured this Snowflake capability: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A test SELECT invokes the UDF and returns the expected value for edge-case inputs.
- The reporting service successfully connects and retrieves authorized columns.
- The revised profile shows lower remote spill and acceptable query latency at a measured credit cost.
- Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables.
Explanation
Correct Answer
D:The platform combines managed storage and compute with authentication and object privileges across its data lifecycle. The stated acceptance evidence is: Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions. That explains the role of “A test SELECT invokes the UDF and returns the expected value for edge-case inputs”, but the present requirement calls for “Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables”: The platform combines managed storage and compute with authentication and object privileges across its data lifecycle.
B:ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication. That explains the role of “The reporting service successfully connects and retrieves authorized columns”, but the present requirement calls for “Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables”: The platform combines managed storage and compute with authentication and object privileges across its data lifecycle.
C:Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query. That explains the role of “The revised profile shows lower remote spill and acceptable query latency at a measured credit cost”, but the present requirement calls for “Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables”: The platform combines managed storage and compute with authentication and object privileges across its data lifecycle.
Question 914
A deployment team has configured this Snowflake capability: Enforce the supported MFA and authentication policy for the target user population. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Direct SQL, BI and application queries yield the same row and column policy results.
- A test login requires the configured factor and expected exception accounts are reviewed.
- Storage reporting isolates active data from retained history and shows the trend after policy changes.
- Usage reporting attributes representative jobs to the intended cost centers.
Explanation
Correct Answer
B:MFA raises assurance beyond a single compromised password or reused secret. The stated acceptance evidence is: A test login requires the configured factor and expected exception accounts are reviewed. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Data-level controls travel with queries across clients and minimize inconsistent authorization behavior. That explains the role of “Direct SQL, BI and application queries yield the same row and column policy results”, but the present requirement calls for “A test login requires the configured factor and expected exception accounts are reviewed”: MFA raises assurance beyond a single compromised password or reused secret.
C:Retained historical data can contribute to storage billing even when active row counts are stable. That explains the role of “Storage reporting isolates active data from retained history and shows the trend after policy changes”, but the present requirement calls for “A test login requires the configured factor and expected exception accounts are reviewed”: MFA raises assurance beyond a single compromised password or reused secret.
D:Clear compute ownership and query identification improve chargeback compared with account totals alone. That explains the role of “Usage reporting attributes representative jobs to the intended cost centers”, but the present requirement calls for “A test login requires the configured factor and expected exception accounts are reviewed”: MFA raises assurance beyond a single compromised password or reused secret.
Question 915
A deployment team has configured this Snowflake capability: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The corrected connector establishes a session and executes a minimal authorized query.
- Refresh history and observed data age show whether the target lag objective is being met.
- The service reads its permitted cloud prefix and cannot enumerate unrelated external storage.
- A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload.
Explanation
Correct Answer
D:COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards. The stated acceptance evidence is: A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Client authentication and session authorization failures are unrelated to warehouse processing capacity. That explains the role of “The corrected connector establishes a session and executes a minimal authorized query”, but the present requirement calls for “A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload”: COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards.
B:Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval. That explains the role of “Refresh history and observed data age show whether the target lag objective is being met”, but the present requirement calls for “A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload”: COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards.
C:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. That explains the role of “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”, but the present requirement calls for “A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload”: COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards.
Question 916
A deployment team has configured this Snowflake capability: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The test batch updates existing IDs, inserts new IDs and maintains intended row counts.
- Warehouse load history shows lower queued overload time after adding capacity.
- DST boundary test rows map to expected reporting timestamps without accidental date shifts.
- An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items.
Explanation
Correct Answer
B:Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources. The stated acceptance evidence is: Warehouse load history shows lower queued overload time after adding capacity. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:MERGE combines conditional matched and unmatched DML paths in one operation. That explains the role of “The test batch updates existing IDs, inserts new IDs and maintains intended row counts”, but the present requirement calls for “Warehouse load history shows lower queued overload time after adding capacity”: Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
C:Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved. That explains the role of “DST boundary test rows map to expected reporting timestamps without accidental date shifts”, but the present requirement calls for “Warehouse load history shows lower queued overload time after adding capacity”: Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
D:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. That explains the role of “An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items”, but the present requirement calls for “Warehouse load history shows lower queued overload time after adding capacity”: Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
Question 917
A deployment team has configured this Snowflake capability: Review the Time Travel and Fail-safe retention windows and storage effects. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The consumer creates a database from the share and sees only the granted objects.
- Storage metrics show retained history according to the approved policy after the drop.
- The secondary account shows the expected objects and the replication lag stays within target.
- A test recipient discovers the listing and accesses the authorized shared objects after approval.
Explanation
Correct Answer
B:Historical storage can remain recoverable or billable according to the table type and retention rules. The stated acceptance evidence is: Storage metrics show retained history according to the approved policy after the drop. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. That explains the role of “The consumer creates a database from the share and sees only the granted objects”, but the present requirement calls for “Storage metrics show retained history according to the approved policy after the drop”: Historical storage can remain recoverable or billable according to the table type and retention rules.
C:Replication propagates supported database state between accounts rather than rebuilding tables through files. That explains the role of “The secondary account shows the expected objects and the replication lag stays within target”, but the present requirement calls for “Storage metrics show retained history according to the approved policy after the drop”: Historical storage can remain recoverable or billable according to the table type and retention rules.
D:Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share. That explains the role of “A test recipient discovers the listing and accesses the authorized shared objects after approval”, but the present requirement calls for “Storage metrics show retained history according to the approved policy after the drop”: Historical storage can remain recoverable or billable according to the table type and retention rules.
Question 918
A deployment team has configured this Snowflake capability: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The worksheet executes the test query and its history displays the selected execution context.
- Usage reporting groups credits by the named department warehouses.
- Required controls are licensed and exercised successfully in the chosen edition.
- A test account in the proposed edition exposes all required security controls and the edition contract supports them.
Explanation
Correct Answer
D:Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption. The stated acceptance evidence is: A test account in the proposed edition exposes all required security controls and the edition contract supports them. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions. That explains the role of “The worksheet executes the test query and its history displays the selected execution context”, but the present requirement calls for “A test account in the proposed edition exposes all required security controls and the edition contract supports them”: Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
B:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. That explains the role of “Usage reporting groups credits by the named department warehouses”, but the present requirement calls for “A test account in the proposed edition exposes all required security controls and the edition contract supports them”: Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
C:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Required controls are licensed and exercised successfully in the chosen edition”, but the present requirement calls for “A test account in the proposed edition exposes all required security controls and the edition contract supports them”: Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
Question 919
A deployment team has configured this Snowflake capability: Apply a tested Snowflake network policy with narrowly scoped allowed IP ranges. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Approved origins connect while an unapproved test origin is denied at the network policy boundary.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
- PUBLIC cannot query restricted fields while approved roles receive only their designated projection.
- Each test role returns expected row counts and masked field values for those rows.
Explanation
Correct Answer
A:Network policies constrain permitted source addresses independently from SQL object grants. The stated acceptance evidence is: Approved origins connect while an unapproved test origin is denied at the network policy boundary. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Query metadata supports operational reporting of status, user, role and execution context. That explains the role of “The report reproduces the seeded failed statement and its assigned warehouse and role”, but the present requirement calls for “Approved origins connect while an unapproved test origin is denied at the network policy boundary”: Network policies constrain permitted source addresses independently from SQL object grants.
C:Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data. That explains the role of “PUBLIC cannot query restricted fields while approved roles receive only their designated projection”, but the present requirement calls for “Approved origins connect while an unapproved test origin is denied at the network policy boundary”: Network policies constrain permitted source addresses independently from SQL object grants.
D:Row access governs record visibility while masking governs values in visible rows, so they must be tested separately. That explains the role of “Each test role returns expected row counts and masked field values for those rows”, but the present requirement calls for “Approved origins connect while an unapproved test origin is denied at the network policy boundary”: Network policies constrain permitted source addresses independently from SQL object grants.
Question 920
A deployment team has configured this Snowflake capability: Use LIST on the intended stage and file path with appropriate privileges. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Task history shows scheduled executions and expected output table updates.
- SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run.
- The output includes the expected files and excludes unrelated prefix paths.
- The corrected connector establishes a session and executes a minimal authorized query.
Explanation
Correct Answer
C:Listing stage contents validates location, pattern and access independently of a COPY operation. The stated acceptance evidence is: The output includes the expected files and excludes unrelated prefix paths. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. That explains the role of “Task history shows scheduled executions and expected output table updates”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.
B:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. That explains the role of “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.
D:Client authentication and session authorization failures are unrelated to warehouse processing capacity. That explains the role of “The corrected connector establishes a session and executes a minimal authorized query”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.