Question 300An administrator schedules replication but does not review last-successful refresh timestamps. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Applications continue targeting an unavailable account after failover. Recovered tables exist but the application cannot authenticate or execute its jobs. A regional failure leaves no tested way to resume service. Failover unexpectedly loses more recent changes than the business accepts. ExplanationCorrect Answer D:Failover unexpectedly loses more recent changes than the business accepts. The direct prevention is to monitor replication status and effective recovery-point lag. Replicated data may lag behind a primary according to configured refresh and workload health. Incorrect Answers A:Data readiness does not by itself redirect JDBC connections and application identities. The immediate omission risk in this case is: Failover unexpectedly loses more recent changes than the business accepts. B:Recovering the database alone may not restore the surrounding account configuration and integrations. The immediate omission risk in this case is: Failover unexpectedly loses more recent changes than the business accepts. C:Replication synchronizes eligible objects but failover requires a documented secondary-account design. The immediate omission risk in this case is: Failover unexpectedly loses more recent changes than the business accepts.
Question 301A healthcare consortium needs to make a private data product available to only named institutions. Which Snowflake configuration or operational action most directly addresses this situation? Create a controlled private listing targeted to the approved consumers. Evaluate a public Snowflake Marketplace listing with reviewed description and access requirements. Validate the delivered shared objects and consumer queries before updating the listing claim. Review the listing's actual provider grants, terms and required approval flow. ExplanationCorrect Answer A:Private listings restrict audience while retaining listing-based discovery for invited accounts. The matching action is to create a controlled private listing targeted to the approved consumers. An invited institution can see the listing but an unrelated account cannot. Incorrect Answers B:Marketplace listings provide a catalog distribution path for eligible shared data products. The operative distinction here is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The targeted change is: Create a controlled private listing targeted to the approved consumers. C:Listing documentation should match the live governed data product contract. The operative distinction here is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The targeted change is: Create a controlled private listing targeted to the approved consumers. D:Listing discovery and underlying data authorization are distinct steps. The operative distinction here is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The targeted change is: Create a controlled private listing targeted to the approved consumers.
Question 302A team sees a Trust Center warning but closes it without checking the finding's source configuration. An engineer proposes to validate the specific posture evidence and apply an approved corrective change before closure. Which explanation best describes why this is appropriate? Account audit records connect changes and execution to actors and timestamps. Security findings require evidence-based remediation rather than status-only dismissal. Alerts can evaluate scheduled conditions and trigger authorized notification actions. Key management choices interact with account architecture and required assurances. ExplanationCorrect Answer B:Security findings require evidence-based remediation rather than status-only dismissal. This is testable: a rerun no longer reports the original misconfiguration. Incorrect Answers A:Account audit records connect changes and execution to actors and timestamps. For the current requirement, the decisive mechanism is: Security findings require evidence-based remediation rather than status-only dismissal. The related action is: Validate the specific posture evidence and apply an approved corrective change before closure. C:Alerts can evaluate scheduled conditions and trigger authorized notification actions. For the current requirement, the decisive mechanism is: Security findings require evidence-based remediation rather than status-only dismissal. The related action is: Validate the specific posture evidence and apply an approved corrective change before closure. D:Key management choices interact with account architecture and required assurances. For the current requirement, the decisive mechanism is: Security findings require evidence-based remediation rather than status-only dismissal. The related action is: Validate the specific posture evidence and apply an approved corrective change before closure.
Question 303A complex aggregate is repeatedly queried and Snowflake Enterprise capabilities are available. After the team decides to assess a materialized view when supported workload and refresh costs justify it, which observation most directly validates the result? The execution plan identifies the expensive source join after dependency review. Reading the view returns current authorized source rows without a separate reload. Query plans and maintenance credits show whether the materialization is worthwhile. An approved source-row change appears through the view without a view reload step. ExplanationCorrect Answer C:Query plans and maintenance credits show whether the materialization is worthwhile. This matters because materialized views maintain eligible precomputed results for repeated query access. Incorrect Answers A:A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. This is not the decisive validation for the stated requirement. The relevant evidence is: Query plans and maintenance credits show whether the materialization is worthwhile. B:A standard view saves a query definition rather than materializing its full result table. This is not the decisive validation for the stated requirement. The relevant evidence is: Query plans and maintenance credits show whether the materialization is worthwhile. D:Standard views evaluate their definition using current authorized data. This is not the decisive validation for the stated requirement. The relevant evidence is: Query plans and maintenance credits show whether the materialization is worthwhile.
Question 304A static aggregate is recomputed by dozens of dashboards every minute from the same large source. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? A poorly matched optimization delivers little benefit. Users expect caching behavior that a plain view does not promise. Each report reads many unrelated partitions. Repeated expensive aggregation dominates warehouse resources. ExplanationCorrect Answer D:Repeated expensive aggregation dominates warehouse resources. The direct prevention is to test a supported materialized view and its maintenance economics. Eligible materialized views store maintained results that can avoid repeated full recomputation. Incorrect Answers A:Different optimization techniques suit point lookups versus broad range pruning. The immediate omission risk in this case is: Repeated expensive aggregation dominates warehouse resources. B:A standard view stores its SQL definition; materialized views maintain results separately. The immediate omission risk in this case is: Repeated expensive aggregation dominates warehouse resources. C:Clustering can improve micro-partition locality and pruning for suitable large datasets. The immediate omission risk in this case is: Repeated expensive aggregation dominates warehouse resources.
Question 305A team tolerates brief queueing and prioritizes minimizing active clusters throughout the day. Which Snowflake configuration or operational action most directly addresses this situation? Use a supported Economy multi-cluster scaling policy with appropriate cluster limits. Review actual scaling mode, running workload and suspend behavior before changing caps. Enable supported multi-cluster scale-out rather than only enlarging a single cluster. Raise max cluster count within licensed, cost-approved limits and observe scale behavior. ExplanationCorrect Answer A:Economy waits longer before provisioning another cluster to favor utilization. The matching action is to use a supported Economy multi-cluster scaling policy with appropriate cluster limits. Warehouse Load History shows fewer extra clusters while waits stay within policy. Incorrect Answers B:Cluster scale-in depends on policy and sustained workload demand, not a static promise. The operative distinction here is: Economy waits longer before provisioning another cluster to favor utilization. The targeted change is: Use a supported Economy multi-cluster scaling policy with appropriate cluster limits. C:Additional clusters provide concurrency capacity without requiring faster individual queries. The operative distinction here is: Economy waits longer before provisioning another cluster to favor utilization. The targeted change is: Use a supported Economy multi-cluster scaling policy with appropriate cluster limits. D:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The operative distinction here is: Economy waits longer before provisioning another cluster to favor utilization. The targeted change is: Use a supported Economy multi-cluster scaling policy with appropriate cluster limits.
Question 306A task is scheduled every five minutes but its SQL fails because it uses a role without underlying table access. An engineer proposes to assign a role with correct source and target privileges to the task ownership context. Which explanation best describes why this is appropriate? Streams track table change offsets for supported incremental processing patterns. Task execution requires permissions for the SQL objects it accesses. Task predecessor relationships enforce ordered execution of dependent SQL work. Change tracking depends on historical metadata remaining available for stream consumption. ExplanationCorrect Answer B:Task execution requires permissions for the SQL objects it accesses. This is testable: task history shows successful runs with the intended owner role. Incorrect Answers A:Streams track table change offsets for supported incremental processing patterns. For the current requirement, the decisive mechanism is: Task execution requires permissions for the SQL objects it accesses. The related action is: Assign a role with correct source and target privileges to the task ownership context. C:Task predecessor relationships enforce ordered execution of dependent SQL work. For the current requirement, the decisive mechanism is: Task execution requires permissions for the SQL objects it accesses. The related action is: Assign a role with correct source and target privileges to the task ownership context. D:Change tracking depends on historical metadata remaining available for stream consumption. For the current requirement, the decisive mechanism is: Task execution requires permissions for the SQL objects it accesses. The related action is: Assign a role with correct source and target privileges to the task ownership context.
Question 307A business unit assumes a resource monitor limits all possible Snowflake charges, including storage. After the team decides to separate supported warehouse credit monitors from other consumption and storage meters, which observation most directly validates the result? The estimated total agrees with observed warehouse metering within timing tolerances. A controlled quota event creates the expected warning before an overrun. The cost report reconciles compute and storage expenses separately. The report lists query IDs, users, warehouses and usage time windows. ExplanationCorrect Answer C:The cost report reconciles compute and storage expenses separately. This matters because a monitor's coverage does not replace comprehensive billing analysis across products. Incorrect Answers A:Warehouse cost depends on size and actual running duration, with minimum charge semantics. This is not the decisive validation for the stated requirement. The relevant evidence is: The cost report reconciles compute and storage expenses separately. B:Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. This is not the decisive validation for the stated requirement. The relevant evidence is: The cost report reconciles compute and storage expenses separately. D:Account usage views provide historical activity records useful for account-level attribution. This is not the decisive validation for the stated requirement. The relevant evidence is: The cost report reconciles compute and storage expenses separately.
Question 308A tiny single-row metadata lookup is slow once after resume and engineers propose 4X-Large compute. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Each small cluster repeats the same memory pressure and fails independently. Idle credits continue accruing after the users leave. Repeated disk spill keeps the batch slow despite low concurrency. The team doubles credits without addressing the startup bottleneck. ExplanationCorrect Answer D:The team doubles credits without addressing the startup bottleneck. The direct prevention is to profile the startup and query overhead before multiplying warehouse size. Bigger compute does not necessarily speed trivial queries dominated by resume or service overhead. Incorrect Answers A:Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. The immediate omission risk in this case is: The team doubles credits without addressing the startup bottleneck. B:Suspension releases idle warehouse compute while resumption serves subsequent activity. The immediate omission risk in this case is: The team doubles credits without addressing the startup bottleneck. C:A larger cluster provides more execution capacity and can reduce spilling for suitable queries. The immediate omission risk in this case is: The team doubles credits without addressing the startup bottleneck.
Question 309A security runbook assumes PUBLIC is a confidential role that only named employees possess. Which Snowflake configuration or operational action most directly addresses this situation? Review grants to PUBLIC and remove sensitive privileges from universally inherited access. Replace routine use with a custom reporting role limited to required tables and warehouses. Delegate approved user management through a suitably scoped USERADMIN or custom role. Use SYSADMIN-backed object-owner roles for data objects and reserve SECURITYADMIN for grants. ExplanationCorrect Answer A:Every Snowflake user inherits the PUBLIC role by design. The matching action is to review grants to PUBLIC and remove sensitive privileges from universally inherited access. A low-privilege test user cannot query restricted tables through PUBLIC. Incorrect Answers B:ACCOUNTADMIN is a powerful administrative role and should not be an application default. The operative distinction here is: Every Snowflake user inherits the PUBLIC role by design. The targeted change is: Review grants to PUBLIC and remove sensitive privileges from universally inherited access. C:Creating principals is different from modifying compute or data objects. The operative distinction here is: Every Snowflake user inherits the PUBLIC role by design. The targeted change is: Review grants to PUBLIC and remove sensitive privileges from universally inherited access. D:Snowflake separates security administration from data and warehouse object administration. The operative distinction here is: Every Snowflake user inherits the PUBLIC role by design. The targeted change is: Review grants to PUBLIC and remove sensitive privileges from universally inherited access.
Question 310A team wants a multi-cluster warehouse in a tier that lacks the feature. An engineer proposes to verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. Which explanation best describes why this is appropriate? Feature availability is edition-dependent even when the underlying SQL tables are supported. Multi-cluster concurrency features depend on edition support as well as warehouse settings. Extended retention beyond the Standard limit requires eligible edition and object settings. Edition choice governs availability of enhanced security and compliance controls. ExplanationCorrect Answer B:Multi-cluster concurrency features depend on edition support as well as warehouse settings. This is testable: the account accepts the supported multi-cluster configuration and shows multiple active clusters under load. Incorrect Answers A:Feature availability is edition-dependent even when the underlying SQL tables are supported. For the current requirement, the decisive mechanism is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The related action is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. C:Extended retention beyond the Standard limit requires eligible edition and object settings. For the current requirement, the decisive mechanism is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The related action is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. D:Edition choice governs availability of enhanced security and compliance controls. For the current requirement, the decisive mechanism is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The related action is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out.