Columns in the HIGH and VERY_HIGH aggregation threshold categories cannot be used when applying ____________ to your query.
- first-party insights
- aggregation functions such as SUM or AVG
- WHERE filters with literal (static) values
- UNION or JOIN functions
or
- WHERE filters
- JOIN functions
- third-party insights
- first-party insights
Explanation:
The correct answer is **WHERE filters with literal (static) values** because columns in the HIGH and VERY_HIGH aggregation threshold categories are typically derived from dynamic values or calculations that involve aggregation or other query functions. These columns cannot be used directly with **WHERE filters that apply static, literal values** because their values are not static and are calculated based on the context of the query. For example, a filter that attempts to use a literal value to restrict data based on dynamic aggregations would result in an error or incorrect results. Instead, such columns are intended to be used with more flexible query functions like aggregation or within calculations that adapt to the query context. The other options—aggregation functions, first-party insights, and UNION or JOIN functions—do not inherently conflict with the use of HIGH and VERY_HIGH threshold categories in the same way.