Match each Simple Network Management Protocol (SNMP) mechanism or operational requirement on the left with its corresponding protocol characteristic or SNMP message type on the right.
- Unacknowledged event notification sent from a managed network device to an NMS using UDP port 162SNMP Trap
- Reliable event notification that requires the destination NMS to send an explicit response PDU back upon receiptSNMP Inform
- SNMPv3 security level providing both message authentication (HMAC-SHA/MD5) and packet encryption (AES/DES)SNMPv3 authPriv
- Request PDU sent by an NMS on UDP port 161 to sequentially traverse and retrieve entries from a MIB tableSNMP GetNext
Answer
Unacknowledged notifications correspond to SNMP Trap; reliable notifications requiring acknowledgment correspond to SNMP Inform; authentication with encryption corresponds to SNMPv3 authPriv; sequential MIB traversal corresponds to SNMP GetNext.
Each SNMP concept is paired to its defining technical attribute: Traps are unacknowledged notifications (UDP 162), Informs provide explicit acknowledgment and retransmission, authPriv adds cryptographic encryption alongside authentication, and GetNext handles sequential MIB walking (UDP 161).
Step-by-Step Solution
Key Concept
SNMP Operational Mechanics, Traps vs. Informs, and SNMPv3 Security Levels