Which RouterOS command configures a PPPoE client on interface ether1 with username and password and adds a default route?

• A. /interface pppoe-client add interface=ether1 user="user" password="pass" add-default-route=yes
• B. /interface pppoe-client add interface=ether1 user="user" password="pass"
• C. /interface pppoe-client add interface=ether1 user="user" password="pass" add-default-route=no
• D. /interface pppoe-client add interface=eth0 user="user" password="pass" add-default-route=yes

Answer: (A)

Starting a PPPoE client in RouterOS involves tying the PPPoE session to a specific physical interface, providing the authentication, and deciding whether to create a default route so internet traffic flows through that connection. The command that uses the correct interface (ether1), supplies the user and password, and automatically creates a default route is the one that establishes the PPPoE session and directs all internet-bound traffic through it by default. This is what makes the router immediately usable for internet access via the PPPoE link.

Using the same command but without adding a default route means the PPPoE session would be established, but there wouldn’t be an automatic 0.0.0.0/0 route via that interface, which might require additional manual routing. Setting add-default-route to no explicitly prevents automatic default routing, which is less common when you want a straightforward internet path. Specifying a different interface name (for example, eth0) would connect the PPPoE client to the wrong physical port, so the session would not attach to the intended link.