An IP packet contains two critical IP addresses in its header:
Source IP address – the IP of the sending host
Destination IP address – the IP of the receiving host
These addresses allow routers to forward the packet from source to destination over Layer 3 (Network Layer).
Other values in the IP header include TTL, protocol type, and checksum — but not additional IP addresses.
A. 4 →❌Incorrect. Only 2 IPs are included
B. 2 →✅Correct: Source and Destination
C. 3 →❌Some protocols like NAT may temporarily associate more addresses, but not in header
D. 1 →❌Incomplete
MTCNA Course Manual – IP Packet Structure:
“An IP packet always contains a source and destination IP address in the Layer 3 header. This allows routing to function across networks.”
René Meneses Guide – Packet Flow:
“IP headers are designed to carry the minimal information necessary for routing. That includes the source and destination IPs.”
Terry Combs Notes – Header Fields:
“Two IPs: one for sender, one for receiver. That’s all you’ll find in the IP header.”
Answer: BQUESTION NO: 21 [Routing]
When viewing the routes in Winbox, some routes will show "DAC" in the first column. These flags mean:
A. Dynamic, Active, Console
B. Dynamic, Active, Connected
C. Direct, Available, Connected
D. Dynamic, Available, Created
Answer: B
MikroTik’s RouterOS assigns flags to routing table entries to describe how they were created and their status.
D = Dynamic (added automatically by the system)
A = Active (currently used by RouterOS)
C = Connected (directly connected subnet or interface)
Thus, "DAC" means:
→ Dynamic, Active, Connected✅
Other flags that may appear include:
MTCNA Course Manual – Routing Flags:
“DAC means that the route is dynamically added by the system, is currently active, and is directly connected to the device.”
René Meneses MTCNA Guide – Routing Table Interpretation:
“Flags help identify how the route was installed and its type. DAC is common for directly connected interfaces.”
Terry Combs Notes – Route Flags Table:
“DAC = Dynamic + Active + Connected. Usually appears after setting IP address on interface.”
Answer: BQUESTION NO: 22 [RouterBOARD Hardware]
In which situations Netinstall can not be used to install RouterOS on a RouterBOARD?
A. The router is connected only to a secondary Ethernet port
B. The router does not have an operating system
C. The router is connected only to a wireless network
D. The password of the router is not known
Answer: C
Netinstall is a MikroTik utility used to reinstall or upgrade RouterOS. It requires a direct Ethernet connection to the router’s first Ethernet port and works via PXE (boot over Ethernet). It cannot function over wireless.
Let's review the options:
A. The router is connected only to a secondary Ethernet port →❌Netinstall works if booted over that port
B. The router does not have an operating system →❌This is the purpose of Netinstall
C. The router is connected only to a wireless network →✅Correct: Netinstall requires a wired Ethernet connection
D. The password of the router is not known →❌Netinstall bypasses current OS; password irrelevant
MTCNA Course Manual – RouterBOARD Recovery and Netinstall:
“Netinstall must be done over a wired Ethernet connection. Wireless booting is not supported.”
René Meneses Guide – System Recovery:
“Netinstall needs Layer 2 communication via Ethernet. It cannot operate over Wi-Fi.”
Terry Combs Notes – Netinstall Limitations:
“Netinstall does not support Wi-Fi. Must connect via Ethernet to first interface, preferably.”
Answer: CQUESTION NO: 23 [DHCP]
DHCP server is configured on a router’s ether1 interface. IP address 192.168.0.100/24 is assigned to the interface. Possible IP pools, that can be used by this DHCP server, are:
A. 192.168.0.1–192.168.0.255
B. 192.169.0.1–192.169.0.254
C. 192.168.0.1–192.168.0.99, 192.168.0.101–192.168.0.254
D. 192.168.0.1–192.168.0.14
Answer: C
The router’s interface IP is 192.168.0.100/24 → which belongs to the subnet 192.168.0.0–192.168.0.255.
However, 192.168.0.100 is already assigned to the router. So, this IP must be excluded from the DHCP pool to avoid conflicts.
Let’s evaluate other options:
A. 192.168.0.1–192.168.0.255 →❌Includes broadcast (.255) and router IP (.100) → Invalid
B. 192.169.0.1–192.169.0.254 →❌Completely wrong subnet
D. 192.168.0.1–192.168.0.14 →✅Valid but unnecessarily small
MTCNA DHCP Chapter – Address Pools:
“Make sure the pool does not include the router’s IP or the network’s broadcast address. Common errors involve overlapping pools.”
René Meneses MTCNA Guide – DHCP Configuration:
“Exclude the router’s own IP from the range. Use address pools below and above the assigned IP.”
Terry Combs Notes – DHCP Pool Tips:
“Split the pool to avoid assigning the interface IP to clients. Also avoid .0 and .255.”
Submit