A Snowflake Administrator needs to persist all virtual warehouse configurations for auditing and backups. Given a table already exists with the following schema:
Table Name: VWH_META
Column 1: SNAPSHOT_TIME TIMESTAMP_NTZ
Column 2: CONFIG VARIANT
Which commands should be executed to persist the warehouse data at the time of execution in JSON format in the table VWH_META?

A Snowflake account is configured with SCIM provisioning for user accounts and has bi-directional synchronization for user identities. An Administrator with access to SECURITYADMIN uses the Snowflake UI to create a user by issuing the following commands:
use role USERADMIN;
create or replace role DEVELOPER_ROLE;
create user PTORRES PASSWORD = 'hello world!' MUST_CHANGE_PASSWORD = FALSE
default_role = DEVELOPER_ROLE;
The new user named PTORRES successfully logs in, but sees a default role of PUBLIC in the web UI. When attempted, the following command fails:
use DEVELOPER_ROLE;
Why does this command fail?

The following commands were executed:
Grant usage on database PROD to role PROD_ANALYST;
Grant usage on database PROD to role PROD_SUPERVISOR;
Grant ALL PRIVILEGES on schema PROD.WORKING to role PROD_ANALYST;
Grant ALL PRIVILEGES on schema PROD.WORKING to role PROD_SUPERVISOR;
Grant role PROD_ANALYST to user A;
Grant role PROD_SUPERVISOR to user B;
What authority does each user have on the WORKING schema?

An organization's sales team leverages this Snowflake query a few times a day:
SELECT CUSTOMER_ID, CUSTOMER_NAME, ADDRESS, PHONE_NO
FROM CUSTOMERS
WHERE LAST_UPDATED BETWEEN TO_DATE(CURRENT_TIMESTAMP) AND (TO_DATE(CURRENT_TIMESTAMP)-7);
What can the Snowflake Administrator do to optimize the use of persisted query results whenever possible?