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 28 Discussion

Actual exam question for HP's HPE6-A84 exam
Question #: 28
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:

Laurena
2 months ago
Come on, you can't just slap a long random name on the community and call it a day. That's like trying to fix a leaky faucet with duct tape. Gotta do it right with SNMPv3.
upvoted 0 times
...
Lonny
2 months ago
Option D all the way! Enabling SNMPv3 is like upgrading from a tricycle to a Ferrari. Sure, it might take a bit more effort, but it's worth it to leave those v1/v2 vulnerabilities in the dust.
upvoted 0 times
Shaquana
28 days ago
A) Enabling control plane policing to automatically drop SNMP GET requests
upvoted 0 times
...
Mabel
1 months ago
B) Setting the snmp-server settings to ''snmpv3-only''
upvoted 0 times
...
Carmela
1 months ago
D) Enabling SNMPv3, which implicitly disables SNMPv1/v2
upvoted 0 times
...
...
Delisa
2 months ago
But wouldn't setting the snmp-server settings to 'snmpv3-only' also work? That's option B.
upvoted 0 times
...
Dino
2 months ago
I agree with Marcos, enabling SNMPv3 is the best way to meet the customer's requirements.
upvoted 0 times
...
Ilda
2 months ago
Enabling SNMPv3-only is definitely the way to go. Gotta keep that sensitive data secure, you know? Plus, it's like a secret handshake for network admins.
upvoted 0 times
Florinda
29 days ago
That's right! SNMPv3-only is the best option for security and meeting the customer's requirements.
upvoted 0 times
...
Paris
1 months ago
D) Enabling SNMPv3, which implicitly disables SNMPv1/v2
upvoted 0 times
...
Clare
1 months ago
B) Setting the snmp-server settings to ''snmpv3-only''
upvoted 0 times
...
...
Marcos
2 months ago
I think we should go with option D.
upvoted 0 times
...
Deandrea
2 months ago
Ah, the classic 'tried to remove the community but got an error' scenario. I bet the admin tried to delete it with a single command and didn't realize it needed some cleanup first.
upvoted 0 times
Tish
26 days ago
Yes, enabling SNMPv3 is the best option to meet the customer's requirements.
upvoted 0 times
...
Clay
29 days ago
D) Enabling SNMPv3, which implicitly disables SNMPv1/v2
upvoted 0 times
...
Cassie
1 months ago
That should do the trick. It will only allow SNMPv3 requests.
upvoted 0 times
...
Annalee
1 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