The default Routerboard configuration should be fine: 1x WAN port (on Eth1) and 4x LAN ports (on Eth2 - Eth5)
The WAN port will use a DHCP-client and the LAN ports will host a DHCP server.
Yes that will work, but it means the device connected to the ADSL line is running as an IP router. Many IP layer functions such as PPPoE session mgmt, outbound NAT, inbound port forwarding, DDNS etc are being performed by that router.
Kinda defeats the point of having an advanced, feature rich router like the Mikrotik RB. Ideally you'd want the RB to handle all the PPPoE session & IP layer functions, with the ADSL connected device acting as a dumb modem, who's sole purpose is bridging packets between its ADSL & Ethernet interfaces.
Traditionally if you were using the RB as the PPPoE client, it would be configured on a seperate physical (WAN) inf to the LAN one. This introduces a problem when you wish to access the ADSL modem's mgmt IP (say to check your ADSL stats). You could add a 2nd subnet on the WAN/PPPoE inf but most ADSL modems/routers in bridge mode by default only allow access to the mgmt IP from the local subnet, which the LAN is not on, so you're going to have to add NAT to the WAN inf. Its all starts getting very messy.
By running the LAN routing & PPPoE infs on the same physical inf, you circumvent all these complications. An added bonus is, if the ADSL modem has WiFi, it will seamlessly work on the LAN subnet.