queries during a pre-defined critical batch state?

Which workload management technique should the Administrator use to reject all QueryGrid

queries during a pre-defined critical batch state?
A . An exception that includes the following Foreign Servers:
TD_SYSFNLIB.QGInitiatorExport
TD_SYSFNLIB.QGInitiatorlmport
TD_SYSFNLIB.QGRemoteExport
TD_SYSFNLIB.QGRemotelmport
B . A filter that includes the following functions:
TD_SYSFNLIB.QGInitiatorExport
TD_SYSFNLIB.QGInitiatorlmport
TD_SYSFNLIB.QGRemoteExport
TD_SYSFNLIB.QGRemotelmport
C . An exception that excludes the following Foreign Servers:
TD_SYSFNLIB.QGInitiatorExport
TD_SYSFNLIB.QGInitiatorlmport
TD_SYSFNLIB.QGRemoteExport
TD_SYSFNLIB.QGRemotelmport
D . A filter that excludes the following functions:
TD_SYSFNLIB.QGInitiatorExport
TD_SYSFNLIB.QGInitiatorlmport
TD_SYSFNLIB.QGRemoteExport
TD_SYSFNLIB.QGRemotelmport

View Answer

Answer: A

Explanation:

In this case, using an exception with the Foreign Servers related to QueryGrid functions will prevent queries involving those foreign servers from running. This is a typical method to block or reject specific workloads during critical times, such as a batch processing window.

Exceptions in workload management are used to define specific conditions under which queries or workloads should be rejected or managed differently. By including these QueryGrid-related functions in an exception, the administrator ensures that any QueryGrid queries involving the listed foreign servers will be rejected during the critical batch state.

Options B and D, which mention filters, are not appropriate for rejecting queries. Filters are used for monitoring or routing purposes, not for outright rejection of workloads.

Option C, which suggests excluding the foreign servers in an exception, would not achieve the goal, as this would mean those queries are not affected by the exception. The goal here is to include these functions in an exception to actively reject them.