Which of the following facts must be considered when designing for IP telephony within an Enterprise Campus network?

Which of the following facts must be considered when designing for IP telephony within an Enterprise Campus network?
A . Because the IP phone is a three-port switch, IP telephony extends the network edge, impacting the Distribution layer.
B . Video and voice are alike in being bursty and bandwidth intensive, and thus impose requirements to be lossless, and have minimized delay and jitter.
C . IP phones have no voice and data VLAN separation, so security policies must be based on upper layer traffic characteristics.
D . Though multi-VLAN access ports are set to Dot1Q and carry more than two VLANs they are not trunk ports.

Answer: D

Explanation:

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-4500-series-switches/69632-configuring-cat-ipphone.

html#topic1

When you connect an IP phone to a switch using a trunk link, it can cause high CPU utilization in the switches.

As all the VLANs for a particular interface are trunked to the phone, it increases the number of STP instances

the switch has to manage. This increases the CPU utilization. Trunking also causes unnecessary broadcast /

multicast / unknown unicast traffic to hit the phone link. In order to avoid this, remove the trunk configuration and keep the voice and access VLAN configured along with Quality of Service (QoS). Technically, it is still a trunk, but it is called a Multi-VLAN Access Port (MVAP). Because voice and data traffic can travel through the same port, you should specify a different VLAN for each type of traffic. You can configure a switch port to forward voice and data traffic on different VLANs. Configure IP phone ports with a voice VLAN configuration.

This configuration creates a pseudo trunk, but does not require you to manually prune the unnecessary VLANs.

Latest 300-320 Dumps Valid Version with 725 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments