A municipal hospital campus needs a joint city-county CMDB application to reach a shared prefix that must remain in both the clinical VRF and the county-admin VRF without merging the rest of those tables. What MPLS L3VPN mechanism enables that controlled sharing?
Select an answer to reveal the explanation.
Short Explanation
Picture two locked file cabinets that need one shared drawer for the CMDB. Route targets are the keys you copy for just that drawer — not a master key that opens everything. Extranet-style RT import/export leaks only the agreed prefix between VRFs.
Full Explanation
MPLS L3VPN isolation is driven by route targets, not by forcing VRFs to share an RD or collapsing into the global table. For a joint city-county CMDB prefix, each VRF exports (and the peer imports) an RT that carries only that route, which is the classic extranet leak pattern. Identical RDs defeat uniqueness in MP-BGP, and P routers must stay VRF-unaware. Keep the rest of each VRF private while selectively sharing the CMDB prefix.