To enable federated authentication (aka SSO via SAML 2.0 ) in Snowflake, the integration with an Identity Provider (IdP) must be configured. This setup involves configuring external authentication via SAML , and Snowflake needs specific information from the IdP.

???? Required Information from IdP:

URL Endpoint for SAML Requests (B)

This is often referred to as the SSO URL or SAML 2.0 Endpoint (HTTP) .

It's the URL that Snowflake redirects users to for authentication.

In Snowflake's SAML configuration, this is required as the SAML2_ISSUER or SAML2_SSO_URL.

Authentication Certificate (D)

This is the X.509 certificate issued by the IdP.

It's used by Snowflake to validate the digital signature of the SAML assertions sent by the IdP.

It ensures that the SAML response is authentic and not tampered with.

❌ Why Other Options Are Incorrect:

A. IdP account details

Not needed. Snowflake doesn’t require credentials or internal details from the IdP. It relies on assertions sent via SAML, not stored accounts.

C. SAML response format

Snowflake adheres to SAML 2.0 standard , and expects a compliant format. There's no need to specify format explicitly — it’s part of the standard protocol.

E. IdP encryption key

Not required by Snowflake. Snowflake verifies SAML assertions via signature validation , not encryption using the IdP’s private key.

???? SnowPro Administrator References:

Snowflake Documentation — Federated Authentication Setup

https://docs.snowflake.com/en/user-guide/security-fed-auth-use

https://docs.snowflake.com/en/user-guide/security-fed-auth-config

Required IdP Metadata for Snowflake SAML Configuration :

SAML2_SSO_URL: SAML 2.0 POST binding endpoint

SAML2_X509_CERT: Public cert used to validate IdP signatures

According to the Using Persisted Query Results documentation, the RESULT_SCAN function allows you to query the result set of a previous command as if it were a table. This can improve the performance of the second query by avoiding reading the same data from micro-partitions again. The other actions do not provide optimal performance for the second query because:

• Assigning additional clusters to the virtual warehouse does not affect the data access speed, but only the query execution speed. It also increases the cost of the warehouse.

• Increasing the STATEMENT_TIMEOUT_IN_SECONDS parameter in the session does not improve the performance of the query, but only allows it to run longer before timing out. It also increases the risk of resource contention and deadlock.

• Preventing the virtual warehouse from suspending between the running of the first and second queries does not guarantee that the data will be cached in memory, as Snowflake uses a least recently used (LRU) cache eviction policy. It also increases the cost of the warehouse.

https://docs.snowflake.com/en/user-guide/querying-persisted-results

Scenario: You want to rollback changes due to a problematic query (e.g., accidental data modification or corruption). Snowflake provides two powerful tools:

✅ B. CLONE ... BEFORE (STATEMENT = > 'query_id')

This uses Time Travel + Zero-Copy Cloning .

You can clone a table as it existed before a specific query .

It creates a full copy of the table's state at that moment without duplicating storage .

Example:

CREATE TABLE prd_table_bkp CLONE prd_table

BEFORE (STATEMENT = > '01a2b3c4-0000-0000-0000-123456789abc');

✅ D. ALTER TABLE ... SWAP WITH ...

Once you've cloned the backup, you can swap it with the live table.

This is a fast, atomic operation — ideal for rollback.

Example:

ALTER TABLE prd_table SWAP WITH prd_table_bkp;

❌ Why the Other Options Are Incorrect:

A. SELECT SYSTEM$CANCEL_QUERY(...)

Cancels a currently running query — doesn’t help if the query already executed and caused damage.

C. CREATE TABLE ... AS SELECT * FROM RESULT_SCAN(...)

Reconstructs results , not the original table.

Only captures output rows, not full table state.

Not ideal for rollback.

E. Contact Snowflake Support to retrieve Fail-safe data

Fail-safe is for disaster recovery only , and only accessible by Snowflake support.

It’s not intended for routine rollback or recovery and has a 7-day fixed retention (non-configurable).

???? SnowPro Administrator References:

Zero-Copy Cloning with Time Travel

ALTER TABLE SWAP

System Functions – SYSTEM$CANCEL_QUERY

Fail-safe Overview