A network operations team is upgrading its centralized monitoring and logging architecture to ensure regulatory compliance and robust forensic capabilities. Match each network logging or telemetry mechanism on the left with its primary operational auditing function on the right.
- NTP TimestampingProvides synchronized time references across all network infrastructure to ensure accurate event correlation during forensic log analysis.
- NetFlow / IPFIX TelemetryCollects IP flow metadata, such as source/destination addresses, port numbers, and byte counts, to audit network traffic volume and bandwidth utilization.
- TACACS+ AccountingRecords user login sessions, privilege elevation, and exact CLI commands executed by administrators for accountability and compliance auditing.
- SNMPv3 Trap / InformSends immediate, asynchronous event notifications to a network management station when hardware errors or specified operational thresholds occur.
Answer
Each network logging mechanism matches its corresponding functional requirement: NTP Timestamping matches synchronized time references for log correlation; NetFlow / IPFIX Telemetry matches IP flow metadata for traffic and bandwidth auditing; TACACS+ Accounting matches tracking user sessions and administrative CLI commands; and SNMPv3 Trap / Inform matches sending immediate asynchronous event notifications for threshold violations.
Each mechanism serves a distinct role in network operations: NTP guarantees consistent timestamping required for forensic event correlation across systems; NetFlow/IPFIX supplies IP traffic flow metadata for bandwidth and throughput auditing; TACACS+ Accounting maintains strict audit logs of administrative CLI actions and user sessions; and SNMPv3 Traps/Informs deliver immediate asynchronous push notifications for device status changes.
Step-by-Step Solution
Key Concept
Network Logging and Telemetry Mechanisms