Deal of The Day! 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-A72 Topic 4 Question 86 Discussion

Actual exam question for HP's HPE6-A72 exam
Question #: 86
Topic #: 4
[All HPE6-A72 Questions]

Your customer has 349 users in a two-story building.

What are two benefits of a 2-Tier design? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, E

Contribute your Thoughts:

Carmelina
2 days ago
I believe having Layer 2 and Layer 3 protocols close to the endpoints is also important for implementing ACL and QoS policies effectively.
upvoted 0 times
...
Kaycee
6 days ago
C is the real winner here. Who needs layer 3 when you can just let those layer 2 switches handle everything? Routing traffic from APs? Easy peasy!
upvoted 0 times
...
Hana
7 days ago
D and E are the way to go. Supporting multiple WAN/MPLS connections directly on the Collapsed core is super convenient, and a cost-effective solution is always a plus.
upvoted 0 times
...
Lisbeth
14 days ago
I'll go with A and B. Implementing ACL and QoS at the edge is crucial for security and quality of service. And the performance boost from the Core is a no-brainer.
upvoted 0 times
...
Nichelle
16 days ago
Option B makes the most sense to me. Offloading processing from the Access layer to the Core should improve overall performance for the users.
upvoted 0 times
Emilio
3 days ago
User 1: I agree, offloading processing to the Core sounds like a good idea.
upvoted 0 times
...
...
Thurman
18 days ago
I agree with Chantell. Offloading processing to the Core and not needing additional switches for a third tier are definitely advantages.
upvoted 0 times
...
Chantell
19 days ago
I think the benefits of a 2-Tier design are improved performance and cost effectiveness.
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