Match each SNMP administrative requirement or operational workflow on the left with its corresponding SNMP version, message type, or transport characteristic on the right.
- An agent generates an unsolicited alert that requires the receiver to send a Response PDU back to clear the notification buffer.SNMP Inform Request
- An NMS queries a router MIB table by requesting the next lexicographical object identifier in the hierarchy without prior knowledge of exact sub-tree indices.SNMP GetNext Operation
- A network device transmits an unacknowledged event notification using plaintext community string authentication to UDP destination port 162.SNMPv2c Trap
- Management traffic requires SHA-256 integrity verification and AES-128 payload encryption for all polled OID data.SNMPv3 authPriv Security Level
Cevap
Matching pairs: 1) Unsolicited acknowledged alert -> SNMP Inform Request, 2) Sequential MIB table traversal -> SNMP GetNext Operation, 3) Unacknowledged community-based notification -> SNMPv2c Trap, 4) Authentication and encryption model -> SNMPv3 authPriv Security Level.
Each match accurately reflects standard Cisco SNMP protocol behaviors: SNMP Informs require receiver acknowledgements via Response PDUs; SNMP GetNext requests iteratively traverse MIB instances sequentially; SNMPv2c Traps send unacknowledged alerts over UDP port 162 using community strings; and SNMPv3 authPriv enforces both authentication hashing and data encryption.
Adım Adım Çözüm
Anahtar Kavram
SNMP Messaging Mechanics, MIB Traversal, and SNMPv3 Security Models