"Choose your S-TAP protocol by using the GIM parameter WINSTAP_V8_PROTOCOL, or the guard_tap.ini parameter V8_PROTOCOL, where … 1: enabled (protocol 8)." The parameter reference states for V8_PROTOCOL: "Enable Protocol 8 on the S-TAP. Both S-TAPs reside in the same image. One is dormant while…" the other runs.
The same setting has two names depending on where you configure it. WINSTAP_V8_PROTOCOL is the GIM parameter, while V8_PROTOCOL is the entry in guard_tap.ini . The question asks about the ini file, so the answer is V8_PROTOCOL=1 . Option A is the trap: it is correct for GIM but not for the file.
Why Protocol 8: "The new S-TAP protocol 8 reduces CPU usage and memory usage." Protocols 7 and 8 coexist and share the same configuration file. The default is off.
Compatibility: Some protocol 7 parameters are not valid for protocol 8, so review the Protocol 8 parameter sections (general, driver, discovery, debug, application server, Guardium hosts).
Ports: Protocol 8 uses TCP 9800/9801 for alive messages.
Apply: Restart the S-TAP service after changing the value.