Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HP Exam HPE6-A84 Topic 10 Question 19 Discussion

Actual exam question for HP's HPE6-A84 exam
Question #: 19
Topic #: 10
[All HPE6-A84 Questions]

Several AOS-CX switches are responding to SNMPv2 GET requests for the public community. The customer only permits SNMPv3. You have asked a network admin to fix this problem. The admin says, ''I tried to remove the community, but the CLI output an error.''

What should you recommend to remediate the vulnerability and meet the customer's requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

This is because SNMPv3 is a secure version of SNMP that provides authentication, encryption, and access control for network management. SNMPv3-only is a configuration option on AOS-CX switches that disables SNMPv1 and SNMPv2c, which are insecure versions of SNMP that use plain text community strings for authentication. By setting the snmp-server settings to ''snmpv3-only'', the switch will only respond to SNMPv3 requests and reject any SNMPv1 or SNMPv2c requests, thus remedying the vulnerability and meeting the customer's requirements.

A) Enabling control plane policing to automatically drop SNMP GET requests. This is not a valid recommendation because control plane policing is a feature that protects the switch from denial-of-service (DoS) attacks by limiting the rate of traffic sent to the CPU. Control plane policing does not disable SNMPv1 or SNMPv2c, but rather applies a rate limit to all SNMP requests, regardless of the version. Moreover, control plane policing might also drop legitimate SNMP requests if they exceed the rate limit, which could affect the network management.

C) Adding an SNMP community with a long random name. This is not a valid recommendation because an SNMP community is a shared secret that acts as a password for accessing network devices using SNMPv1 or SNMPv2c. Adding an SNMP community with a long random name does not disable SNMPv1 or SNMPv2c, but rather creates another community string that can be used for authentication. Moreover, adding an SNMP community with a long random name does not improve the security of SNMPv1 or SNMPv2c, as the community string is still transmitted in plain text and can be intercepted by an attacker.

D) Enabling SNMPv3, which implicitly disables SNMPv1/v2. This is not a valid recommendation because enabling SNMPv3 does not implicitly disable SNMPv1 or SNMPv2c on AOS-CX switches. Enabling SNMPv3 only adds support for the secure version of SNMP, but does not remove support for the insecure versions. Therefore, enabling SNMPv3 alone does not remedy the vulnerability or meet the customer's requirements.


Contribute your Thoughts:

Cristy
6 months ago
Gotta love it when the admin tries something and it just doesn't work. Reminds me of that time I tried to fix my car with duct tape. Didn't end well, let me tell you.
upvoted 0 times
...
Lura
6 months ago
I don't know, man. Policing the control plane sounds a bit overkill to me. Why not just go for the straightforward SNMPv3 route? It's the customer's requirement, after all.
upvoted 0 times
Helene
5 months ago
SNMPv3 is the best option to meet the customer's requirements.
upvoted 0 times
...
Lauran
6 months ago
But what about adding an SNMP community with a long random name?
upvoted 0 times
...
Dannie
6 months ago
Just go with SNMPv3, it's the easiest solution.
upvoted 0 times
...
...
Tequila
6 months ago
Hmm, I'm not sure about adding a random community name. That just seems like a bandaid solution. Why not just go straight for the SNMPv3 option and be done with it?
upvoted 0 times
...
Pete
6 months ago
I'd go with option D. Enabling SNMPv3 is the way to go, and it should automatically disable the older versions. Gotta keep up with the latest and greatest, you know?
upvoted 0 times
Linwood
6 months ago
Great, let's go with option D then. It's important to stay updated with the latest protocols.
upvoted 0 times
...
Tegan
6 months ago
I agree, SNMPv3 is more secure and will meet the customer's requirements.
upvoted 0 times
...
Kina
6 months ago
Option D is the best choice. Enabling SNMPv3 will solve the issue.
upvoted 0 times
...
...
Antione
6 months ago
Wow, this is a tricky one. Removing the community should definitely be the way to go, but the error is throwing me off. Maybe the admin needs to try a different approach?
upvoted 0 times
Anika
5 months ago
B) Setting the snmp-server settings to ''snmpv3-only''
upvoted 0 times
...
Yasuko
6 months ago
A) Enabling control plane policing to automatically drop SNMP GET requests
upvoted 0 times
...
Josphine
6 months ago
D) Enabling SNMPv3, which implicitly disables SNMPv1/v2
upvoted 0 times
...
Jaclyn
6 months ago
B) Setting the snmp-server settings to ''snmpv3-only''
upvoted 0 times
...
Annabelle
6 months ago
A) Enabling control plane policing to automatically drop SNMP GET requests
upvoted 0 times
...
Frederica
6 months ago
B) Setting the snmp-server settings to ''snmpv3-only''
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77