A wastewater plant edge PE must offer civic Internet exit for one VRF’s users. Which design choice correctly frames Internet in a VRF versus the global routing table?
Select an answer to reveal the explanation.
Short Explanation
Internet-in-VRF versus global-table exit is a deliberate architecture fork: keep the default inside a services VRF, or leak carefully to/from global. Neither is magic — pick based on isolation, ops ownership, and how much Internet state you want in the VRF. P routers are not your Internet PE.
Full Explanation
Operators choose whether civic Internet is carried inside a VRF (often a shared Internet or services VRF with RT import) or handed off via the global routing table with controlled leaking between VRF and global. That choice affects isolation, default-route scope, and troubleshooting boundaries. P routers do not host the Internet edge for customer VRFs, PHP does not depend on importing the full Internet, and identical RTs collapse separation. Document which model the wastewater edge uses and leak only what policy allows.