Which SNMP versions are commonly supported by NPM, and what distinguishes them for monitoring?

Which SNMP versions are commonly supported by NPM, and what distinguishes them for monitoring?

• A. SNMP v4 is the standard, offering modern security features.
• B. SNMP v3 provides security features like authentication and encryption; SNMP v1/v2c use simple read-only community strings.
• C. SNMP v1/v2c provide basic monitoring with community strings, while SNMP v3 adds authentication and encryption.
• D. SNMP v3 is deprecated in modern monitoring.

Answer: (C)

SNMP versions differ mainly in how access and data are secured during monitoring. In NPM you’ll commonly see support for SNMP v1, v2c, and v3. Versions v1 and v2c use community strings as a simple form of access control, and these strings determine whether a device’s data can be read or written. These community strings are not encrypted, so the data can be exposed in transit and there’s no strong user authentication. SNMP v3, on the other hand, introduces a formal security model. It uses user-based authentication to verify who is requesting data and can encrypt the data in transit to protect it from eavesdropping. This is implemented with different security levels, such as noAuthNoPriv, authNoPriv, and authPriv, giving finer control over authentication and privacy. Choosing the option that states basic monitoring with community strings for v1/v2c and adding authentication and encryption for v3 best reflects how these versions differ in practice for monitoring: it explains both the simple, legacy access method and the significantly more secure, modern approach. The other choices are inaccurate or incomplete—no SNMP v4 exists, SNMP v3’s security is broader than just “it provides security,” and SNMP v3 is not deprecated.

SNMP versions differ mainly in how access and data are secured during monitoring. In NPM you’ll commonly see support for SNMP v1, v2c, and v3. Versions v1 and v2c use community strings as a simple form of access control, and these strings determine whether a device’s data can be read or written. These community strings are not encrypted, so the data can be exposed in transit and there’s no strong user authentication.

SNMP v3, on the other hand, introduces a formal security model. It uses user-based authentication to verify who is requesting data and can encrypt the data in transit to protect it from eavesdropping. This is implemented with different security levels, such as noAuthNoPriv, authNoPriv, and authPriv, giving finer control over authentication and privacy.

Choosing the option that states basic monitoring with community strings for v1/v2c and adding authentication and encryption for v3 best reflects how these versions differ in practice for monitoring: it explains both the simple, legacy access method and the significantly more secure, modern approach. The other choices are inaccurate or incomplete—no SNMP v4 exists, SNMP v3’s security is broader than just “it provides security,” and SNMP v3 is not deprecated.