Which sequence creates a DHCP pool named dhcp_pool for 192.168.1.100-192.168.1.200 and a DHCP server using that pool with gateway 192.168.1.1 on interface bridge1?

• A. /ip pool add name=dhcp_pool ranges=192.168.2.100-192.168.2.200; /ip dhcp-server add name=dhcp1 address-pool=dhcp_pool gateway=192.168.1.1 interface=bridge1
• B. /ip pool add name=dhcp_pool ranges=192.168.1.50-192.168.1.150; /ip dhcp-server add name=dhcp1 address-pool=dhcp_pool gateway=192.168.1.1 interface=bridge1
• C. /ip pool add name=dhcp_pool ranges=192.168.1.100-192.168.1.200; /ip dhcp-server add name=dhcp1 address-pool=dhcp_pool gateway=192.168.1.1 interface=bridge1
• D. /ip pool add name=dhcp_pool ranges=192.168.1.100-192.168.1.200; /ip dhcp-server add name=dhcp1 address-pool=dhcp_pool

Answer: (C)

Configuring a DHCP server in RouterOS starts with defining an IP pool of addresses to hand out to clients, then creating a DHCP server that uses that pool and supplies the network gateway while binding to the correct interface. The pool must reside in the same subnet as the gateway and the interface serving clients. In this case, the pool is created with the exact range 192.168.1.100 through 192.168.1.200, which belongs to the 192.168.1.0/24 network. The DHCP server is then set to use that pool, with the gateway 192.168.1.1 (the router’s address on that network), and bound to bridge1 so it serves clients on that bridge. This combination ensures the offered addresses are within the requested range, the default gateway is correctly provided, and DHCP traffic is handled on the right interface.

The other options fail because they either define a pool in a different subnet (192.168.2.x), use a different range within the same subnet, or omit binding the DHCP server to the correct interface, which would prevent devices on bridge1 from obtaining addresses.