Teradata Workload Management Filters are designed to screen incoming requests or sessions based on specific classification criteria. An administrator can create a filter that identifies sessions based on a combination of attributes, such as the application username and the client application/ID. The filter can then be configured with an action, such as 'Reject,' to prevent the session from being established or the query from running. This directly addresses the security policy requirement to prohibit access for a specific user/client combination.

A. Flex Throttle: Flex Throttles are used to dynamically manage the concurrency of active queries based on system health conditions (e.g., CPU usage), not to reject sessions based on user or client criteria.

B. Utility Session: This is not a specific workload management feature for enforcing security policies. It refers to sessions initiated by Teradata utilities, which are managed by workloads but not filtered by a feature of this name.

C. Exception: Exceptions are rules that trigger actions (like aborting a query) when a running query violates predefined resource limits (e.g., exceeds CPU time), not for preventing a session from starting.

1. Teradata Vantage™ Workload Management User Guide, Release 17.20, B035-1197-112K, November 2022.

Chapter 4: Workload Management Setup Steps > Filters (Page 61): "Filters provide a way to screen requests that you do not want to run on the system... A filter specifies classification criteria for a request and an action to take if the request matches the criteria. The action can be to reject the request..."

Filter Classification Criteria (Page 62): The guide lists User Name, Application, and Client ID as valid classification criteria, confirming that a filter can target the specific combination mentioned in the question.

Chapter 6: Throttles (Page 91): "Throttles limit the number of concurrent queries from all sources or from a specific workload." This confirms throttles are for concurrency, not rejection based on identity.

Chapter 7: Exceptions (Page 105): "Exceptions are rules that specify what to do when a query misbehaves or exceeds system resource limits." This confirms exceptions apply to already running queries.