SnowPro Core COF-C03 Practice Test 91
Question 900
A deployment team has configured this Snowflake capability: Use COPY INTO an external stage location with an approved file format and storage integration. 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.
- End-to-end test rows become queryable at the required latency without staging files.
- The scheduled report completes and query history records the intended warehouse context.
- The expected files appear in the authorized cloud path and their content matches the query result.
Explanation
Correct Answer
D:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. The stated acceptance evidence is: The expected files appear in the authorized cloud path and their content matches the query result. 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 “The expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
B: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 expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
C:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. That explains the role of “The scheduled report completes and query history records the intended warehouse context”, but the present requirement calls for “The expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
Question 901
A deployment team has configured this Snowflake capability: Inspect Snowflake persisted query result reuse and conditions that invalidate it. 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 generated columns match the documented category set and totals reconcile.
- The output preserves rows and assigns expected ranks for tied sales totals.
- A seeded unknown status receives the fallback label and known codes map correctly.
- Query history shows eligible result reuse and fast execution while changed inputs prevent stale results.
Explanation
Correct Answer
D:Result caching can return compatible prior query results without reexecuting a full warehouse scan. The stated acceptance evidence is: Query history shows eligible result reuse and fast execution while changed inputs prevent stale results. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output. That explains the role of “The generated columns match the documented category set and totals reconcile”, but the present requirement calls for “Query history shows eligible result reuse and fast execution while changed inputs prevent stale results”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
B:Window functions compute rankings across a partition while retaining the underlying row granularity. That explains the role of “The output preserves rows and assigns expected ranks for tied sales totals”, but the present requirement calls for “Query history shows eligible result reuse and fast execution while changed inputs prevent stale results”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
C:CASE supplies conditional SQL expressions suited to bounded mappings, including defaults. That explains the role of “A seeded unknown status receives the fallback label and known codes map correctly”, but the present requirement calls for “Query history shows eligible result reuse and fast execution while changed inputs prevent stale results”: Result caching can return compatible prior query results without reexecuting a full warehouse scan.
Question 902
A deployment team has configured this Snowflake capability: Use a transient table only after approving its limited data-recovery guarantees. 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?
- Replication history shows a successful refresh and controlled failover testing meets recovery targets.
- Object metadata reflects transient type and the retention policy matches the accepted operational risk.
- The consumer queries only the approved projection and cannot read the underlying protected table.
- A disaster-recovery drill can access the replicated secondary account after loss of the primary region.
Explanation
Correct Answer
B:Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics. The stated acceptance evidence is: Object metadata reflects transient type and the retention policy matches the accepted operational risk. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features. That explains the role of “Replication history shows a successful refresh and controlled failover testing meets recovery targets”, but the present requirement calls for “Object metadata reflects transient type and the retention policy matches the accepted operational risk”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
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 “Object metadata reflects transient type and the retention policy matches the accepted operational risk”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
D: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 “Object metadata reflects transient type and the retention policy matches the accepted operational risk”: Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
Question 903
A deployment team has configured this Snowflake capability: Combine Snowflake SQL with supported Snowpark and native application development capabilities. 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 profile displays a reduced count of scanned partitions for the selective filter.
- Queued overload time drops as demand spreads across active clusters.
- Authorized roles see only expected columns and unauthorized roles are denied source access.
- A supported Snowpark job executes against authorized tables without first exporting unrestricted source data.
Explanation
Correct Answer
D:Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces. The stated acceptance evidence is: A supported Snowpark job executes against authorized tables without first exporting unrestricted source data. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans. That explains the role of “The profile displays a reduced count of scanned partitions for the selective filter”, but the present requirement calls for “A supported Snowpark job executes against authorized tables without first exporting unrestricted source data”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
B:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Queued overload time drops as demand spreads across active clusters”, but the present requirement calls for “A supported Snowpark job executes against authorized tables without first exporting unrestricted source data”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
C:Views define reusable query projections; they are different from full materialized table copies. That explains the role of “Authorized roles see only expected columns and unauthorized roles are denied source access”, but the present requirement calls for “A supported Snowpark job executes against authorized tables without first exporting unrestricted source data”: Snowflake executes SQL and supported application code close to governed data through its managed compute and developer interfaces.
Question 904
A deployment team has configured this Snowflake capability: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. 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 job authenticates with the approved identity and source repositories contain no static password.
- Only the governance role can alter a test masking policy; reader roles cannot.
- Two test roles return different permitted row sets from the identical table.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
Explanation
Correct Answer
A:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. The stated acceptance evidence is: The job authenticates with the approved identity and source repositories contain no static password. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. That explains the role of “Only the governance role can alter a test masking policy; reader roles cannot”, but the present requirement calls for “The job authenticates with the approved identity and source repositories contain no static password”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
C:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Two test roles return different permitted row sets from the identical table”, but the present requirement calls for “The job authenticates with the approved identity and source repositories contain no static password”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
D: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 “The job authenticates with the approved identity and source repositories contain no static password”: Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle.
Question 905
A deployment team has configured this Snowflake capability: Use COPY INTO table with an appropriate VALIDATION_MODE for supported bulk load cases. 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?
- Measured data age is checked against the target rather than assuming fixed refresh timestamps.
- The scheduled report completes and query history records the intended warehouse context.
- The validation run identifies malformed records and the target row count remains unchanged.
- DNS resolution and observed routes demonstrate private endpoint usage for the production connector.
Explanation
Correct Answer
C:Bulk copy validation checks how staged rows would parse without treating the test as a production load. The stated acceptance evidence is: The validation run identifies malformed records and the target row count remains unchanged. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. That explains the role of “Measured data age is checked against the target rather than assuming fixed refresh timestamps”, but the present requirement calls for “The validation run identifies malformed records and the target row count remains unchanged”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
B:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. That explains the role of “The scheduled report completes and query history records the intended warehouse context”, but the present requirement calls for “The validation run identifies malformed records and the target row count remains unchanged”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
D:Private network access relies on cloud routing and DNS as well as Snowflake account policies. That explains the role of “DNS resolution and observed routes demonstrate private endpoint usage for the production connector”, but the present requirement calls for “The validation run identifies malformed records and the target row count remains unchanged”: Bulk copy validation checks how staged rows would parse without treating the test as a production load.
Question 906
A deployment team has configured this Snowflake capability: Investigate local warehouse cache warm-up before attributing the slowdown solely to query text. 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 smaller warehouse meets the same reporting targets with fewer credits consumed.
- Repeated controlled runs on active compute show different cache behavior from a cold restart.
- The normalized query processes strings, numbers and arrays according to tested rules.
- Load tests show interactive latency is stable during the transformation run.
Explanation
Correct Answer
B:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. The stated acceptance evidence is: Repeated controlled runs on active compute show different cache behavior from a cold restart. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence. That explains the role of “The smaller warehouse meets the same reporting targets with fewer credits consumed”, but the present requirement calls for “Repeated controlled runs on active compute show different cache behavior from a cold restart”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
C:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. That explains the role of “The normalized query processes strings, numbers and arrays according to tested rules”, but the present requirement calls for “Repeated controlled runs on active compute show different cache behavior from a cold restart”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
D:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Load tests show interactive latency is stable during the transformation run”, but the present requirement calls for “Repeated controlled runs on active compute show different cache behavior from a cold restart”: Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching.
Question 907
A deployment team has configured this Snowflake capability: Configure eligible extended Time Travel retention up to the edition's supported maximum. 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 table parameter displays the approved retention period and a historical test query succeeds.
- A consumer refreshes the imported share and can SELECT the newly granted secure view.
- Each test recipient sees only the listing or share explicitly assigned to it.
- A test consumer in the destination region can access the approved replicated or distributed product.
Explanation
Correct Answer
A:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. The stated acceptance evidence is: The table parameter displays the approved retention period and a historical test query succeeds. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Cross-account access requires the provider to grant the intended objects and containing namespace appropriately. That explains the role of “A consumer refreshes the imported share and can SELECT the newly granted secure view”, but the present requirement calls for “The table parameter displays the approved retention period and a historical test query succeeds”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
C:Individual product authorization reduces inadvertent cross-tenant data access. That explains the role of “Each test recipient sees only the listing or share explicitly assigned to it”, but the present requirement calls for “The table parameter displays the approved retention period and a historical test query succeeds”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
D:Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly. That explains the role of “A test consumer in the destination region can access the approved replicated or distributed product”, but the present requirement calls for “The table parameter displays the approved retention period and a historical test query succeeds”: Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs.
Question 908
A deployment team has configured this Snowflake capability: Correct the design to use independent warehouses reading shared Snowflake tables. 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 corrected approved identity and network policy allows a session to establish before a query runs.
- The processing job meets its memory and runtime targets without unacceptable compute cost.
- The JSON path expressions return expected nested fields and data types.
- The workload runs on distinct warehouses while both resolve the same fully qualified table identifier.
Explanation
Correct Answer
D:Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table. The stated acceptance evidence is: The workload runs on distinct warehouses while both resolve the same fully qualified table identifier. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity. That explains the role of “A corrected approved identity and network policy allows a session to establish before a query runs”, but the present requirement calls for “The workload runs on distinct warehouses while both resolve the same fully qualified table identifier”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
B:Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries. That explains the role of “The processing job meets its memory and runtime targets without unacceptable compute cost”, but the present requirement calls for “The workload runs on distinct warehouses while both resolve the same fully qualified table identifier”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
C:VARIANT holds flexible structured values without forcing one rigid input schema for every record. That explains the role of “The JSON path expressions return expected nested fields and data types”, but the present requirement calls for “The workload runs on distinct warehouses while both resolve the same fully qualified table identifier”: Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
Question 909
A deployment team has configured this Snowflake capability: Configure supported federated single sign-on with the organization's identity provider. 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?
- Storage reporting isolates active data from retained history and shows the trend after policy changes.
- A support role sees the approved masked prefix and a privileged role sees the full value.
- A direct SELECT under the restricted role still returns only authorized departments.
- The employee signs in through the expected IdP and disabled IdP identities no longer establish access.
Explanation
Correct Answer
D:Federated SSO centralizes login assurance and deprovisioning for interactive employees. The stated acceptance evidence is: The employee signs in through the expected IdP and disabled IdP identities no longer establish access. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.
B:Column masking can transform visible values for less-privileged roles without changing stored source values. That explains the role of “A support role sees the approved masked prefix and a privileged role sees the full value”, but the present requirement calls for “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.
C:Application-level filtering is not a reliable security boundary for users with direct query access. That explains the role of “A direct SELECT under the restricted role still returns only authorized departments”, but the present requirement calls for “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”: Federated SSO centralizes login assurance and deprovisioning for interactive employees.
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.