N10-009 ยท Documentation, lifecycle and monitoring
SNMP monitoring
Traps, MIB, v2c vs v3, community strings, authentication.
Key points
- A manager polls agents on UDP 161; agents send traps (unsolicited alerts) to UDP 162.
- Data is described by a MIB and addressed by OIDs. v1/v2c use clear-text community strings; v3 adds user-based authentication and optional encryption (noAuthNoPriv, authNoPriv, authPriv).
Practice questions
What is an SNMP trap?
- A manager request for a value
- An unsolicited alert sent by an agent to the manager
- A file describing available objects
- An encrypted community string
Show answer
Answer: B. An unsolicited alert sent by an agent to the manager
A trap is sent by the agent on its own when an event occurs. Polling is manager-initiated; a MIB is the data definition, not a message.
Which statements about SNMPv3 are correct?
- It supports authentication of users
- It can encrypt message contents
- It relies on clear-text community strings
- It uses TCP 443 only
- It removes the need for a MIB
Show answer
Answer: A. It supports authentication of users, B. It can encrypt message contents
v3 introduced user-based security with authentication and optional privacy. It does not rely on community strings, and it still uses UDP 161/162.
Changing the community string from "public" to something else makes SNMPv2c encrypted.
Show answer
Answer: False
False. A custom string is better than the default, but v2c still sends it in clear text. Only v3 offers encryption.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
