Refer to the exhibit. A network administrator configures an interface on a new switch so that it connects to interface Gi1/0/1 on switch Cat9300-1. Which configuration must be applied to the new interface?
Why B? The switch port in the exhibit was configured with "switchport mode trunk", as can be seen by Administrative Mode: trunk. So why not do same configuration on the new switch? Also I believe Cisco recommends statically configuring trunks and not using DTP for security reasons
but new cisco devices have to 1dotq command auto configured today, tryng to use this command today will not work since its already configured. I ran into this already.
Both A and B will work.
switchport trunk encapsulation dot1q is a very old command. No switch needs this nowadays.
A is better than B because it's more straightforward. Since the other end is already statically configured as trunk, we don't need to pretend to be negotiable from this end. Just tell the switch, configure your port as a trunk! This is safer and more efficient. Trunk settings on a switch is not something that often requires changes. Once set, it will run this way for years. No need to negotiate.
tried A in Packet Tracer :
Switch(config-if)#switchport mode trunk
Command rejected: An interface whose trunk encapsulation is "Auto" can not be configured to "trunk" mode.
B worked well
I choose B because its a tricky question: it's asking you to select the configuration that is applied ON THE OTHER SIDE of the configuration which is exhibited. The exhibited show illustrates that the negotiation of trunking is on (so you can configure the other side by DTP), and you don't know if the other side makes you apply the "switchport trunk encapsulation dot1q" command before applying the "switchport mode trunk" command (if it's a Cisco 9300, the dot1q command is not necessary).
it's B, default state on all ports is Auto, you can't configure to switchport mode trunk directly, cause you need to change the encapsulation mode to dot1Q. This way is not given here, so you have to choose : Switch(config-if)#switchport mode dynamic desirable
Here is the output if you start with Answer A
Command rejected: An interface whose trunk encapsulation is "Auto" can not be configured to "trunk" mode.
This is true assuming the new switch support both dot1q and ISL as a trunking protocol, but since we don't know the new switch model, we have to assume the new switch is the same model of cat9300-1 which support just 802.1q, therefore we are forced to choose A in the context of the exam.
I choose the letter A. The trunk negotiation is enabled, however as we have "Switchport Mode Trunk", static mode configured, for best practices I believe that keeping the trunk statically on the other side would be more adequate and consistent. For example, a technician could disable negotiation on the static side by mistake (with "switchport nonegotiate") and the other side with dynamic negotiation would lose trunk mode negotiation. Therefore, I believe that static mode would be better with static mode (On/On) or dynamic mode with dynamic (Desirable/Auto) would also be best.
A and B are both correct. Negotiation of trunking is on, so the trunk will form for trunk, dynamic auto or dynamic desirable option set on the other end of the link. Anyway, I would probably choose answer B at the exam (but I hope that the question at the exam is more clear)
This section is not available anymore. Please use the main Exam Page.200-301 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
oatmealturkey
Highly Voted 2 years, 2 months agoaskar430
1 year, 2 months agoRich_rude
1 year agoJoshua25
Most Recent 6 months, 1 week agoadrianspa
8 months, 2 weeks agoexiledwl
7 months, 2 weeks agoexiledwl
7 months, 2 weeks ago[Removed]
1 year, 1 month agoaskar430
1 year, 2 months agoRich_rude
1 year agoFranRig
1 year, 3 months agoFranRig
1 year, 3 months ago1stAid
1 year, 3 months agoNmk3216
1 year, 5 months ago[Removed]
1 year, 7 months agomarle77
1 year, 7 months agoRick3390
1 year, 5 months agoAndreaGambera
1 year, 8 months agoNetworkGeek00
1 year, 9 months agodropspablo
1 year, 10 months agonzjobhunt
2 years agoPeter_panda
2 years agoCiscoman021
2 years, 1 month agoRynurr
2 years, 2 months ago