Question 60A customer wants to re-share incoming provider data to an unrelated third party without any agreement. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Unapproved supplier or customer information becomes visible externally. The partner cannot consume the data because it has no account of its own. Repeated file copies become stale and extend data exposure. Data is distributed beyond the agreed provider-consumer trust boundary. ExplanationCorrect Answer D:Data is distributed beyond the agreed provider-consumer trust boundary. The direct prevention is to check the provider's sharing and resharing permissions before enabling redistribution. Consumer access to a shared database does not grant arbitrary onward redistribution rights. Incorrect Answers A:Provider-side views can limit exposed columns and permitted values in a share. The immediate omission risk in this case is: Data is distributed beyond the agreed provider-consumer trust boundary. B:Reader accounts let a provider enable restricted data consumption for eligible partners. The immediate omission risk in this case is: Data is distributed beyond the agreed provider-consumer trust boundary. C:Secure Data Sharing lets consumers query provider-approved objects without copying the underlying data. The immediate omission risk in this case is: Data is distributed beyond the agreed provider-consumer trust boundary.
Question 61A team promotes a recovery region without deciding how clients will find the new active account. Which Snowflake configuration or operational action most directly addresses this situation? Design the supported client connection and routing steps for controlled failover. Follow the supported failback workflow and reconcile data and ownership before resuming clients. Plan supported replication and failover capabilities with explicit activation steps. Inventory supported replication scope and account-level dependencies before declaring recovery-ready. ExplanationCorrect Answer A:Data readiness does not by itself redirect JDBC connections and application identities. The matching action is to design the supported client connection and routing steps for controlled failover. A test client reconnects through the approved secondary endpoint after the drill. Incorrect Answers B:Failback needs a controlled role transition rather than assuming the old primary is current. The operative distinction here is: Data readiness does not by itself redirect JDBC connections and application identities. The targeted change is: Design the supported client connection and routing steps for controlled failover. C:Replication synchronizes eligible objects but failover requires a documented secondary-account design. The operative distinction here is: Data readiness does not by itself redirect JDBC connections and application identities. The targeted change is: Design the supported client connection and routing steps for controlled failover. D:Recovering the database alone may not restore the surrounding account configuration and integrations. The operative distinction here is: Data readiness does not by itself redirect JDBC connections and application identities. The targeted change is: Design the supported client connection and routing steps for controlled failover.
Question 62A developer attempts to use FLATTEN on every scalar field and creates many duplicate rows. An engineer proposes to apply FLATTEN only to the intended repeated array or object path. Which explanation best describes why this is appropriate? Typed conversion clarifies semantics for numeric predicates and calculations. Expansion multiplies source rows by the selected collection's elements. VARIANT preserves semi-structured types and supports documented element-path access. Semi-structured element paths follow JSON key semantics independently of SQL identifier rules. ExplanationCorrect Answer B:Expansion multiplies source rows by the selected collection's elements. This is testable: a controlled three-element array produces exactly three expected output records. Incorrect Answers A:Typed conversion clarifies semantics for numeric predicates and calculations. For the current requirement, the decisive mechanism is: Expansion multiplies source rows by the selected collection's elements. The related action is: Apply FLATTEN only to the intended repeated array or object path. C:VARIANT preserves semi-structured types and supports documented element-path access. For the current requirement, the decisive mechanism is: Expansion multiplies source rows by the selected collection's elements. The related action is: Apply FLATTEN only to the intended repeated array or object path. D:Semi-structured element paths follow JSON key semantics independently of SQL identifier rules. For the current requirement, the decisive mechanism is: Expansion multiplies source rows by the selected collection's elements. The related action is: Apply FLATTEN only to the intended repeated array or object path.
Question 63A team creates one massive task that loads files, transforms and publishes data without observable step boundaries. After the team decides to break the workflow into supported tasks with clear dependency and failure checkpoints, which observation most directly validates the result? An inventory shows only the intended durable curated objects remain after processing. A sample unexpected column triggers a controlled validation alert. A simulated failed transform blocks publication while its upstream load remains recorded. A corrected invoice updates once and unaffected rows retain their existing IDs. ExplanationCorrect Answer C:A simulated failed transform blocks publication while its upstream load remains recorded. This matters because task graphs provide ordered execution and per-step operational visibility. Incorrect Answers A:Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. This is not the decisive validation for the stated requirement. The relevant evidence is: A simulated failed transform blocks publication while its upstream load remains recorded. B:Source evolution can silently change downstream mappings and expectations. This is not the decisive validation for the stated requirement. The relevant evidence is: A simulated failed transform blocks publication while its upstream load remains recorded. D:Incremental processing can apply changed records while retaining stable target data. This is not the decisive validation for the stated requirement. The relevant evidence is: A simulated failed transform blocks publication while its upstream load remains recorded.
Question 64An engineer edits Snowflake SQL inside VS Code and wants governed connections rather than pasted passwords. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Manual changes leave different object grants and names between environments. A homegrown connection layer lacks supported authentication and driver behavior. Performance triage proceeds without the relevant visual execution evidence. Credentials leak through version-controlled files or unsupported editor scripts. ExplanationCorrect Answer D:Credentials leak through version-controlled files or unsupported editor scripts. The direct prevention is to use a supported IDE integration with an approved connection and secrets workflow. IDE tools can combine local authoring with Snowflake execution while authentication remains controlled. Incorrect Answers A:Repeatable command execution reduces environment drift from interactive manual changes. The immediate omission risk in this case is: Credentials leak through version-controlled files or unsupported editor scripts. B:The JDBC interface integrates Java applications with Snowflake's SQL protocol. The immediate omission risk in this case is: Credentials leak through version-controlled files or unsupported editor scripts. C:Snowsight presents interactive execution and activity evidence for eligible queries. The immediate omission risk in this case is: Credentials leak through version-controlled files or unsupported editor scripts.
Question 65A warehouse experiences brief heavy resource bursts during analytic queries and the team wants help for eligible query fragments. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate Query Acceleration Service for supported queries and measured workload behavior. Analyze actual query predicates and apply optimization only to justified targets. Investigate multi-cluster scale-out for queue-bound queries before adding acceleration. Evaluate Search Optimization Service for supported selective access patterns. ExplanationCorrect Answer A:Query Acceleration Service can offload eligible portions of a query to additional compute. The matching action is to evaluate Query Acceleration Service for supported queries and measured workload behavior. Eligible test queries show a reduction in duration with documented acceleration use. Incorrect Answers B:Targeted access paths have maintenance cost and predicate-support constraints. The operative distinction here is: Query Acceleration Service can offload eligible portions of a query to additional compute. The targeted change is: Evaluate Query Acceleration Service for supported queries and measured workload behavior. C:Query acceleration targets eligible execution work, not warehouse admission contention. The operative distinction here is: Query Acceleration Service can offload eligible portions of a query to additional compute. The targeted change is: Evaluate Query Acceleration Service for supported queries and measured workload behavior. D:Search optimization maintains an access path useful for eligible high-selectivity lookups. The operative distinction here is: Query Acceleration Service can offload eligible portions of a query to additional compute. The targeted change is: Evaluate Query Acceleration Service for supported queries and measured workload behavior.
Question 66An operator estimates warehouse spend by multiplying peak size by all hours of the month. An engineer proposes to use actual warehouse metering and runtime records to attribute billed credits. Which explanation best describes why this is appropriate? Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. Per-second usage after the startup minimum depends on running duration and resource size. Suspended warehouses require a supported start path before executing compute work. Warehouse usage and modification are distinct privileges. ExplanationCorrect Answer B:Per-second usage after the startup minimum depends on running duration and resource size. This is testable: reported credits reconcile with warehouse usage history rather than an all-month estimate. Incorrect Answers A:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. For the current requirement, the decisive mechanism is: Per-second usage after the startup minimum depends on running duration and resource size. The related action is: Use actual warehouse metering and runtime records to attribute billed credits. C:Suspended warehouses require a supported start path before executing compute work. For the current requirement, the decisive mechanism is: Per-second usage after the startup minimum depends on running duration and resource size. The related action is: Use actual warehouse metering and runtime records to attribute billed credits. D:Warehouse usage and modification are distinct privileges. For the current requirement, the decisive mechanism is: Per-second usage after the startup minimum depends on running duration and resource size. The related action is: Use actual warehouse metering and runtime records to attribute billed credits.
Question 67A data steward removes a source table without checking which pipelines rely on it. After the team decides to use dependency and lineage evidence to review downstream impact before deletion, which observation most directly validates the result? The analysis identifies the affected materialization and reporting consumers. An inventory shows consistent values for a sample of same-sensitivity columns. The dependency review lists the impacted views and scheduled tasks. A newly tagged test column receives the intended masking behavior. ExplanationCorrect Answer C:The dependency review lists the impacted views and scheduled tasks. This matters because consumers and derived objects can depend on the same source across schemas. Incorrect Answers A:Lineage links transformations and consuming objects to upstream data assets. This is not the decisive validation for the stated requirement. The relevant evidence is: The dependency review lists the impacted views and scheduled tasks. B:Consistent classifications are necessary for reliable policy automation. This is not the decisive validation for the stated requirement. The relevant evidence is: The dependency review lists the impacted views and scheduled tasks. D:Tag metadata can drive policy assignment at scale when configured deliberately. This is not the decisive validation for the stated requirement. The relevant evidence is: The dependency review lists the impacted views and scheduled tasks.
Question 68An organization operator wants multi-account administration but uses ACCOUNTADMIN of a single workload account. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Identity management access is bundled with unnecessary warehouse control. Sensitive rows become accessible to nearly all account users. Developers can change unrelated role grants across the account. Cross-account tasks are attempted using the wrong authority. ExplanationCorrect Answer D:Cross-account tasks are attempted using the wrong authority. The direct prevention is to use authorized organization-level administration rather than conflating it with account control. Organization scope and one account's administrative scope are distinct security boundaries. Incorrect Answers A:Creating principals is different from modifying compute or data objects. The immediate omission risk in this case is: Cross-account tasks are attempted using the wrong authority. B:Every Snowflake user inherits the PUBLIC role by design. The immediate omission risk in this case is: Cross-account tasks are attempted using the wrong authority. C:Snowflake separates security administration from data and warehouse object administration. The immediate omission risk in this case is: Cross-account tasks are attempted using the wrong authority.
Question 69An admin sees yesterday's ACCOUNT_USAGE records arriving later than near-real-time Snowsight activity. Which Snowflake configuration or operational action most directly addresses this situation? Account for documented latency in ACCOUNT_USAGE views before interpreting missing rows. Reconcile estimated credits with metered usage and Snowflake billing rules. Separate supported warehouse credit monitors from other consumption and storage meters. Query appropriate ACCOUNT_USAGE query history views with permitted access. ExplanationCorrect Answer A:Some historical account usage views are delayed relative to live query monitoring. The matching action is to account for documented latency in ACCOUNT_USAGE views before interpreting missing rows. A later refresh includes the known query and matches its original timestamp. Incorrect Answers B:Warehouse cost depends on size and actual running duration, with minimum charge semantics. The operative distinction here is: Some historical account usage views are delayed relative to live query monitoring. The targeted change is: Account for documented latency in ACCOUNT_USAGE views before interpreting missing rows. C:A monitor's coverage does not replace comprehensive billing analysis across products. The operative distinction here is: Some historical account usage views are delayed relative to live query monitoring. The targeted change is: Account for documented latency in ACCOUNT_USAGE views before interpreting missing rows. D:Account usage views provide historical activity records useful for account-level attribution. The operative distinction here is: Some historical account usage views are delayed relative to live query monitoring. The targeted change is: Account for documented latency in ACCOUNT_USAGE views before interpreting missing rows.
Question 70A data file contains a malformed record and an engineer needs to identify errors before committing new rows. An engineer proposes to validate staged data using a supported COPY validation or error-inspection workflow. Which explanation best describes why this is appropriate? COPY tracks previously loaded files to help avoid accidental duplicate ingestion. Pre-load validation surfaces parsing and column conversion problems. A SELECT transform during COPY can align and cast source expressions into target columns. Snowflake records file-loading outcomes that can support safe reconciliation. ExplanationCorrect Answer B:Pre-load validation surfaces parsing and column conversion problems. This is testable: the error report pinpoints the malformed input row and offending field. Incorrect Answers A:COPY tracks previously loaded files to help avoid accidental duplicate ingestion. For the current requirement, the decisive mechanism is: Pre-load validation surfaces parsing and column conversion problems. The related action is: Validate staged data using a supported COPY validation or error-inspection workflow. C:A SELECT transform during COPY can align and cast source expressions into target columns. For the current requirement, the decisive mechanism is: Pre-load validation surfaces parsing and column conversion problems. The related action is: Validate staged data using a supported COPY validation or error-inspection workflow. D:Snowflake records file-loading outcomes that can support safe reconciliation. For the current requirement, the decisive mechanism is: Pre-load validation surfaces parsing and column conversion problems. The related action is: Validate staged data using a supported COPY validation or error-inspection workflow.