Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 0d 11h 4m 14s Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HP Exam HPE7-A01 Topic 4 Question 20 Discussion

Actual exam question for HP's HPE7-A01 exam
Question #: 20
Topic #: 4
[All HPE7-A01 Questions]

A customer is looking Tor a wireless authentication solution for all of their loT devices that meet the following requirements

- The wireless traffic between the IoT devices and the Access Points must be encrypted

- Unique passphrase per device

- Use fingerprint information to perform role-based access

Which solutions will address the customer's requirements? (Select two.)

Show Suggested Answer Hide Answer
Suggested Answer: C

The reason is that the linkup delay timer is a feature that delays bringing downstream VSX links up, following a VSX device reboot or an ISL flap. The linkup delay timer has two phases: initial synchronization phase and link-up delay phase.

The initial synchronization phase is the download phase where the rebooted node learns all the LACP+MAC+ARP+STP database entries from its VSX peer through ISLP. The initial synchronization timer, which is not configurable, is the required time to download the database information from the peer.

The link-up delay phase is the duration for installing the downloaded entries to the ASIC, establishing router adjacencies with core nodes and learning upstream routes. The link-up delay timer default value is 180 seconds. Depending on the network size, ARP/routing tables size, you might be required to set the timer to a higher value (maximum 600 seconds).

When both VSX devices reboot, the link-up delay timer is not used.

Therefore, by configuring the linkup delay timer to include LAGs 101 and 102, which are part of the same VSX device as LAG 201, you can ensure that both devices have enough time to synchronize their databases and form routing adjacencies before bringing down their downstream links.


Contribute your Thoughts:

Basilia
18 days ago
A and D seem like the best options. Unique passphrases and encrypted traffic are covered, and EAP-TLS provides the fingerprint-based access control.
upvoted 0 times
Rasheeda
8 hours ago
A and D are definitely the best options. They meet all the requirements.
upvoted 0 times
...
...
Louvenia
19 days ago
I'm not sure about ClearPass Policy Manager, it doesn't seem to meet all the requirements. I would go with A and D as well.
upvoted 0 times
...
Jose
24 days ago
I agree with Jackie, MPSK and an internal RADIUS server, as well as MPSK Local with EAP-TLS, seem like the best solutions.
upvoted 0 times
...
Jackie
27 days ago
I think options A and D would address the customer's requirements.
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
a