Snowflake Time Travel preserves historical data versions to support recovery operations such as querying previously modified data, cloning historical objects, and restoring dropped objects.
The default Time Travel retention period for transient databases, schemas, and tables is one day, regardless of whether the account uses Enterprise Edition or a higher edition.
Option A is therefore correct.
Unlike permanent tables, transient tables do not benefit from Snowflake's seven-day Fail-safe retention period. Their Time Travel retention can be configured to zero or one day, and historical data is not recoverable through normal Time Travel operations after the applicable period expires.
Option D is a plausible distractor because Enterprise Edition and higher support Time Travel retention periods of up to 90 days for permanent databases, schemas, and tables. However, this extended retention capability does not apply to transient tables.
Options B and C describe durations that are unavailable for transient tables.
Administrators should carefully distinguish between a database's default retention setting and the maximum retention supported by its contained table types. Creating a transient database does not provide extended historical recovery merely because the account uses Enterprise Edition.
Transient objects are primarily appropriate for intermediate, reproducible, or noncritical datasets where reduced storage overhead is more important than extended recovery protection.
Official Snowflake references: Working with Temporary and Transient Tables: Comparison of Table Types; Understanding & Using Time Travel.