When using TLS for syslog, which configuration allows for secure and reliable transportation of messages to its default port?

Question

Options

• Alogging host 10.2.3.4 vrf mgmt transport tcp port 6514
• Blogging host 10.2.3.4 vrf mgmt transport udp port 6514
• Clogging host 10.2.3.4 vrf mgmt transport tcp port 514
• Dlogging host 10.2.3.4 vrf mgmt transport udp port 514

• A
  89% (33)
• C
  3% (1)
• D
  8% (3)

Explanation

TLS Syslog Configuration Explained

Option A is correct because TLS-secured syslog operates over TCP port 6514 - TCP provides the reliable, connection-oriented transport required for TLS encryption, and port 6514 is the IANA-assigned default port specifically designated for syslog over TLS (RFC 5425).

Why the distractors fail:

• Option B uses UDP, which is connectionless and cannot establish the TLS handshake required for encryption - TLS fundamentally requires TCP.
• Option C uses the correct transport (TCP) but the wrong port - port 514 is the legacy syslog port for unencrypted UDP traffic, not TLS.
• Option D combines both errors: UDP transport (incompatible with TLS) and port 514 (the traditional unencrypted syslog port).

Memory Tip: Think "TLS = TCP + 6514" - the "6" in 6514 can remind you it's the secure (next-generation) version of port 514. If you see UDP in a TLS syslog question, eliminate it immediately, as TLS always requires TCP's reliable connection to complete its handshake.

No community discussion yet for this question.