A Citrix Administrator needs to investigate why Citrix ADC messages are NOT being recorded on an external server. What should the administrator check to resolve this issue?

Question

Options

• ALocation of nslog file
• BContent inspection
• CAuthentication, authorization, and auditing (AAA) policy
• DSyslog server entry

• A
  5% (2)
• B
  16% (6)
• C
  3% (1)
• D
  76% (28)

Explanation

Option D is correct because when Citrix ADC messages are not reaching an external server, the first thing to verify is whether a syslog server entry is properly configured. The ADC must have the external syslog server's IP address, port, and log level defined - without this entry, the system has no destination to send log messages to, regardless of any other settings.

Why the distractors are wrong:

• A (nslog file location): The nslog file is a local log file on the ADC itself. If the issue is that messages aren't reaching an external server, the local file location is irrelevant.
• B (Content inspection): Content inspection is a security feature for inspecting application payloads (e.g., SSL/HTTP traffic). It has nothing to do with syslog/audit logging configuration.
• C (AAA policy): AAA policies govern user authentication and access control, not the routing of system log messages to external servers.

Memory tip: Think of it this way - before logs can go anywhere, the ADC needs to know where to send them. A missing or misconfigured syslog server entry is like having no address on an envelope. Always check the destination first when logs don't arrive externally.

No community discussion yet for this question.