4A0-106 Practice Exam Questions with Answers Nokia Virtual Private Routed Networks Certification

It will label switch the packet based on this label

It will decrement the TTL and label switch the packet based on this label

It will SWAP the label for a new label and then label switch the packet

The P router does not perform any operation on this label

A single routing protocol for exchanging routes with both the internal customer routers and with the PE

MP-BGP to exchange routes with the PE.

MPLS and a routing protocol for the exchange of labels and routes with the PE

MPLS for exchanging labels with other CE devices

A routing protocol for exchanging routes with the internal customer routers and a routing protocol for exchanging routes with the PE

One Route Distinguisher per VRF route

One Route Distinguisher per VRF

One Route Distinguisher per VRF per site

One Route Distinguisher per VPN

True

False

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

Allow routes to be exchanged between all or selected sites of one VPRN and all or selected sites of a second VPRN

Allow the service provider to provide multiple VPRNs with Internet access

Reduce the number of VPRN tunnels required

Simplify the administration of multiple VPRNs

Force all traffic in multiple VPRNs to pass through a single device

Traditional BGP loop detection mechanisms may detect a loop in the VPRN scenario, which in fact is not present.

The Nokia 7750 SR accepts routes containing AS_PATH loops by default.

When the CLI command "config>router>bgp# loop-detect discard-route" is used, the Nokia 7750 SR sends a notification to the remote peer and drops the BGP session.

In VPRN implementations where the CE-PE protocol is BGP, it is possible for separate sites of the same customer to use the same BGP autonomous system number.

P devices participate in service provider core routing.

P devices are not required to be MPLS-enabled.

P devices must be aware of the VPRNs.

P devices must support MP-BGP.

ample Policy should be applied as an export policy on the PE connected to the main site of Customer 1

ample Policy 3 should be applied as an export policy on the PE connected to the main site of Customer 2

ample Policy 3 should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on both PEs connected to the main site of Customer 1 and the main site of Customer 2

ample Policy should be applied as an export policy on all PEs connected to sites of Customer 1

Distributing customer routing information between sites

Forwarding customer data packets

Providing an integrated billing solution

Maintaining separation between distinct customer networks

Allowing the implementation of Layer 3 devices in the provider core

PE1

RR1

ASBR1

ASBR2

A full mesh VPRN

APE hub and spoke VPRN

An extranet VPRN

ACE hub and spoke VPRN

Target:65100:2 and target:65100:3

Target:65100:1 and target:65100:2

Target:65100:1 and target:65100:3

Target:65100:1, target:65100:2 and target:65100:3

Five routes: the local route, the two BGP routes learned from the local CE, and two tunneled routes.

Six routes: the local route, the two BGP routes learned from the local CE, and three tunneled routes.

Two routes: the local route and one tunneled route.

Three routes: the local route and two tunneled routes.

Two routes: the local route and one BGP route learned from the local CE.

target:65100:2 and target:65100:3

target:65100:1 and target:65100:2

target:65100:1 and target:65100:3

target:65100:1, target:65100:2 and target:65100:3

PE1 pushes three labels on the IP packet: a VPN label, a BGP label, and an LDP transport label.

ASBR1 pops the LDP label, swaps the BGP label and forwards the IP packet to ASBR2.

ASBR2 swaps the BGP label and pushes an LDP transport label.

PE2 pops all labels and forwards the unlabeled packet to its destination.

show router 10 bgp routes vpn-ipv4

show router bgp routes

show router bgp routes vpn-ipv4

show router route-table

Based on the interface on which they are received.

Based on the Route Distinguisher.

Based on the Route Target.

Based on the Service Identifier.

Red VRF imports only "Internet"

Internet VRF imports only "Red-Only"

Red VRF imports "Internet" and "Red-Only"

Internet VRF imports only "Red-Only"

Red VRF imports only "Red-Only"

Internet VRF imports "Red-Only" and "Internet"

Red VRF imports "Internet" and "Red-Only"

Internet VRF imports only "Internet"

The routes learned from CE3 and PE1.

The route learned from CE3 only.

The routes learned from PE1 and PE2.

The routes learned from CE3 and PE2.

It requires the configuration of back-to-back VRFs between ASBR routers in different autonomous systems

It is the most scalable of the Inter-AS models.

Most routers that support VPRN functionality support model A by default.

It uses conventional eBGP to distribute unlabeled IPv4 routes between ASBR routers in different autonomous systems.

Creating an export policy on CSC-CE1 and CSC-CE2 to advertise local PE addresses to the network provider.

Configuring eBGP between CSC-CE and CSC-PE routers; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring iBGP between PE and CSC-CE within each customer carrier site; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring MP-iBGP between PE1 and PE2; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

The VPRN ID must match the value used in the vrf-target command.

The VPRN ID must match the value used in the route-distinguisher command.

The router-id command should not be used in this context.

The "no shutdown" command must be configured for the VPRN to be operationally UP.

The customer carrier does not learn any network provider routes.

The network provider must learn the customer carrier PE and CE system addresses.

Routes exchanged between CSC-CE and CSC-PE are labeled.

The customer carrier PE system addresses are populated in the CSC VRF.

The customer carrier network can be a pure IP network.

The customer carrier can provide Layer 2 and Layer 3 services to its end-customers.

If the customer carrier offers VPRN services, PE routers residing in different customer carrier sites must run iBGP between them to exchange IPv4 routes.

If the customer carrier offers VPRN services, the network provider stores the end-customer routes in its CSC VPRN.

"Blue-Only"

"Blue-Only" and "Blue-Green"

"Green-Only"

"Extranet-VPN-Green"

"Blue-Green"