The LOGIN_HISTORY view in the ACCOUNT_USAGE schema provides information about login attempts, including both successful and failed logins. This view can be used to review the failed login attempts of a specific user for the past 30 days. References: [COF-C02] SnowPro Core Certification Exam Study Guide

Snowpark-optimized virtual warehouses in Snowflake are designed to efficiently handle workloads with large memory requirements. Snowpark is a developer framework that allows users to write code in languages like Scala, Java, and Python to process data in Snowflake. Given the nature of these programming languages and the types of data processing tasks they are typically used for, having a virtual warehouse that can efficiently manage large memory-intensive operations is crucial.
Understanding Snowpark-Optimized Virtual Warehouses:
Snowpark allows developers to build complex data pipelines and applications within Snowflake using familiar programming languages.
These virtual warehouses are optimized to handle the execution of Snowpark workloads, which often involve large datasets and memory-intensive operations.
Large Memory Requirements:
Workloads with large memory requirements include data transformations, machine learning model training, and advanced analytics.
These operations often need to process significant amounts of data in memory to perform efficiently.
Snowpark-optimized virtual warehouses are configured to provide the necessary memory resources to support these tasks, ensuring optimal performance and scalability.
Other Considerations:
While Snowpark can handle other types of workloads, its optimization for large memory tasks makes it particularly suitable for scenarios where data processing needs to be done in-memory.
Snowflake's ability to scale compute resources dynamically also plays a role in efficiently managing large memory workloads, ensuring that performance is maintained even as data volumes grow.
Snowflake Documentation: Introduction to Snowpark
Snowflake Documentation: Virtual Warehouses

Snowflake recommends considering adding a clustering key to a table when its size reaches 1 Terabyte (TB) or larger. Clustering keys help optimize the storage and query performance by organizing the data in a table based on the specified columns. This is particularly beneficial for large tables where data retrieval can become inefficient without proper clustering.
Why Clustering Keys Are Important: Clustering keys ensure that data stored in Snowflake is physically ordered in a way that aligns with the most frequent access patterns, thereby reducing the amount of scanned data during queries and improving performance.
Recommendation Basis: The recommendation for tables of size 1 TB or larger is based on the observation that smaller tables generally do not benefit as much from clustering, given Snowflake's architecture. However, as tables grow in size, the benefits of clustering become more pronounced.
Implementing Clustering Keys:
To set a clustering key for a table, you can use the CLUSTER BY clause during table creation or alter an existing table to add it:
CREATE TABLE my_table (... ) CLUSTER BY (column1, column2);
Or for an existing table:
ALTER TABLE my_table CLUSTER BY (column1, column2);