An engineer must avoid routing loops on the SD-WAN fabric for routes advertised between data center sites. Which BGP loop prevention attribute must be configured on the routers to meet this…

Static routing avoids BGP loops but does not address BGP-specific loop prevention attributes, which is what the question asks for.

When all Customer Edge (CE) and Provider Edge (PE) routers that exchange BGP routes across data centers belong to the same BGP AS, they function as Internal BGP (iBGP) peers. The iBGP split-horizon rule, a fundamental BGP loop prevention mechanism, prevents an iBGP router from advertising a route learned from one iBGP peer to another iBGP peer, thereby avoiding routing loops within that AS.

OMP overlay-as is a loop prevention attribute for the Overlay Management Protocol (OMP), not specifically for BGP routing loops as requested in the question.

The configuration of the same BGP AS between WAN Edge routers and their directly connected CE routers describes local peering, but doesn't inherently prevent routing loops for routes advertised *between* data center sites without further context or architectural assumptions.