Chapter Review Answers
Answer: C. In the default EX configuration, there is no native VLAN. The default VLAN is untagged, and in this manner it is similar but not equal to a native VLAN.
Answer: A. A native VLAN is not technically required, depending on what switch-to-switch protocols and what types of equipment you are working with. On the EX, you must specifically define and then add trunk support for a native VLAN when one is desired.
Answer: False. Traffic on access links is untagged. The access link is mapped to a VLAN at the
[edit interfaces <name> unit <number> family ethernet-switching]hierarchy using thevlan membersstatement.Answer: D. A Layer 3 device (a router) is needed, but this function does not have to be external and can be instantiated through the EX switch’s RVI.
Answer: C. Only C is correct. EX switches do not have any dynamic trunking negotiation protocols, and do not support ISL encapsulation.
Answer: A. Currently, GVRP functions only to automate VLAN-to-trunk bindings. It does not operate in a client/server model, nor does it propagate VLAN definitions themselves, and it does not support authentication.
Answer: B. With no trunk negotiation protocols, the default is access mode, even on switch-to-switch links. As there is no native VLAN in a default configuration, the access port defaults to the default VLAN, and does not use tagging.
Answer: C. Only a trunk interface is allowed to have multiple VLAN associations. Use the output of a
show vlans extensivecommand ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access