A regional planning commission wants clinic spoke sites to reach only a central hub VRF, not each other, over an MPLS L3VPN. How should route-target import and export be arranged?
Select an answer to reveal the explanation.
Short Explanation
Hub-and-spoke is like a star-shaped mail room: clinics drop mail tagged for the hub, and only the hub’s tag gets into clinic inboxes. Matching export/import RTs that way blocks clinic-to-clinic shortcuts. One shared RT for everyone is full mesh — the opposite of what you want.
Full Explanation
VPN topology is shaped by which RTs each VRF exports and imports. For hub-and-spoke clinics, spokes export a spoke-only RT imported solely at the hub, and the hub exports a hub RT imported at the spokes — spokes do not import each other’s RT. A single mutual RT yields full mesh. P routers never rewrite customer RTs, and wild-card imports at the hub would over-accept routes. Align RT policy with the intended hub-spoke graph.