Snowflake SnowPro Core Practice Test 17
Question 160
For an original SnowPro Core educational scenario, consider: Analysts need to reproduce a report as of a known timestamp within the configured retention period. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Assume every historical version is queryable indefinitely after the retention period expires.
- Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency.
- Check: Verify client driver version, role, database, warehouse, authentication and query history for a representative operation.
- Check: Check retention settings, query timestamp and a before/after row sample before restoring.
- Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
Explanation
Correct Answer
D:Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition. Acceptance: The prior valid state is inspected or restored without overwriting unrelated current records.
E:Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition. Evidence: Check retention settings, query timestamp and a before/after row sample before restoring.
Incorrect Answers
A:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
B:Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency. Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
C:Check: Verify client driver version, role, database, warehouse, authentication and query history for a representative operation. Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
Question 161
A Snowflake engineer is examining this platform situation: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly. A proposed shortcut is: Run SELECT AT against Fail-safe as though it were an unlimited public snapshot store. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
- Run SELECT AT against Fail-safe as though it were an unlimited public snapshot store.
Explanation
Correct Answer
A:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
B:Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
D:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
Question 162
A Snowflake implementation review finds: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly. The team proposes: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Specialized warehouse types provide different memory-to-compute characteristics and cost profiles; they are not universally preferable for SQL reporting.
- Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
- Snowflake's legacy notebook experience is being superseded by Notebooks in Workspaces; availability and workflows depend on account rollout and current documentation.
- Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Explanation
Correct Answer
D:Demonstrable success requires: The recovery runbook specifies the correct mechanism and realistic timing for historical incidents. This principle explains the proposed technical approach, which is: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowpark-optimized warehouse selection) rather than the documented Fail-safe purpose and operational limits decision.
B:Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:Snowflake's legacy notebook experience is being superseded by Notebooks in Workspaces; availability and workflows depend on account rollout and current documentation. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 163
The data platform team has not yet approved changes. Current evidence indicates: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Verify client driver version, role, database, warehouse, authentication and query history for a representative operation.
- Inspect raw PARSE_JSON output, key names, TYPEOF and TRY_TO_NUMBER results on representative records.
- Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- Compare service-level billing and account usage with warehouse usage for the relevant reporting period.
Explanation
Correct Answer
C:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. Applied case: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly.
Incorrect Answers
A:Verify client driver version, role, database, warehouse, authentication and query history for a representative operation. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
B:Inspect raw PARSE_JSON output, key names, TYPEOF and TRY_TO_NUMBER results on representative records. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
D:Compare service-level billing and account usage with warehouse usage for the relevant reporting period. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 164
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- The recovery runbook specifies the correct mechanism and realistic timing for historical incidents.
- Idle hours stop consuming warehouse compute and the next permitted query resumes processing as expected.
- Monitoring reports show expected data at the promised freshness and scope without misinterpreting latency as absence.
- Each intended array element appears as a queryable row while empty or malformed payloads are handled deliberately.
Explanation
Correct Answer
A:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. The result must be validated using the documented dataset or access context.
Incorrect Answers
B:Idle hours stop consuming warehouse compute and the next permitted query resumes processing as expected. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:This option addresses a different Snowflake technical topic (Information Schema versus Account Usage) rather than the documented Fail-safe purpose and operational limits decision.
D:Each intended array element appears as a queryable row while empty or malformed payloads are handled deliberately. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 165
An implementation sign-off request identifies the following problem: An operator wants to use Fail-safe as a routine SQL query method to recover a deleted test table instantly. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. Verify: Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases.
- Change: Store evolving documents in suitable VARIANT structures while defining needed relational attributes with appropriate native types. Verify: Inspect parsed JSON values, TYPEOF results and casts for null, numeric, Boolean and string examples.
- Change: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Verify: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Verify: Inspect execution history before and after actions such as collect or write and compare data transfer size.
Explanation
Correct Answer
C:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. The change is successful only when: The recovery runbook specifies the correct mechanism and realistic timing for historical incidents.
Incorrect Answers
A:Change: Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
B:This option addresses a different Snowflake technical topic (Structured and semi-structured data types) rather than the documented Fail-safe purpose and operational limits decision.
D:This option addresses a different Snowflake technical topic (Snowpark DataFrame execution) rather than the documented Fail-safe purpose and operational limits decision.
Question 166
A Snowflake engineer is examining this platform situation: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention. A proposed shortcut is: Run SELECT AT against Fail-safe as though it were an unlimited public snapshot store. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Separate persistent cloud storage from independently provisioned warehouse compute and Snowflake-managed cloud services when designing the architecture.
- Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets.
- Run SELECT AT against Fail-safe as though it were an unlimited public snapshot store.
- Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
Explanation
Correct Answer
D:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. Applied case: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention.
Incorrect Answers
A:Separate persistent cloud storage from independently provisioned warehouse compute and Snowflake-managed cloud services when designing the architecture. An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention.
B:Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. Use this instead: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
Question 167
A Snowflake implementation review finds: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention. The team proposes: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
- Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
- Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
- Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Explanation
Correct Answer
A:Demonstrable success requires: The recovery runbook specifies the correct mechanism and realistic timing for historical incidents. Applied case: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention.
Incorrect Answers
B:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 168
The data platform team has not yet approved changes. Current evidence indicates: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Review warehouse configuration, idle duration and metered credit history around overnight gaps.
- Inspect stage file listings, directory table refresh and supported document-processing entry points.
- Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
Explanation
Correct Answer
C:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Review warehouse configuration, idle duration and metered credit history around overnight gaps. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
B:Inspect stage file listings, directory table refresh and supported document-processing entry points. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
D:Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 169
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- The prior valid state is inspected or restored without overwriting unrelated current records.
- The recovery runbook specifies the correct mechanism and realistic timing for historical incidents.
- Both interactive and automated users access only the authorized objects through the correct interfaces.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
Explanation
Correct Answer
B:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. The approved implementation step was: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
Incorrect Answers
A:The prior valid state is inspected or restored without overwriting unrelated current records. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
C:Both interactive and automated users access only the authorized objects through the correct interfaces. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
D:Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
Question 170
For an original SnowPro Core educational scenario, consider: An audit plan treats Fail-safe as a zero-cost customer-managed backup with unlimited retention. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Select Snowsight for suitable interactive tasks and supported Snowflake connectors, drivers or CLI for automated access.
- Check: Examine task graph history, predecessor states, warehouse permissions and failure handling.
- Change: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
- Check: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- Run SELECT AT against Fail-safe as though it were an unlimited public snapshot store.
Explanation
Correct Answer
C:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. Evidence: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
D:Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel. Required intervention: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism.
Incorrect Answers
A:Change: Select Snowsight for suitable interactive tasks and supported Snowflake connectors, drivers or CLI for automated access. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
B:Check: Examine task graph history, predecessor states, warehouse permissions and failure handling. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
E:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Fail-safe is not an ordinary customer-queryable historical table interface and it has different guarantees and storage implications from Time Travel.
