A Citrix Administrator configured an external syslog server but is NOT seeing detailed TCP information. What could be causing this?

Question

Options

• ALog facility is NOT configured.
• BLog level is NOT enabled.
• CTCP logging is NOT enabled.
• DUser-defined audit log is NOT configured.

• A
  3% (1)
• B
  13% (4)
• C
  77% (24)
• D
  6% (2)

Explanation

TCP logging in Citrix must be explicitly enabled as a separate setting; configuring the syslog server destination alone does not automatically capture TCP connection details. Without enabling TCP logging, the syslog server receives general log data but no protocol-specific TCP information.

Why the distractors are wrong:

• A (Log facility): Log facility determines the category (e.g., local0–local7) under which logs are filed - misconfiguring it would misdirect logs entirely, not cause missing TCP details specifically.
• B (Log level): Log level controls severity filtering (debug, info, warning, error). A wrong log level reduces event volume overall but does not selectively strip TCP information.
• D (User-defined audit log): This relates to custom audit trails for administrative actions, not network protocol logging.

Memory tip: Think of TCP logging as its own "switch" separate from the syslog destination - you can have a fully working syslog server and still see nothing TCP-related if that switch is off. On the exam, when a question says "configured but NOT seeing specific protocol info," the answer is almost always that the protocol-level logging toggle is disabled.

No community discussion yet for this question.