nerdexam
SnowflakeSnowflake

SOL-C01 · Question #134

SOL-C01 Question #134: Real Exam Question with Answer & Explanation

The correct answer is B: Set the 'QUERY _ TAG' session parameter to 'REPORTING' before executing queries against. Setting the `QUERY TAG' session parameter allows you to tag queries with metadata, such as 'REPORTING'. This tag is associated with the query regardless of the warehouse used, enabling accurate cost allocation and tracking even if the wrong warehouse is accidentally used. Resourc

Snowflake Account and Security

Question

A Snowflake account has two virtual warehouses, 'WH ETC and 'WH REPORTING'. You need to ensure that the cost of running queries against a specific table, 'SALES DATA' , is accurately attributed to the reporting team, even when they accidentally use the 'WH ETL' warehouse. How can you achieve this cost allocation effectively?

Options

  • AUse resource monitors to limit the total credit consumption of 'WH ETC.
  • BSet the 'QUERY _ TAG' session parameter to 'REPORTING' before executing queries against
  • Ccontrols access but not cost allocation. A IJDF (option D) is complex and may not be practical.
  • DCreate a user-defined function (UDF) that checks the current warehouse and raises an error if
  • EConfigure data masking on 'SALES DATA' when queried from 'WH ETC.

Explanation

Setting the `QUERY TAG' session parameter allows you to tag queries with metadata, such as 'REPORTING'. This tag is associated with the query regardless of the warehouse used, enabling accurate cost allocation and tracking even if the wrong warehouse is accidentally used. Resource monitors (option A) limit credit usage but don't attribute cost. Role-based access control (option Data masking (option E) focuses on data security, not cost attribution.

Topics

#Cost Management#QUERY_TAG#Cost Allocation#Query Tracking

Community Discussion

No community discussion yet for this question.

Full SOL-C01 PracticeBrowse All SOL-C01 Questions