A.PE-1 must be configured with mesh-SDPs to every node receiving the multicast traffic. There is no way to reduce the replication or bandwidth.

B.PE nodes in Metro 1 could be configured with mesh-SDPs. PE nodes in Metro 2 would be configured with mesh-SDPs. However, the connection between Metro networks (PE-2 to PE-6) can be configured with a spoke-sdp. This would reduce the replication and bandwidth used on the link between Metro networks. This also reduces the replication required by PE-1.

C.PE nodes in Metro 1 could be configured with spoke-SDPs. PE nodes in Metro 2 would be configured with spoke-SDPs. However, the connection between Metro networks (PE-2 to PE-6) can be configured with a mesh-sdp. This would reduce the replication and bandwidth used on the link between Metro networks. This also reduces the replication required by PE-1.

D.PE-1 can be configured with spoke-SDPs to every PE node in both Metro networks. This will reduce the bandwidth and replication within the network.

A.MPLS for exchanging labels with the CE devices

B.A label signaling protocol for defining transport tunnels between PE and CE devices

C.MPLS for exchanging labels with other provider core devices

D.A routing protocol for exchanging customer routes with the CE

E.MP-BGP for exchanging customer routes with other PEs

F.Targeted LDP for exchanging VPRN labels with other PE devices

A.Show service id <service-id> base

B.Show router <service-id> status

C.Show service id <service-id> maximum-routes

D.Show router bgp <service-id> routes

A.The routes learned from CE3 and PE2.

B.The routes learned from CE3 and PE1.

C.The routes learned from PE1 and PE2.

D.The route learned from CE3 only.

A.Bridge C 1/1/2

B.Bridge B 1/1/2

C.Bridge C 2/1/1

D.Bridge E 1/1/1

E.Bridge D 1/1/3

F.Bridge E 1/1/3

G.Bridge D 1/1/1

H.Bridge B 1/1/3