A customer requests that sites are connected over an MPLS backbone using the MPLS AToM service. However, the network engineer advises that the MPLS L3VPN service may be better for this situation…

From a Service Provider's perspective, MPLS L3VPN reduces operational complexity by allowing PE routers to handle customer routing via VRFs, rather than simply transporting Layer 2 frames (as with AToM). This centralizes routing intelligence on the SP's equipment, simplifying customer network integration, scaling, and policy management.

While MPLS L3VPN primarily focuses on IP, MPLS AToM is generally more versatile for supporting a wider range of Layer 2 protocols that might encapsulate legacy network layer protocols like IPX or SNA, making this not a strong advantage for L3VPN.

Maintaining customer Layer 2 information over the SP core is a characteristic feature of MPLS AToM (Layer 2 VPN), not MPLS L3VPN, where Layer 2 is terminated at the PE router.

Both AToM and L3VPN aim to be transparent to the customer in different ways (Layer 2 for AToM, Layer 3 for L3VPN), so this is not a unique advantage that makes L3VPN inherently 'better' in terms of SP operational complexity.