Exam SnowPro Core topic 1 question 750 discussion

When working with ETL processes, you need to use distributed paradigms very often, so can't use Temporary tables. Transient tables are specifically design for ETL processes. Additionaly, ETL processes can take a lot of time, and you often need to split the processes into smaller processes, so Temporary tables, which only lives during the session, are impractible.

Snowflake supports creating temporary tables for storing non-permanent, transitory data (e.g. ETL data, session-specific data). Temporary tables only exist within the session in which they were created and persist only for the remainder of the session. As such, they are not visible to other users or sessions. Once the session ends, data stored in the table is purged completely from the system and, therefore, is not recoverable, either by the user who created the table or Snowflake.

Direct quote on using temp tables for ETL on this link: https://docs.snowflake.com/en/user-guide/tables-temp-transient

actually reading Snowflake documentation they recommend temporary tables for ETL jobs. If you could please remove my comment dear moderator that says D.

Definitely Transient as ETL jobs may require you to NOT lose any data after a session.

My understanding is Transient will be the more suitable answer as this table will be used during the ETL operations on the contrary Temp tables are session-oriented and used for temporary purposes although Transient tables reside and are available after ETL ops and as they are not fail-safe and 0-1 day of time-travel so quite economical then Permamanet

Answer is C: https://docs.snowflake.com/en/user-guide/tables-temp-transient Snowflake supports creating temporary tables for storing non-permanent, transitory data (e.g. ETL data, session-specific data).

It's D, not C. The question tells us about ETL. You are using Transient with ETL not Temporary, and the cost will be be also reduce with Transient

correct