SnowPro Core COF-C03 Practice Test 52
Question 510
During a pilot, engineers pursued an unrelated workaround: Grant the necessary ancestor object USAGE privileges to the intended role. The required outcome remained unsatisfied: A connector breaks when its user default warehouse is dropped but its SELECT grants remain valid. Which correction should the team prioritize?
- Enforce the supported MFA and authentication policy for the target user population.
- Revoke their assigned access roles or object grants through the controlled role hierarchy.
- Assign an available warehouse with USAGE to the connecting role and update the client context.
- Grant the necessary ancestor object USAGE privileges to the intended role.
Explanation
Correct Answer
C:SQL execution requires an accessible running or resumable warehouse, separate from table read rights. The corrective step addresses the missing requirement: A connector breaks when its user default warehouse is dropped but its SELECT grants remain valid. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:MFA raises assurance beyond a single compromised password or reused secret. That explains the role of “Enforce the supported MFA and authentication policy for the target user population”, but the present requirement calls for “Assign an available warehouse with USAGE to the connecting role and update the client context”: SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
B:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “Revoke their assigned access roles or object grants through the controlled role hierarchy”, but the present requirement calls for “Assign an available warehouse with USAGE to the connecting role and update the client context”: SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
D:Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights. That explains the role of “Grant the necessary ancestor object USAGE privileges to the intended role”, but the present requirement calls for “Assign an available warehouse with USAGE to the connecting role and update the client context”: SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
Question 511
During a pilot, engineers pursued an unrelated workaround: Use a supported Snowflake storage integration for delegated cloud storage access. The required outcome remained unsatisfied: A nightly export must place only approved columns of a sensitive table into a partner's storage area. Which correction should the team prioritize?
- Configure the CSV file format with the correct delimiter and enclosure options.
- Use a supported Snowflake storage integration for delegated cloud storage access.
- Use COPY INTO an external stage location with an approved file format and storage integration.
- Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants.
Explanation
Correct Answer
D:Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table. The corrective step addresses the missing requirement: A nightly export must place only approved columns of a sensitive table into a partner's storage area. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:File-format parsing rules must match real source encoding and quote conventions. That explains the role of “Configure the CSV file format with the correct delimiter and enclosure options”, but the present requirement calls for “Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
B:Storage integrations manage cloud authentication using controlled trust and permission assignments. That explains the role of “Use a supported Snowflake storage integration for delegated cloud storage access”, but the present requirement calls for “Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
C:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. That explains the role of “Use COPY INTO an external stage location with an approved file format and storage integration”, but the present requirement calls for “Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
Question 512
During a pilot, engineers pursued an unrelated workaround: Separate the interactive and transformation workloads into different warehouses. The required outcome remained unsatisfied: An administrator wants to use an aggressive latency-oriented scale-out policy for urgent interactive reports. Which correction should the team prioritize?
- Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing.
- Benchmark a smaller warehouse with representative query sizes and verify service-level objectives.
- Separate the interactive and transformation workloads into different warehouses.
- Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME.
Explanation
Correct Answer
A:STANDARD favors starting additional clusters to minimize query queuing as demand grows. The corrective step addresses the missing requirement: An administrator wants to use an aggressive latency-oriented scale-out policy for urgent interactive reports. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence. That explains the role of “Benchmark a smaller warehouse with representative query sizes and verify service-level objectives”, but the present requirement calls for “Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
C:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Separate the interactive and transformation workloads into different warehouses”, but the present requirement calls for “Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
D:Suspension releases active compute after an idle period rather than relying on staff to stop it. That explains the role of “Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME”, but the present requirement calls for “Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
Question 513
During a pilot, engineers pursued an unrelated workaround: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. The required outcome remained unsatisfied: A data exchange platform needs to offer separate products to departments without creating one shared account-wide PUBLIC data grant. Which correction should the team prioritize?
- Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
- Remove that consumer from the authorized share or revoke the relevant shared object grants.
- Use separate secured listings or shares with scoped recipients and approved views.
- Plan supported cross-region sharing or listing and replication arrangements as required.
Explanation
Correct Answer
C:Individual product authorization reduces inadvertent cross-tenant data access. The corrective step addresses the missing requirement: A data exchange platform needs to offer separate products to departments without creating one shared account-wide PUBLIC data grant. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model. That explains the role of “Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options”, but the present requirement calls for “Use separate secured listings or shares with scoped recipients and approved views”: Individual product authorization reduces inadvertent cross-tenant data access.
B:Provider-owned grants control consumer access independently of data persistence. That explains the role of “Remove that consumer from the authorized share or revoke the relevant shared object grants”, but the present requirement calls for “Use separate secured listings or shares with scoped recipients and approved views”: Individual product authorization reduces inadvertent cross-tenant data access.
D:Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly. That explains the role of “Plan supported cross-region sharing or listing and replication arrangements as required”, but the present requirement calls for “Use separate secured listings or shares with scoped recipients and approved views”: Individual product authorization reduces inadvertent cross-tenant data access.
Question 514
During a pilot, engineers pursued an unrelated workaround: Investigate authentication and authorization in the cloud services control path and the selected role. The required outcome remained unsatisfied: An ingestion team needs to explain whether metadata management is the responsibility of individual virtual warehouse nodes. Which correction should the team prioritize?
- Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work.
- Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
- Investigate authentication and authorization in the cloud services control path and the selected role.
- Identify managed database storage as the persistence layer for compressed columnar table data.
Explanation
Correct Answer
A:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. The corrective step addresses the missing requirement: An ingestion team needs to explain whether metadata management is the responsibility of individual virtual warehouse nodes. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data. That explains the role of “Allocate distinct warehouses to the jobs and use the same authorized database storage objects”, but the present requirement calls for “Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
C:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. That explains the role of “Investigate authentication and authorization in the cloud services control path and the selected role”, but the present requirement calls for “Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
D:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. That explains the role of “Identify managed database storage as the persistence layer for compressed columnar table data”, but the present requirement calls for “Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
Question 515
During a pilot, engineers pursued an unrelated workaround: Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely. The required outcome remained unsatisfied: Several contractors should lose access to a shared dataset at contract end without changing the table contents. Which correction should the team prioritize?
- Revoke their assigned access roles or object grants through the controlled role hierarchy.
- Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely.
- Use user-management privileges or the appropriate system administration role without broad data grants.
- Inspect Snowflake access and query history using properly privileged monitoring views.
Explanation
Correct Answer
A:Authorization revocation separates identity lifecycle from destructive changes to stored data. The corrective step addresses the missing requirement: Several contractors should lose access to a shared dataset at contract end without changing the table contents. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. That explains the role of “Configure Snowflake-supported key-pair or approved token authentication and rotate credentials securely”, but the present requirement calls for “Revoke their assigned access roles or object grants through the controlled role hierarchy”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
C:Managing identities and accessing all customer tables are distinct authorization duties. That explains the role of “Use user-management privileges or the appropriate system administration role without broad data grants”, but the present requirement calls for “Revoke their assigned access roles or object grants through the controlled role hierarchy”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
D:Account activity history connects query operations to principals and execution context for investigation. That explains the role of “Inspect Snowflake access and query history using properly privileged monitoring views”, but the present requirement calls for “Revoke their assigned access roles or object grants through the controlled role hierarchy”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
Question 516
During a pilot, engineers pursued an unrelated workaround: Consume the stream with a committed downstream DML transaction. The required outcome remained unsatisfied: A partner uploads new small files throughout the hour and the team wants serverless ingestion without scheduling warehouse-based batch jobs. Which correction should the team prioritize?
- Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps.
- Define an auto-ingest Snowpipe with a stage and supported cloud event notifications.
- Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table.
- Consume the stream with a committed downstream DML transaction.
Explanation
Correct Answer
B:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. The corrective step addresses the missing requirement: A partner uploads new small files throughout the hour and the team wants serverless ingestion without scheduling warehouse-based batch jobs. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. That explains the role of “Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps”, but the present requirement calls for “Define an auto-ingest Snowpipe with a stage and supported cloud event notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
C:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table”, but the present requirement calls for “Define an auto-ingest Snowpipe with a stage and supported cloud event notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
D:A stream offset advances when its changes are consumed by a committed transactional operation. That explains the role of “Consume the stream with a committed downstream DML transaction”, but the present requirement calls for “Define an auto-ingest Snowpipe with a stage and supported cloud event notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
Question 517
During a pilot, engineers pursued an unrelated workaround: Separate the interactive and transformation workloads into different warehouses. The required outcome remained unsatisfied: A noninteractive batch reporting warehouse should conserve credits even if some queries wait briefly. Which correction should the team prioritize?
- Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits.
- Enable AUTO_RESUME after verifying user role USAGE and operational expectations.
- Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands.
- Separate the interactive and transformation workloads into different warehouses.
Explanation
Correct Answer
A:ECONOMY prioritizes fuller use of existing clusters before starting more compute. The corrective step addresses the missing requirement: A noninteractive batch reporting warehouse should conserve credits even if some queries wait briefly. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
B:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. That explains the role of “Enable AUTO_RESUME after verifying user role USAGE and operational expectations”, but the present requirement calls for “Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
C:A specialized warehouse might provide better memory characteristics for supported Snowpark jobs. That explains the role of “Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands”, but the present requirement calls for “Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
D:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Separate the interactive and transformation workloads into different warehouses”, but the present requirement calls for “Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
Question 518
During a pilot, engineers pursued an unrelated workaround: Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls. The required outcome remained unsatisfied: A development team needs a quick independent sandbox copy of a production database with minimal initial duplicate storage. Which correction should the team prioritize?
- Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window.
- Create a supported zero-copy clone of the database.
- Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls.
- Configure eligible extended Time Travel retention up to the edition's supported maximum.
Explanation
Correct Answer
B:Cloning initially shares immutable micro-partitions and forks logically when later writes change data. The corrective step addresses the missing requirement: A development team needs a quick independent sandbox copy of a production database with minimal initial duplicate storage. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Time Travel supports restoration of recently dropped eligible objects while their retention remains valid. That explains the role of “Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window”, but the present requirement calls for “Create a supported zero-copy clone of the database”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
C:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. That explains the role of “Evaluate a Snowflake Data Clean Room with approved analysis templates and privacy controls”, but the present requirement calls for “Create a supported zero-copy clone of the database”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
D:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. That explains the role of “Configure eligible extended Time Travel retention up to the edition's supported maximum”, but the present requirement calls for “Create a supported zero-copy clone of the database”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
Question 519
During a pilot, engineers pursued an unrelated workaround: Explain that suspending compute does not delete persisted Snowflake table data. The required outcome remained unsatisfied: A Snowflake user wants both high compute isolation and a single consistent dataset across a machine-learning job and reporting app. Which correction should the team prioritize?
- Verify the active database and schema context used for unqualified object references.
- Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage.
- Allocate distinct warehouses to the jobs and use the same authorized database storage objects.
- Explain that suspending compute does not delete persisted Snowflake table data.
Explanation
Correct Answer
C:Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data. The corrective step addresses the missing requirement: A Snowflake user wants both high compute isolation and a single consistent dataset across a machine-learning job and reporting app. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions. That explains the role of “Verify the active database and schema context used for unqualified object references”, but the present requirement calls for “Allocate distinct warehouses to the jobs and use the same authorized database storage objects”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
B:Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution. That explains the role of “Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage”, but the present requirement calls for “Allocate distinct warehouses to the jobs and use the same authorized database storage objects”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
D:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “Explain that suspending compute does not delete persisted Snowflake table data”, but the present requirement calls for “Allocate distinct warehouses to the jobs and use the same authorized database storage objects”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
Question 520
During a pilot, engineers pursued an unrelated workaround: Retain masking enforcement on underlying governed columns and test effective role conditions. The required outcome remained unsatisfied: A customer-support table has salary columns that should appear redacted for non-HR roles without hiding all rows. Which correction should the team prioritize?
- Apply a row access policy that filters rows based on authorized role or mapping context.
- Retain masking enforcement on underlying governed columns and test effective role conditions.
- Attach an appropriate dynamic data masking policy to protected columns.
- Use object tagging and catalog metadata to track data classification and responsible owners.
Explanation
Correct Answer
C:Masking policies condition returned column values based on authorized execution context. The corrective step addresses the missing requirement: A customer-support table has salary columns that should appear redacted for non-HR roles without hiding all rows. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Apply a row access policy that filters rows based on authorized role or mapping context”, but the present requirement calls for “Attach an appropriate dynamic data masking policy to protected columns”: Masking policies condition returned column values based on authorized execution context.
B:A view does not automatically remove column-level policy obligations inherited from its sources. That explains the role of “Retain masking enforcement on underlying governed columns and test effective role conditions”, but the present requirement calls for “Attach an appropriate dynamic data masking policy to protected columns”: Masking policies condition returned column values based on authorized execution context.
D:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. That explains the role of “Use object tagging and catalog metadata to track data classification and responsible owners”, but the present requirement calls for “Attach an appropriate dynamic data masking policy to protected columns”: Masking policies condition returned column values based on authorized execution context.