Question 340A company requires SSO for staff but administrators keep issuing local login credentials that bypass its identity provider. After this response — Set supported federation and authentication policy requirements and validate the approved exceptions. — which result most directly proves successful correction? A controlled session under operations can read approved objects but creation attempts fail. An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. The departed employee's old identity fails a login test and audit records show the disable operation. The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. ExplanationCorrect Answer B:An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. This directly validates the action: Set supported federation and authentication policy requirements and validate the approved exceptions. The control reduces this exposure: Parallel unmanaged login methods increase account takeover exposure. Incorrect Answers A:Effective privileges follow role inheritance and can exceed direct grants if hierarchy is not reviewed. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. C:Identity revocation must propagate to each downstream service, including data platform accounts. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. D:Managed access schemas centralize grant control and differ from ordinary object-owner grant administration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized SSO login succeeds and a nonexception local-password sign-in is rejected.
Question 341An analyst writes a join with a missing equality predicate and produces billions of rows from two small lookup tables. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Treating cardinality defects as performance issues leaves inaccurate business reports. Persistent spills cause high latency and unpredictable batch windows. A Cartesian product can multiply costs and corrupt aggregate results. Late filtering can multiply CPU and memory work at scale. ExplanationCorrect Answer C:A Cartesian product can multiply costs and corrupt aggregate results. Here the failing condition is: An analyst writes a join with a missing equality predicate and produces billions of rows from two small lookup tables. The specific correction is: Correct the intended join condition and compare estimated and actual row counts in the plan. Verify through: A test query returns expected unique business keys and bounded intermediate rows. Incorrect Answers A:Data shape and join semantics determine result correctness as well as computational load. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A Cartesian product can multiply costs and corrupt aggregate results. B:Oversized intermediate results and spilling can dominate runtime independently of final row count. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A Cartesian product can multiply costs and corrupt aggregate results. D:Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A Cartesian product can multiply costs and corrupt aggregate results.
Question 342A query over a ten-year transaction table filters by a recent date but still reads nearly every micro-partition. What is the most appropriate Snowflake configuration or data-platform response? Select only required columns and validate columnar scan metrics for the workload. Use per-query execution profiles and cluster history to locate workload-specific bottlenecks. Inspect partition pruning and filter predicate shape in the query plan and storage metadata. Inspect data skew and join partition distribution with tenant-specific test workloads. ExplanationCorrect Answer C:Inspect partition pruning and filter predicate shape in the query plan and storage metadata. This directly addresses the scenario: A query over a ten-year transaction table filters by a recent date but still reads nearly every micro-partition. Technical basis: Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination. Check success by confirming: Profile statistics show materially fewer partitions scanned for the same date range. Incorrect Answers A:Column-oriented storage can avoid reading unnecessary columns when SQL projection is selective. That is relevant to a different intervention. For the stated situation, the required action is: Inspect partition pruning and filter predicate shape in the query plan and storage metadata. The governing reason is: Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination. B:Warehouse utilization averages do not reveal each query's CPU, memory and I/O behavior. That is relevant to a different intervention. For the stated situation, the required action is: Inspect partition pruning and filter predicate shape in the query plan and storage metadata. The governing reason is: Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination. D:Highly uneven key distribution can create execution imbalance across parallel tasks. That is relevant to a different intervention. For the stated situation, the required action is: Inspect partition pruning and filter predicate shape in the query plan and storage metadata. The governing reason is: Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination.
Question 343A company requires SSO for staff but administrators keep issuing local login credentials that bypass its identity provider. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Parallel unmanaged login methods increase account takeover exposure. Incorrect role assumptions produce access outages or unreviewed privilege broadening. Confused role boundaries create support incidents and privilege overreach. Broad token trust exposes unrelated account roles to partner applications. ExplanationCorrect Answer A:Parallel unmanaged login methods increase account takeover exposure. Here the failing condition is: A company requires SSO for staff but administrators keep issuing local login credentials that bypass its identity provider. The specific correction is: Set supported federation and authentication policy requirements and validate the approved exceptions. Verify through: An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. Incorrect Answers B:Session role settings and connector support determine which granted privileges participate in access checks. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Parallel unmanaged login methods increase account takeover exposure. C:Database roles package database-scoped privileges but still require correct account-role assignment. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Parallel unmanaged login methods increase account takeover exposure. D:OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Parallel unmanaged login methods increase account takeover exposure.
Question 344A team sets the maximum cluster count higher than the approved minimum and assumes all clusters stay running throughout each day. What is the most appropriate Snowflake configuration or data-platform response? Use monitored auto-scale policies with explicit minimum and maximum cluster settings. Track warehouse monitor coverage and use appropriate account usage and cost controls for other billing categories. Set an appropriate auto-suspend interval and confirm auto-resume behavior for the report workload. Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. ExplanationCorrect Answer A:Use monitored auto-scale policies with explicit minimum and maximum cluster settings. This directly addresses the scenario: A team sets the maximum cluster count higher than the approved minimum and assumes all clusters stay running throughout each day. Technical basis: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. Check success by confirming: Cluster history shows added capacity during bursts and reduced capacity as demand falls. Incorrect Answers B:Resource monitors have defined scope and cannot be assumed to meter every type of Snowflake consumption. That is relevant to a different intervention. For the stated situation, the required action is: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. The governing reason is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. C:Warehouse credits accrue while compute resources remain active and idle periods should be minimized. That is relevant to a different intervention. For the stated situation, the required action is: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. The governing reason is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. D:A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. That is relevant to a different intervention. For the stated situation, the required action is: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. The governing reason is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand.
Question 345A user changes default roles and warehouse but believes the change will apply to an already running long-lived application session. An engineer recommends: Explicitly set or reconnect session context for the application instead of relying on altered user defaults. Which Snowflake architecture or data-governance principle best supports the recommendation? Service authentication should use managed identities and credential lifecycle controls separate from employees. Managed access schemas centralize grant control and differ from ordinary object-owner grant administration. Current session state may differ from future user-level defaults and must be managed intentionally. Object ownership carries administrative authority beyond ordinary read and write permissions. ExplanationCorrect Answer C:Current session state may differ from future user-level defaults and must be managed intentionally. This supports the stated action: Explicitly set or reconnect session context for the application instead of relying on altered user defaults. Verification should show: A fresh session reflects approved defaults while the existing connection is handled through controlled context changes. Incorrect Answers A:Service authentication should use managed identities and credential lifecycle controls separate from employees. This does not establish the proposed intervention. The governing principle here is: Current session state may differ from future user-level defaults and must be managed intentionally. Apply it by: Explicitly set or reconnect session context for the application instead of relying on altered user defaults. B:Managed access schemas centralize grant control and differ from ordinary object-owner grant administration. This does not establish the proposed intervention. The governing principle here is: Current session state may differ from future user-level defaults and must be managed intentionally. Apply it by: Explicitly set or reconnect session context for the application instead of relying on altered user defaults. D:Object ownership carries administrative authority beyond ordinary read and write permissions. This does not establish the proposed intervention. The governing principle here is: Current session state may differ from future user-level defaults and must be managed intentionally. Apply it by: Explicitly set or reconnect session context for the application instead of relying on altered user defaults.
Question 346A privileged schema owner drops a sensitive table while developers have a documented requirement for centralized schema-level grant governance. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Incorrect role assumptions produce access outages or unreviewed privilege broadening. Orphaned accounts permit unauthorized data access after employment ends. Decentralized grants can undermine centrally approved access boundaries. Confused role boundaries create support incidents and privilege overreach. ExplanationCorrect Answer C:Decentralized grants can undermine centrally approved access boundaries. Here the failing condition is: A privileged schema owner drops a sensitive table while developers have a documented requirement for centralized schema-level grant governance. The specific correction is: Evaluate managed access schema ownership and assign grant-management responsibility appropriately. Verify through: The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. Incorrect Answers A:Session role settings and connector support determine which granted privileges participate in access checks. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Decentralized grants can undermine centrally approved access boundaries. B:Identity revocation must propagate to each downstream service, including data platform accounts. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Decentralized grants can undermine centrally approved access boundaries. D:Database roles package database-scoped privileges but still require correct account-role assignment. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Decentralized grants can undermine centrally approved access boundaries.
Question 347A team expects a resource monitor to cap all Snowflake account spending including every serverless service. After this response — Track warehouse monitor coverage and use appropriate account usage and cost controls for other billing categories. — which result most directly proves successful correction? A peak loading rehearsal no longer increases BI warehouse queue time. A cost review distinguishes monitored warehouse credits from additional serverless and storage charges. Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job. The lone aggregation finishes within target time without a redundant cluster count. ExplanationCorrect Answer B:A cost review distinguishes monitored warehouse credits from additional serverless and storage charges. This directly validates the action: Track warehouse monitor coverage and use appropriate account usage and cost controls for other billing categories. The control reduces this exposure: Assuming one control covers every charge can leave the account budget unprotected. Incorrect Answers A:Compute isolation can protect workloads even when they read and write the same governed storage. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A cost review distinguishes monitored warehouse credits from additional serverless and storage charges. C:Warehouse credits accrue while compute resources remain active and idle periods should be minimized. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A cost review distinguishes monitored warehouse credits from additional serverless and storage charges. D:Warehouse size affects resources within one executing cluster, while cluster count supports simultaneous workload. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A cost review distinguishes monitored warehouse credits from additional serverless and storage charges.
Question 348An administrator sets a resource monitor on a reporting warehouse but assumes it also suspends every serverless pipeline job in the account. An engineer recommends: Document resource monitor scope and inspect separately metered serverless compute for the project. Which Snowflake architecture or data-governance principle best supports the recommendation? Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. Chargeback requires a stable mapping between metered resources and responsible business users. Partial utilization trends cannot establish total cost performance across the account. Compute billing and individual query history should be examined together before assigning cost causation. ExplanationCorrect Answer A:Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. This supports the stated action: Document resource monitor scope and inspect separately metered serverless compute for the project. Verification should show: A monthly statement reconciles monitored warehouse credits and unrelated service charges separately. Incorrect Answers B:Chargeback requires a stable mapping between metered resources and responsible business users. This does not establish the proposed intervention. The governing principle here is: Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. Apply it by: Document resource monitor scope and inspect separately metered serverless compute for the project. C:Partial utilization trends cannot establish total cost performance across the account. This does not establish the proposed intervention. The governing principle here is: Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. Apply it by: Document resource monitor scope and inspect separately metered serverless compute for the project. D:Compute billing and individual query history should be examined together before assigning cost causation. This does not establish the proposed intervention. The governing principle here is: Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. Apply it by: Document resource monitor scope and inspect separately metered serverless compute for the project.
Question 349A marketing analyst filters a shared view to infer hidden customer IDs through unauthorized projection of protected join keys. After this response — Evaluate projection and join policy controls for the sensitive dataset where supported. — which result most directly proves successful correction? Users from two regions receive distinct approved row populations from the same query. A controlled query uses an allowed aggregate join while prohibited key projection is denied. A report against each derived table returns only the phone fields allowed to the user role. Consumers can query the designated view but direct source table access is rejected. ExplanationCorrect Answer B:A controlled query uses an allowed aggregate join while prohibited key projection is denied. This directly validates the action: Evaluate projection and join policy controls for the sensitive dataset where supported. The control reduces this exposure: Unrestricted join keys can enable de-anonymization and cross-dataset tracking. Incorrect Answers A:Row access policies constrain visible rows independently of client application filters. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled query uses an allowed aggregate join while prohibited key projection is denied. C:Security controls on source columns must not be assumed to transfer automatically into every new object. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled query uses an allowed aggregate join while prohibited key projection is denied. D:A secure consumer abstraction does not justify opening direct access to underlying protected data. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled query uses an allowed aggregate join while prohibited key projection is denied.
Question 350A multinational group shares data across cloud regions but assumes a regional account can read another region's source without any configured replication or supported cross-region sharing mechanism. After this response — Confirm the supported cross-region distribution approach and required replication or listing configuration. — which result most directly proves successful correction? A consumer in the target region can query the approved shared object after the configured distribution completes. A test partner signs in through the approved reader environment and queries the limited dataset. A consumer SELECT succeeds while an attempted UPDATE to provider-owned source data is denied. The consumer can read allowed attributes but receives no protected identifiers. ExplanationCorrect Answer A:A consumer in the target region can query the approved shared object after the configured distribution completes. This directly validates the action: Confirm the supported cross-region distribution approach and required replication or listing configuration. The control reduces this exposure: Unplanned cross-region access can fail or violate location restrictions. Incorrect Answers B:Direct shares require supported consumer account arrangements and reader accounts have distinct provider responsibilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A consumer in the target region can query the approved shared object after the configured distribution completes. C:Shared database consumption does not make the consumer the owner of the producer's source tables. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A consumer in the target region can query the approved shared object after the configured distribution completes. D:Sharing requires intentional exposed object design rather than assuming every table column is contractually safe. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A consumer in the target region can query the approved shared object after the configured distribution completes.