SnowPro Core COF-C03 Practice Test 50
Question 490
An architecture reviewer proposes the following solution: Correct the design to use independent warehouses reading shared Snowflake tables. The business and technical requirement is: An executive assumes copying the same table into separate warehouses is necessary to isolate dashboards from transformations. Which explanation most accurately justifies this choice?
- Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions.
- IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
- Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table.
- Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
Explanation
Correct Answer
C:Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table. This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Package a supported Snowpark UDF with the correct runtime and package permissions. That explains the role of “Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions”, but the present requirement calls for “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.
B:This mechanism explains why the proposed action fits the scenario: Use a supported VS Code Snowflake extension or integration with repository version control. That explains the role of “IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges”, but the present requirement calls for “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.
D:This mechanism explains why the proposed action fits the scenario: Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs. That explains the role of “Interactive and automated interfaces suit different workflows but share Snowflake's security and object model”, but the present requirement calls for “Warehouse separation is a compute isolation strategy, not a requirement to duplicate each underlying table”: This mechanism explains why the proposed action fits the scenario: Correct the design to use independent warehouses reading shared Snowflake tables.
Question 491
An architecture reviewer proposes the following solution: Configure supported federated single sign-on with the organization's identity provider. The business and technical requirement is: A company already uses enterprise identity federation and wants employee Snowflake sign-ins tied to its central identity provider. Which explanation most accurately justifies this choice?
- Federated SSO centralizes login assurance and deprovisioning for interactive employees.
- Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
- Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
- Access history exposes which objects or columns were referenced, supporting data governance investigation.
Explanation
Correct Answer
A:Federated SSO centralizes login assurance and deprovisioning for interactive employees. This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Evaluate hourly credit usage across all warehouses and Snowflake-managed services. That explains the role of “Current warehouse size alone omits runtime, concurrency, and independent serverless consumption”, but the present requirement calls for “Federated SSO centralizes login assurance and deprovisioning for interactive employees”: This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider.
C:This mechanism explains why the proposed action fits the scenario: Evaluate row access filtering and column masking independently with representative roles. That explains the role of “Row access governs record visibility while masking governs values in visible rows, so they must be tested separately”, but the present requirement calls for “Federated SSO centralizes login assurance and deprovisioning for interactive employees”: This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider.
D:This mechanism explains why the proposed action fits the scenario: Use Snowflake-supported access history with an authorized investigation role. That explains the role of “Access history exposes which objects or columns were referenced, supporting data governance investigation”, but the present requirement calls for “Federated SSO centralizes login assurance and deprovisioning for interactive employees”: This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider.
Question 492
An architecture reviewer proposes the following solution: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results. The business and technical requirement is: A batch load should continue with valid files while collecting rejected-row details under an agreed error policy. Which explanation most accurately justifies this choice?
- Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
- COPY loading error behavior is configurable; silent skipping without review can hide data loss.
- Private network access relies on cloud routing and DNS as well as Snowflake account policies.
- DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
Explanation
Correct Answer
B:COPY loading error behavior is configurable; silent skipping without review can hide data loss. This mechanism explains why the proposed action fits the scenario: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create a Snowflake task with an appropriate schedule and execution context. That explains the role of “Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary”, but the present requirement calls for “COPY loading error behavior is configurable; silent skipping without review can hide data loss”: This mechanism explains why the proposed action fits the scenario: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results.
C:This mechanism explains why the proposed action fits the scenario: Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint. That explains the role of “Private network access relies on cloud routing and DNS as well as Snowflake account policies”, but the present requirement calls for “COPY loading error behavior is configurable; silent skipping without review can hide data loss”: This mechanism explains why the proposed action fits the scenario: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results.
D:This mechanism explains why the proposed action fits the scenario: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. That explains the role of “DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer”, but the present requirement calls for “COPY loading error behavior is configurable; silent skipping without review can hide data loss”: This mechanism explains why the proposed action fits the scenario: Choose an appropriate COPY INTO ON_ERROR setting and inspect load results.
Question 493
An architecture reviewer proposes the following solution: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy. The business and technical requirement is: An ETL query spills gigabytes to remote storage during a hash join. Which explanation most accurately justifies this choice?
- Large intermediate joins that exceed memory can create costly remote spill and longer runtimes.
- CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
- A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
- Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
Explanation
Correct Answer
A:Large intermediate joins that exceed memory can create costly remote spill and longer runtimes. This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values. That explains the role of “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”, but the present requirement calls for “Large intermediate joins that exceed memory can create costly remote spill and longer runtimes”: This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy.
C:This mechanism explains why the proposed action fits the scenario: Enable AUTO_RESUME after verifying user role USAGE and operational expectations. That explains the role of “A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it”, but the present requirement calls for “Large intermediate joins that exceed memory can create costly remote spill and longer runtimes”: This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy.
D:This mechanism explains why the proposed action fits the scenario: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules. That explains the role of “Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved”, but the present requirement calls for “Large intermediate joins that exceed memory can create costly remote spill and longer runtimes”: This mechanism explains why the proposed action fits the scenario: Inspect Query Profile spill indicators and evaluate warehouse memory or SQL join strategy.
Question 494
An architecture reviewer proposes the following solution: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported. The business and technical requirement is: An application should retrieve the historical state from a particular Snowflake statement instead of estimating wall-clock seconds. Which explanation most accurately justifies this choice?
- Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
- Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model.
- Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
- Statement-based history offers precise temporal reference points for eligible Snowflake objects.
Explanation
Correct Answer
D:Statement-based history offers precise temporal reference points for eligible Snowflake objects. This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Expose a governed secure view through a direct share rather than granting raw base-table access. That explains the role of “Secure views can project approved data to recipients while protecting provider-owned source logic and columns”, but the present requirement calls for “Statement-based history offers precise temporal reference points for eligible Snowflake objects”: This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported.
B:This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. That explains the role of “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”, but the present requirement calls for “Statement-based history offers precise temporal reference points for eligible Snowflake objects”: This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported.
C:This mechanism explains why the proposed action fits the scenario: Create a supported zero-copy clone of the database. That explains the role of “Cloning initially shares immutable micro-partitions and forks logically when later writes change data”, but the present requirement calls for “Statement-based history offers precise temporal reference points for eligible Snowflake objects”: This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported.
Question 495
An architecture reviewer proposes the following solution: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets. The business and technical requirement is: A new analytics project needs scalable ingestion, SQL transformation and reporting with consistently enforced access restrictions. Which explanation most accurately justifies this choice?
- The platform combines managed storage and compute with authentication and object privileges across its data lifecycle.
- CLI workflows allow controlled automation and environment selection without fragile UI clicking.
- Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists.
- Cortex functions can perform language processing close to Snowflake data subject to availability and policy.
Explanation
Correct Answer
A:The platform combines managed storage and compute with authentication and object privileges across its data lifecycle. This mechanism explains why the proposed action fits the scenario: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake CLI and authenticated configuration for scripted deployment. That explains the role of “CLI workflows allow controlled automation and environment selection without fragile UI clicking”, but the present requirement calls for “The platform combines managed storage and compute with authentication and object privileges across its data lifecycle”: This mechanism explains why the proposed action fits the scenario: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets.
C:This mechanism explains why the proposed action fits the scenario: Select an edition that explicitly includes the required enterprise security or governance capabilities. That explains the role of “Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists”, but the present requirement calls for “The platform combines managed storage and compute with authentication and object privileges across its data lifecycle”: This mechanism explains why the proposed action fits the scenario: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake Cortex AI SQL functions under approved data security controls. That explains the role of “Cortex functions can perform language processing close to Snowflake data subject to availability and policy”, but the present requirement calls for “The platform combines managed storage and compute with authentication and object privileges across its data lifecycle”: This mechanism explains why the proposed action fits the scenario: Design one Snowflake platform workflow with staged ingestion, transform compute, and role-governed datasets.
Question 496
An architecture reviewer proposes the following solution: Enforce the supported MFA and authentication policy for the target user population. The business and technical requirement is: Security wants a second authentication factor for interactive account access. Which explanation most accurately justifies this choice?
- Some Snowflake services use serverless credits independently of warehouse runtime.
- MFA raises assurance beyond a single compromised password or reused secret.
- Automated or assisted classification helps discover and manage sensitive data across a large catalog.
- Data-level controls travel with queries across clients and minimize inconsistent authorization behavior.
Explanation
Correct Answer
B:MFA raises assurance beyond a single compromised password or reused secret. This mechanism explains why the proposed action fits the scenario: Enforce the supported MFA and authentication policy for the target user population. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Inspect serverless ingestion and task usage independently from user-managed warehouse charges. That explains the role of “Some Snowflake services use serverless credits independently of warehouse runtime”, but the present requirement calls for “MFA raises assurance beyond a single compromised password or reused secret”: This mechanism explains why the proposed action fits the scenario: Enforce the supported MFA and authentication policy for the target user population.
C:This mechanism explains why the proposed action fits the scenario: Use supported data classification and semantic labeling to locate sensitive columns. That explains the role of “Automated or assisted classification helps discover and manage sensitive data across a large catalog”, but the present requirement calls for “MFA raises assurance beyond a single compromised password or reused secret”: This mechanism explains why the proposed action fits the scenario: Enforce the supported MFA and authentication policy for the target user population.
D:This mechanism explains why the proposed action fits the scenario: Attach Snowflake governance policies at the data object instead of implementing separate app-only filters. That explains the role of “Data-level controls travel with queries across clients and minimize inconsistent authorization behavior”, but the present requirement calls for “MFA raises assurance beyond a single compromised password or reused secret”: This mechanism explains why the proposed action fits the scenario: Enforce the supported MFA and authentication policy for the target user population.
Question 497
An architecture reviewer proposes the following solution: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional. The business and technical requirement is: A daily batch rerun reuses the same file names and unexpectedly does not reload previously ingested data. Which explanation most accurately justifies this choice?
- Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
- API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions.
- Client authentication and session authorization failures are unrelated to warehouse processing capacity.
- COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards.
Explanation
Correct Answer
D:COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards. This mechanism explains why the proposed action fits the scenario: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create a Snowflake task with an appropriate schedule and execution context. That explains the role of “Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary”, but the present requirement calls for “COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional.
B:This mechanism explains why the proposed action fits the scenario: Configure a supported API integration with the required external-function security boundary. That explains the role of “API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions”, but the present requirement calls for “COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional.
C:This mechanism explains why the proposed action fits the scenario: Validate connection settings, credential renewal and active role context before resizing compute. That explains the role of “Client authentication and session authorization failures are unrelated to warehouse processing capacity”, but the present requirement calls for “COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards”: This mechanism explains why the proposed action fits the scenario: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional.
Question 498
An architecture reviewer proposes the following solution: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. The business and technical requirement is: A BI warehouse receives hundreds of concurrent short SELECT statements and queue time dominates response latency. Which explanation most accurately justifies this choice?
- Capacity should be evaluated against actual queue time, execution time and consumed credits.
- CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
- LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
- Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources.
Explanation
Correct Answer
D:Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources. This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Compare warehouse load, credits and query profile statistics before and after configuration changes. That explains the role of “Capacity should be evaluated against actual queue time, execution time and consumed credits”, but the present requirement calls for “Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources”: This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
B:This mechanism explains why the proposed action fits the scenario: Use CASE expressions with explicit ELSE handling for unknown values. That explains the role of “CASE supplies conditional SQL expressions suited to bounded mappings, including defaults”, but the present requirement calls for “Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources”: This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
C:This mechanism explains why the proposed action fits the scenario: Use LAG in a partitioned, ordered window expression. That explains the role of “LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset”, but the present requirement calls for “Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources”: This mechanism explains why the proposed action fits the scenario: Scale out with an appropriate multi-cluster warehouse rather than only increasing one cluster's size.
Question 499
An architecture reviewer proposes the following solution: Review the Time Travel and Fail-safe retention windows and storage effects. The business and technical requirement is: An operator assumes deleting a permanent table will instantly remove all stored historical bytes from Snowflake billing. Which explanation most accurately justifies this choice?
- Historical storage can remain recoverable or billable according to the table type and retention rules.
- Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features.
- Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially.
- Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model.
Explanation
Correct Answer
A:Historical storage can remain recoverable or billable according to the table type and retention rules. This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported database replication and failover configuration for the required regions and account editions. That explains the role of “Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features”, but the present requirement calls for “Historical storage can remain recoverable or billable according to the table type and retention rules”: This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects.
C:This mechanism explains why the proposed action fits the scenario: Write to the clone using its own object name and verify copy-on-write isolation. That explains the role of “Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially”, but the present requirement calls for “Historical storage can remain recoverable or billable according to the table type and retention rules”: This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects.
D:This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. That explains the role of “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”, but the present requirement calls for “Historical storage can remain recoverable or billable according to the table type and retention rules”: This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects.
Question 500
An architecture reviewer proposes the following solution: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. The business and technical requirement is: An architect wants an accountable method to compare service editions before promising a regulated data feature to stakeholders. Which explanation most accurately justifies this choice?
- External tables reference data outside Snowflake-managed table storage and require consistent metadata handling.
- Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption.
- Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
- Economy favors better cluster utilization before adding parallel compute capacity.
Explanation
Correct Answer
B:Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption. This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Keep external table storage ownership and refresh metadata responsibilities explicit. That explains the role of “External tables reference data outside Snowflake-managed table storage and require consistent metadata handling”, but the present requirement calls for “Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption”: This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
C:This mechanism explains why the proposed action fits the scenario: Let Snowflake manage storage, compression, and micro-partitions for standard tables. That explains the role of “Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement”, but the present requirement calls for “Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption”: This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.
D:This mechanism explains why the proposed action fits the scenario: Use the ECONOMY scaling policy on the supported auto-scale warehouse. That explains the role of “Economy favors better cluster utilization before adding parallel compute capacity”, but the present requirement calls for “Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption”: This mechanism explains why the proposed action fits the scenario: Check feature availability and compliance requirements against the chosen Snowflake edition and deployment region.