Which command correctly creates a VLAN interface named vlan10 with vlan-id 10 on bridge1?

Prepare for the MikroTik Certified Network Associate Exam. Enhance your skills with diverse modules, adaptive quizzes, and detailed explanations. Ace your certification with confidence!

Multiple Choice

Which command correctly creates a VLAN interface named vlan10 with vlan-id 10 on bridge1?

Explanation:
Creating a VLAN interface on RouterOS is done by adding a VLAN sub-interface on a chosen parent interface, using the add operation with three key pieces: the new interface’s name, the VLAN ID to tag, and the parent interface it sits on. The parent determines where the VLAN traffic will be processed or forwarded. Here, the VLAN should be part of bridge1, so the parent is bridge1. The VLAN ID is 10, which is a valid tag (1–4094), and the interface is named vlan10. Using /interface vlan add with name=vlan10, vlan-id=10, interface=bridge1 creates exactly that VLAN interface on top of the bridge, so frames tagged 10 can be handled by the bridge. The other approaches aren’t correct for this scenario: attaching to a physical port like ether1 would place the VLAN on that port rather than on the bridge, which isn’t what’s asked. Using a VLAN ID of 101 is simply a different tag, not 10. And using create instead of add isn’t valid RouterOS syntax for adding a VLAN interface.

Creating a VLAN interface on RouterOS is done by adding a VLAN sub-interface on a chosen parent interface, using the add operation with three key pieces: the new interface’s name, the VLAN ID to tag, and the parent interface it sits on. The parent determines where the VLAN traffic will be processed or forwarded.

Here, the VLAN should be part of bridge1, so the parent is bridge1. The VLAN ID is 10, which is a valid tag (1–4094), and the interface is named vlan10. Using /interface vlan add with name=vlan10, vlan-id=10, interface=bridge1 creates exactly that VLAN interface on top of the bridge, so frames tagged 10 can be handled by the bridge.

The other approaches aren’t correct for this scenario: attaching to a physical port like ether1 would place the VLAN on that port rather than on the bridge, which isn’t what’s asked. Using a VLAN ID of 101 is simply a different tag, not 10. And using create instead of add isn’t valid RouterOS syntax for adding a VLAN interface.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy