An enterprise network engineer is auditing centralized management protocols and event notification mechanisms across core infrastructure switches. Match each network logging or management protocol configuration on the left with its correct operational or security characteristic on the right.
- Syslog Severity Level 2 (Critical)Indicates severe device conditions, such as primary system component failures, that require immediate attention.
- SNMPv3 authNoPrivProvides HMAC-based message integrity and user authentication, but transmits payload data unencrypted.
- NetFlow v9 / IPFIXProvides statistical traffic flow metadata and IP header information rather than individual event log messages.
- Syslog over TLS (TCP 6514)Establishes a connection-oriented, cryptographically secured transport channel to prevent log eavesdropping and tampering.
Answer
Syslog Severity Level 2 (Critical) matches with indicating severe device conditions requiring immediate attention. SNMPv3 authNoPriv matches with providing HMAC-based authentication without payload encryption. NetFlow v9 / IPFIX matches with providing statistical traffic flow metadata. Syslog over TLS (TCP 6514) matches with establishing a connection-oriented, cryptographically secured transport channel.
Each protocol or standard is correctly matched based on its core technical functionality: Syslog Level 2 represents Critical alerts; SNMPv3 authNoPriv authenticates users without encrypting traffic; NetFlow/IPFIX exports flow statistics rather than log strings; and Syslog over TLS utilizes TCP port 6514 for secure, reliable event transport.
Step-by-Step Solution
Key Concept
Network Logging and Auditing Mechanisms (Syslog, SNMPv3, NetFlow)