Pass the Nokia SRC Certification 4A0-C02 Questions and answers with ExamsMirror

In the CSC VPRN, configure an eBGP session between CSC-PE and CSC-CE and use the "advertise-label vpn-ipv4" CLI command to enable the advertisement of VPN-IPv4 routes.

When the customer carrier uses the same autonomous system number in various sites, use the "loop-detect off" CLI command to disable the loop detection functionality on CSC-CE and PE routers.

On the CSC-PE routers, use the "carrier-carrier-vpn" CLI command to configure the VPRN service as CSC.

Configure an iBGP session between PE1 and PE2 and use the "family vpn-ipv4" CLI command to directly exchange end-customer routes learned from CE1 and CE2.

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

The LDP identifier

The Service identifier

The Route Target

The Route Distinguisher

The tunnel label

This configuration is correct and complete.

This configuration is correct, except that the system interface must be added.

This configuration is correct, except that the interfaces facing the CE routers must be added.

MPLS configuration is not required.

PE1

RR1

ASBR1

ASBR2

MP-BGP for exchanging customer routes with other PEs

A routing protocol for exchanging customer routes with the CE

MPLS for exchanging labels with other provider core devices

MPLS for exchanging labels with the CE devices

Targeted LDP for exchanging VPRN labels with other PE devices

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

When the route is first received at the P from the PE

When the route from the CE is populated into the VRF at the PE

When the route from the PE is populated into the VRF at the CE

When the route is propagated from the PE to the CE

When the route is exported into the MP-BGP table from the VRF

RR2 advertises the VPN-IPv4 route update of 192.2.1.0/27 to RR1

RR1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR2

RR2 advertises the VPN-IPv4 route update of 192.1.1.0/27 to PE2

PE1 advertises the VPN-IPv4 route update of 192.1.1.0/27 to RR1 and ASBRL

No need to build and maintain its own backbone.

The solution scales as the number of serviced customer carriers increases.

The solution scales as the number of VPNs offered by the customer carriers increases.

The ability to manage end-customer services.

Participate in service provider core routing

P devices are not required to be MPLS enabled. MPLS is only required on the PE devices

Run a common routing protocol with the CE router

Must support MP-BGP

Do not have any connections to the CE

Must be aware of the VPRNs

CSC does not allow a customer carrier to offer Layer 2 services to its end customers.

A CSC VPRN is configured on the network provider's CSC-PE routers.

CSC eliminates the need for customer carriers to build and maintain their own MPLS backbone.

The network provider provides an MPLS VPN backbone to the customer carrier.

PE1 pushes an LDP transport label.

CSC-PE1 pops the BGP label and pushes two labels: a VPN label and an MPLS transport label.

CSC-PE2 pops the MPLS transport label and pushes a BGP label.

CSC-CE2 pops the BGP label and pushes an LDP transport label.

An MP-BGP update carries an MPLS label that is used as the service label for a VPRN.

There can be multiple Route Targets per route in an MP-BGP update.

There can only be one Route Distinguisher per route in an MP-BGP update.

On a specific PE, the MP-BGP updates for prefixes from a single VPRN carry different labels.

Traditional BGP attributes and MP-BGP attributes are present in an MP-BGP update.

CE2 forwards an unlabeled IP packet to PE2 via the VPRN interface.

PE2 pushes two labels on the IP packet and label-switches the packet to ASBR2.

ASBR2 pops one label from the IP packet and label-switches it to ASBR1.

ASBR1 pushes two labels on the IP packet and label-switches the packet to PEL.

The Route Target is added to an IPv4 route to create the VPN-IPv4 route.

The Route Target is an extended community string that identifies VPN membership.

A route can have only one Route Target.

The Route Target is a 64-bit value added to customer prefixes to make them unique.