Which of the following about VPRN VRF tables is FALSE?

The statement that P routers use VRF tables is false. P (Provider) routers in an MPLS VPN core are responsible for label switching based on the outer (transport) label only. They have no knowledge of customer VPNs, VRF tables, or the inner (service) label. This design principle keeps the core simple and scalable, as customer-specific state is maintained only at the network edge on the PE (Provider Edge) routers. PE routers maintain VRF tables to provide routing and forwarding separation for each customer's VPRN service.

A. This is true. PE routers use MP-BGP to advertise VPN routes, which includes VRF-specific information like the Route Distinguisher and Route Targets.
B. This is true. The VRF on a PE router contains the specific routes needed to forward traffic towards the attached CE (Customer Edge) devices for that VPN.
D. This is true. The primary function of a VRF is to create a separate, isolated virtual routing and forwarding instance for each customer on a PE router.

1. Nokia 7750 SR OS Services Architecture Guide, Release 22.10.R1, "VPRN Service Overview" section. This section details that VRFs exist on PE routers to maintain per-customer routing information and that P routers are not customer-aware.

2. Nokia 7750 SR OS MPLS Guide, Release 22.10.R1, "MPLS Label Stack" section. This guide explains the roles of P and PE routers, clarifying that P routers only process the top label (transport label) and are unaware of the service label or its associated VRF.

3. RFC 4364, "BGP/MPLS IP Virtual Private Networks (VPNs)", Section 2, "Overview". This foundational RFC states that "P-routers... do not maintain any VPN routing information."