In an auto-scaling multi-cluster virtual warehouse with the SCALING_POLICY set to ECONOMY, another cluster is started when the system has enough load for 2 minutes (A). This policy is designed to optimize the balance between performance and cost, starting additional clusters only when the sustained load justifies it2.

When cloning a database containing stored procedures and regular views with fully qualified table references, the cloned views and stored procedures will reference the cloned tables in the cloned database (A). This ensures that the cloned database is a self-contained copy of the original, with all references pointing to objects within the same cloned database. References: SnowPro Core Certification cloning database stored procedures views

The Snowflake Account_Usage.Metering_History view is used to gather the hourly credit usage for an account. This view provides details on the credits consumed by various services within Snowflake for the last
365 days1.

Snowpipe uses key-based authentication for its REST endpoints. This involves generating and using a key pair (public and private keys) to securely authenticate API requests.
* Generate Key Pair: Generate a public and private key pair.
* Register Public Key: Register the public key with the Snowflake user that will be making the API requests.
* Authenticate Requests: Use the private key to sign API requests sent to Snowpipe REST endpoints.
References:
* Snowflake Documentation: Key Pair Authentication & Key Rotation
* Snowflake Documentation: Using Snowpipe REST API

The credit consumption for maintaining a materialized view is impacted by how often the base table changes
and whether the materialized view has a cluster key defined (D). Changes to the base table can trigger a refresh of the materialized view, consuming credits. Additionally, having a cluster key defined can optimize the performance and credit usage during the materialized view's maintenance. References: SnowPro Core Certification materialized view credit consumption