Question 150A provider grants a partner share to a full base table although the contract permits only selected nonidentifying columns. What is the most appropriate Snowflake configuration or data-platform response? Confirm the supported cross-region distribution approach and required replication or listing configuration. Evaluate a supported data clean room design with approved aggregation and query controls. Use an appropriately secured view or designated approved share object with validated consumer visibility. Evaluate Snowflake secure data sharing with scoped database objects and consumer entitlements. ExplanationCorrect Answer C:Use an appropriately secured view or designated approved share object with validated consumer visibility. This directly addresses the scenario: A provider grants a partner share to a full base table although the contract permits only selected nonidentifying columns. Technical basis: Sharing requires intentional exposed object design rather than assuming every table column is contractually safe. Check success by confirming: The consumer can read allowed attributes but receives no protected identifiers. Incorrect Answers A:Data collaboration across locations has explicit service and governance requirements beyond same-region direct shares. That is relevant to a different intervention. For the stated situation, the required action is: Use an appropriately secured view or designated approved share object with validated consumer visibility. The governing reason is: Sharing requires intentional exposed object design rather than assuming every table column is contractually safe. B:Privacy-preserving collaboration can provide controlled joint analysis without unrestricted raw dataset sharing. That is relevant to a different intervention. For the stated situation, the required action is: Use an appropriately secured view or designated approved share object with validated consumer visibility. The governing reason is: Sharing requires intentional exposed object design rather than assuming every table column is contractually safe. D:Secure data sharing can expose provider-governed live data without maintaining duplicate export files. That is relevant to a different intervention. For the stated situation, the required action is: Use an appropriately secured view or designated approved share object with validated consumer visibility. The governing reason is: Sharing requires intentional exposed object design rather than assuming every table column is contractually safe.
Question 151A Spark engineering job queries Snowflake but downloads full tables before applying filters that could be pushed down. An engineer recommends: Configure a supported Spark connector path and evaluate predicate pushdown and partitioning. Which Snowflake architecture or data-governance principle best supports the recommendation? Efficient data federation reduces unnecessary network transfer when transformations can run near the source. Client and driver compatibility is part of secure platform integration, not just server-side SQL privileges. Private connectivity requires aligned name resolution, certificate identity and network paths. Client connector behavior and SQL bind semantics should be validated at integration boundaries. ExplanationCorrect Answer A:Efficient data federation reduces unnecessary network transfer when transformations can run near the source. This supports the stated action: Configure a supported Spark connector path and evaluate predicate pushdown and partitioning. Verification should show: A representative Spark job reads only the selected rows and meets the transfer budget. Incorrect Answers B:Client and driver compatibility is part of secure platform integration, not just server-side SQL privileges. This does not establish the proposed intervention. The governing principle here is: Efficient data federation reduces unnecessary network transfer when transformations can run near the source. Apply it by: Configure a supported Spark connector path and evaluate predicate pushdown and partitioning. C:Private connectivity requires aligned name resolution, certificate identity and network paths. This does not establish the proposed intervention. The governing principle here is: Efficient data federation reduces unnecessary network transfer when transformations can run near the source. Apply it by: Configure a supported Spark connector path and evaluate predicate pushdown and partitioning. D:Client connector behavior and SQL bind semantics should be validated at integration boundaries. This does not establish the proposed intervention. The governing principle here is: Efficient data federation reduces unnecessary network transfer when transformations can run near the source. Apply it by: Configure a supported Spark connector path and evaluate predicate pushdown and partitioning.
Question 152A manager reports falling warehouse charges as proof of an overall cost reduction while serverless task executions have quadrupled. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Cache-contaminated benchmarks can lead to underprovisioned production warehouses. Unattributed shared infrastructure makes cost accountability ineffective. Optimizing latency alone may increase monthly finance costs unexpectedly. Single-category accounting can hide growing pipeline spending. ExplanationCorrect Answer D:Single-category accounting can hide growing pipeline spending. Here the failing condition is: A manager reports falling warehouse charges as proof of an overall cost reduction while serverless task executions have quadrupled. The specific correction is: Review consolidated consumption metrics across compute types and correlate them with project activity. Verify through: Project reporting shows warehouse and serverless charges together for the same period. Incorrect Answers A:Result reuse can return previously computed output without representative warehouse execution work. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Single-category accounting can hide growing pipeline spending. B:Chargeback requires a stable mapping between metered resources and responsible business users. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Single-category accounting can hide growing pipeline spending. C:Faster execution does not automatically mean lower cost when resource size increases. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Single-category accounting can hide growing pipeline spending.
Question 153A dashboard frequently times out, but the application records only wall-clock response and no Snowflake query IDs. An engineer recommends: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. Which Snowflake architecture or data-governance principle best supports the recommendation? Oversized intermediate results and spilling can dominate runtime independently of final row count. Query performance investigations need correlated execution evidence rather than client duration alone. Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. Selective point lookup patterns need an appropriate access path or pruning strategy, not just more compute. ExplanationCorrect Answer B:Query performance investigations need correlated execution evidence rather than client duration alone. This supports the stated action: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. Verification should show: A slow request is linked to its query history and the actual wait category is identified. Incorrect Answers A:Oversized intermediate results and spilling can dominate runtime independently of final row count. This does not establish the proposed intervention. The governing principle here is: Query performance investigations need correlated execution evidence rather than client duration alone. Apply it by: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. C:Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. This does not establish the proposed intervention. The governing principle here is: Query performance investigations need correlated execution evidence rather than client duration alone. Apply it by: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. D:Selective point lookup patterns need an appropriate access path or pruning strategy, not just more compute. This does not establish the proposed intervention. The governing principle here is: Query performance investigations need correlated execution evidence rather than client duration alone. Apply it by: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time.
Question 154A streaming app groups tiny daily files into a single huge compressed payload and its COPY job has poor parallelism. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Stale source selection can cause reports to lag behind actual transactions. Unreviewed file layout can break partner ingestion or create expensive serialization bottlenecks. Oversized or poorly distributed files can delay ingestion deadlines. An invalid stage reference leaves daily sales data missing from reports. ExplanationCorrect Answer C:Oversized or poorly distributed files can delay ingestion deadlines. Here the failing condition is: A streaming app groups tiny daily files into a single huge compressed payload and its COPY job has poor parallelism. The specific correction is: Benchmark supported file size and compression choices with practical stage and warehouse parallelism. Verify through: An optimized representative file set loads inside the window with stable row reconciliation. Incorrect Answers A:Source-file identity and stable load checkpoints matter for trustworthy batch ingestion. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Oversized or poorly distributed files can delay ingestion deadlines. B:Unload file partitioning and size settings affect processing efficiency and delivery compatibility. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Oversized or poorly distributed files can delay ingestion deadlines. D:Snowflake bulk loading reads data through defined stages with configured cloud storage access. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Oversized or poorly distributed files can delay ingestion deadlines.
Question 155A large audit table is mostly queried for one transaction ID at a time but business analysts have enabled only a broad date clustering key. An engineer recommends: Benchmark Search Optimization Service or another supported selective lookup approach for the transaction ID workload. Which Snowflake architecture or data-governance principle best supports the recommendation? Micro-partition organization can improve pruning for selective repeated filters at sufficient table scale. Point-selective search access has different strengths from clustering by common range filters. Transformation shape and refresh semantics determine which materialization object can implement a pipeline. Different performance services target different patterns and must be selected by actual bottleneck. ExplanationCorrect Answer B:Point-selective search access has different strengths from clustering by common range filters. This supports the stated action: Benchmark Search Optimization Service or another supported selective lookup approach for the transaction ID workload. Verification should show: Transaction lookup latency improves without imposing unnecessary clustering maintenance on every column. Incorrect Answers A:Micro-partition organization can improve pruning for selective repeated filters at sufficient table scale. This does not establish the proposed intervention. The governing principle here is: Point-selective search access has different strengths from clustering by common range filters. Apply it by: Benchmark Search Optimization Service or another supported selective lookup approach for the transaction ID workload. C:Transformation shape and refresh semantics determine which materialization object can implement a pipeline. This does not establish the proposed intervention. The governing principle here is: Point-selective search access has different strengths from clustering by common range filters. Apply it by: Benchmark Search Optimization Service or another supported selective lookup approach for the transaction ID workload. D:Different performance services target different patterns and must be selected by actual bottleneck. This does not establish the proposed intervention. The governing principle here is: Point-selective search access has different strengths from clustering by common range filters. Apply it by: Benchmark Search Optimization Service or another supported selective lookup approach for the transaction ID workload.
Question 156A marketing analyst filters a shared view to infer hidden customer IDs through unauthorized projection of protected join keys. What is the most appropriate Snowflake configuration or data-platform response? Attach an approved dynamic data masking policy to the sensitive column with role-based outcomes. Define a supported row access policy that enforces authorized regions at the data boundary. Evaluate role precedence and allowed row combinations with representative overlapping grant tests. Evaluate projection and join policy controls for the sensitive dataset where supported. ExplanationCorrect Answer D:Evaluate projection and join policy controls for the sensitive dataset where supported. This directly addresses the scenario: A marketing analyst filters a shared view to infer hidden customer IDs through unauthorized projection of protected join keys. Technical basis: Column exposure and join behavior may need controls beyond simple role grants and row filters. Check success by confirming: A controlled query uses an allowed aggregate join while prohibited key projection is denied. Incorrect Answers A:Masking policies can control query-time exposure of protected values without duplicating source tables. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate projection and join policy controls for the sensitive dataset where supported. The governing reason is: Column exposure and join behavior may need controls beyond simple role grants and row filters. B:Row access policies constrain visible rows independently of client application filters. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate projection and join policy controls for the sensitive dataset where supported. The governing reason is: Column exposure and join behavior may need controls beyond simple role grants and row filters. C:Policy logic must encode the intended entitlement union or intersection explicitly. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate projection and join policy controls for the sensitive dataset where supported. The governing reason is: Column exposure and join behavior may need controls beyond simple role grants and row filters.
Question 157A multinational Snowflake deployment needs a recoverable account state in a secondary region but has replicated only one analytics database. What is the most appropriate Snowflake configuration or data-platform response? Use supported Time Travel querying or recovery within the table's configured retention period. Create and validate a zero-copy clone for the test and document its independent write lifecycle. Design appropriate supported account object and data replication coverage with a tested failover plan. Document and test user-accessible Time Travel recovery while recognizing Fail-safe's separate limited purpose. ExplanationCorrect Answer C:Design appropriate supported account object and data replication coverage with a tested failover plan. This directly addresses the scenario: A multinational Snowflake deployment needs a recoverable account state in a secondary region but has replicated only one analytics database. Technical basis: Business continuity depends on replicating necessary databases and supported account-level dependencies together. Check success by confirming: A controlled failover restores access through the approved secondary environment and required roles. Incorrect Answers A:Historical data recovery is governed by the object's supported retention window and table type. That is relevant to a different intervention. For the stated situation, the required action is: Design appropriate supported account object and data replication coverage with a tested failover plan. The governing reason is: Business continuity depends on replicating necessary databases and supported account-level dependencies together. B:A zero-copy clone begins with shared storage references but supports logically independent later changes. That is relevant to a different intervention. For the stated situation, the required action is: Design appropriate supported account object and data replication coverage with a tested failover plan. The governing reason is: Business continuity depends on replicating necessary databases and supported account-level dependencies together. D:Fail-safe is not a normal user-operated query or object-restore facility. That is relevant to a different intervention. For the stated situation, the required action is: Design appropriate supported account object and data replication coverage with a tested failover plan. The governing reason is: Business continuity depends on replicating necessary databases and supported account-level dependencies together.
Question 158A company configures a maximum of one cluster for a growing cross-region support dashboard and assumes queue handling is unlimited. An engineer recommends: Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. Which Snowflake architecture or data-governance principle best supports the recommendation? Query execution limits and resource isolation bound the impact of runaway statements on shared compute. Compute isolation can protect workloads even when they read and write the same governed storage. A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism. A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. ExplanationCorrect Answer D:A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. This supports the stated action: Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. Verification should show: A measured concurrency run stays within approved wait thresholds after capacity adjustments. Incorrect Answers A:Query execution limits and resource isolation bound the impact of runaway statements on shared compute. This does not establish the proposed intervention. The governing principle here is: A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. Apply it by: Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. B:Compute isolation can protect workloads even when they read and write the same governed storage. This does not establish the proposed intervention. The governing principle here is: A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. Apply it by: Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. C:A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism. This does not establish the proposed intervention. The governing principle here is: A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. Apply it by: Review actual query concurrency and supported multi-cluster limits for the assigned warehouse.
Question 159A finance group deploys new row policies without documenting what happens when a role belongs to two authorized departments. An engineer recommends: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. Which Snowflake architecture or data-governance principle best supports the recommendation? Governance metadata needs both approved editors and a traceable classification-change process. Column exposure and join behavior may need controls beyond simple role grants and row filters. Policy logic must encode the intended entitlement union or intersection explicitly. Effective governance needs observable use of data in addition to grants that authorize potential access. ExplanationCorrect Answer C:Policy logic must encode the intended entitlement union or intersection explicitly. This supports the stated action: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. Verification should show: A dual-department test role receives exactly the approved records for both departments. Incorrect Answers A:Governance metadata needs both approved editors and a traceable classification-change process. This does not establish the proposed intervention. The governing principle here is: Policy logic must encode the intended entitlement union or intersection explicitly. Apply it by: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. B:Column exposure and join behavior may need controls beyond simple role grants and row filters. This does not establish the proposed intervention. The governing principle here is: Policy logic must encode the intended entitlement union or intersection explicitly. Apply it by: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. D:Effective governance needs observable use of data in addition to grants that authorize potential access. This does not establish the proposed intervention. The governing principle here is: Policy logic must encode the intended entitlement union or intersection explicitly. Apply it by: Evaluate role precedence and allowed row combinations with representative overlapping grant tests.
Question 160A contractor receives direct privileges on numerous tables and the security team cannot determine which access is still approved. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Careless ownership transfer can block applications or permit unauthorized policy changes. An overly narrow policy breaks operations and broad allowlists enable network-based attacks. A compromised shared service account could expose multiple unrelated data domains. Untracked direct privileges make contractor offboarding unreliable. ExplanationCorrect Answer D:Untracked direct privileges make contractor offboarding unreliable. Here the failing condition is: A contractor receives direct privileges on numerous tables and the security team cannot determine which access is still approved. The specific correction is: Move applicable access through managed roles and perform periodic grant reviews using Snowflake metadata. Verify through: An inventory of effective grants maps each contractor right to a recorded business authorization. Incorrect Answers A:Object ownership carries administrative authority beyond ordinary read and write permissions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Untracked direct privileges make contractor offboarding unreliable. B:Network access restrictions must match actual trusted origins while preserving least privilege. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Untracked direct privileges make contractor offboarding unreliable. C:The workload identity should define a narrow permission boundary, not just authenticate successfully. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Untracked direct privileges make contractor offboarding unreliable.