You have a data pipeline that aggregates web server logs hourly. The pipeline loads data into a Snowflake table 'WEB LOGS' which is partitioned by 'event_time'. You notice that queries against this table are slow, especially those that filter on specific time ranges. Analyze the following Snowflake table definition and query pattern and select the options to diagnose and fix the performance issue: Table Definition:

• A. Change the table to use clustering on 'event_time' instead of partitioning to improve query performance for range filters.
• B. Create a materialized view that pre-aggregates the 'status_code' by hour to speed up the aggregation query.
• C. Increase the warehouse size to improve query performance.
• D. The table is already partitioned by 'event_time' , so there is no need for further optimization.
• E. Add a search optimization strategy to the table on the 'event_time' column.

A data engineering team is managing a Snowflake warehouse that supports a high volume of ad-hoc queries from data analysts exploring a large, semi-structured JSON dataset containing website clickstream data'. The query performance is frequently slow, and analysts are complaining about long wait times. The warehouse is already sized appropriately. You have identified that many of the queries filter on nested JSON attributes that are not explicitly indexed. Considering only query acceleration service features, what is the MOST effective approach to improve query performance for these ad-hoc queries without modifying the queries themselves or significantly increasing storage costs?

• A. Use a combination of materialized views and query acceleration for best performance.
• B. Enable Search Optimization Service for the table containing the JSON data. Selectively enable search optimization on the specific columns and nested paths that are frequently used in WHERE clause predicates.
• C. Enable Automatic Clustering on the table to improve data organization based on query patterns.
• D. Create a dedicated virtual warehouse specifically for ad-hoc queries, and enable query acceleration on this warehouse.
• E. Enable the Materialized View feature to create materialized views over the frequently queried nested JSON attributes.

A healthcare provider stores patient data in Snowflake, including 'PATIENT ID', 'NAME, 'MEDICAL HISTORY , and 'INSURANCE ID. They need to comply with HIPAA regulations. As a data engineer, you need to ensure that PHI (Protected Health Information) is masked appropriately based on user roles. Which of the following steps are NECESSARY to achieve this using Snowflake's data masking features and RBAC? (Select all that apply)

• A. Apply the created masking policies to the corresponding columns in the patient data tables, ensuring that the masking policies are designed to reveal only the necessary information based on the user's role (e.g., doctors see full medical history, nurses see limited medical history, admins see de-identified data).
• B. Grant the 'OWNERSHIP privilege on the 'PATIENT table to the 'ACCOUNTADMIN' role, ensuring complete control and management of the data by the administrator.
• C. Create custom roles representing different user groups within the organization (e.g., 'DOCTOR, 'NURSE, 'ADMIN') and grant them the necessary privileges to access the data, including 'SELECT on the tables and views containing patient data.
• D. Enforce multi-factor authentication (MFA) for all users accessing the Snowflake environment to enhance security and prevent unauthorized access to sensitive data.
• E. Identify the columns containing PHI and create appropriate masking policies for each column (e.g., masking 'NAME, 'MEDICAL HISTORY, INSURANCE_ID).

You are managing a Snowflake environment where data retention is set to the default 1 day for all databases and tables. You need to clone a production table, 'CUSTOMER DATA, to a development environment to test some complex transformations. However, after cloning, you realize that the original 'CUSTOMER DATA' table in production was accidentally dropped 2 days ago. Which of the following statements accurately describe the situation and what can be done, if anything?

• A. While the source 'CUSTOMER DATA' is dropped and outside the retention period, the clone created will remain available and fully functional for querying. It is an independent copy. The clone is usable indefinitely, within the limits of your Snowflake account storage.
• B. The cloned 'CUSTOMER DATA' table in the development environment will remain accessible because the clone operation created a point-in-time snapshot.
• C. The cloned 'CUSTOMER DATA' table will only remain accessible if the source database was also cloned at the same time. If only the table was cloned, the cloned table is unusable after 1 day.
• D. The cloned 'CUSTOMER DATA' table in the development environment will inherit the data retention period from the original 'CUSTOMER DATA' table, so it will also be inaccessible after 1 day if dropped in development.
• E. The cloned 'CUSTOMER DATA' table in the development environment will no longer be accessible because the source table has been dropped and the data retention period has expired. The clone is effectively useless.