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

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

CSC-CE1 pops the LDP label and swaps the BGP label.

CSC-PE1 pops the BGP label, swaps the VPN label, and pushes an LDP transport label.

CSC-PE2 pops the LDP and VPN labels and pushes a BGP label.

It forwards the packet based on the label signaled by MP-BGP.

It decrements the TTL and forwards the packet based on the inner label.

It swaps the outer label then forwards the packet.

The P router does not perform any operations on labeled packets.

Open

Update

Route Refresh

Notification

64491 {64492 64493}

64491

64492 64493 64491

{64492 64493)64491

The primary VRF on PE1 contains routes learned from spoke sites.

All traffic between spoke sites must pass through CE1.

The secondary VRF on PE1 is used to route data packets from the hub CE to the spoke sites.

PE1 advertises the primary VRF routes to CE1.

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

The route update sent from PE1.

The route update sent from PE2.

The route update sent from ASBR1.

The route update sent from ASBR2.

Signaled via MP-BGP and used to identify the egress PE.

Signaled via T-LDP and used to identify the customer VPRN.

Signaled via MP-BGP and used to identify the customer VPRN.

Signaled via RSVP and LDP and used to identify the egress PE.

Signaled via RSVP and LDP and used to identify the customer VPRN.

“Spoke_Sites”

“Hub_Site”

“Spoke_Sites” and “Hub_Site”

No communities should be imported.

PE2 pushes one label on the IP packet and forwards it to ASBR2.

ASBR2 sends the IP packet with one label to ASBR1.

ASBR1 sends the IP packet with one label to PEL

PE1 pops one label off the IP packet and forwards it to CE1.

Each PE must implement a policy to apply a unique SoO attribute to the set of routes received from each customer site.

A different BGP extended community is used on each PE that connects to a single site.

An import policy on the PE rejects a route if the attached SoO matches the configured value.

Import and export policies are applied on the PEs under the global BGP context.

The route with the shortest AS path.

The route with the lowest route or tunnel table cost to the NEXT_HOP.

The route with the highest local preference.

The route with the lowest originator ID or BGP identifier.

the configuration is complete and correct.

'as-override' should be configured under the BGP context.

'as-override' should be configured under the group context.

'as-override' should not be part of this configuration.

64496 64497

64496

64497

64497 64497

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.

The customer carrier network must be MPLS-enabled.

VPRN instances are created on the CSC-CE routers.

All traffic exchanged between end-customers is carried over a single CSC VRF.

Customer carrier PEs residing in different sites must run MP-iBGP between them to exchange customers' routes.

Three route targets and three route distinguishers

Five route targets and three route distinguishers

Three route targets and two route distinguishers

Five route targets and two route distinguishers

Full mesh of MP-BGP between all P devices

Full mesh of MP-BGP between PE devices

Route reflector configuration between PE devices

Confederation configuration between PE devices

"Extranet-VPN-Blue" and "Extranet-VPN-Green"

"Blue-Only"

"Extranet-VPN-Blue"

"Blue-Green"

This command is required on all PE routers to distribute labeled IPv4 routes directly to PEs in remote AS.

This command is required on the ASBRs to exchange labeled IPv4 routes between the ASs.

This command is required on the route reflectors to exchange customer routes between ASs as labeled IPv4 routes.

This command is required on all PE routers to distribute labeled IPv4 routes to connected CEs.

On the PE facing the CE neighbor

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

Resources consumed at the sender and receiver PEs can be reduced by using BGP ORF.

BGP ORF allows a receiving PE to filter out unnecessary inbound routes.

A PE indicates its ORF capabilities to its neighbor PE in a BGP Open message.

BGP ORF is most effective when a large number of routes is being exchanged between two peers, and most routes are filtered out on arrival.

ASBRs exchange labeled IPv4 routes for the system addresses of PE routers.

It requires a route reflector to be configured in each AS for successful operation.

VPN-IPv4 routes are neither maintained nor distributed by the ASBRs.

PE routers in different ASes exchange VPN-IPv4 routes directly between each other using MP-eBGP.

The neighbor shown is an ASBR router.

The address family between the peers should be VPN-IPv4 instead of IPv4.

The neighbor address cannot be the interface address 10.3.4.4.

The omitted AS number under "BGP summary" must be equal to 64496.

Based on the interface on which they are received.

Based on the Route Distinguisher.

Based on the Route Target.

Based on the Service Identifier.

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.

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.

"Spoke.Sites" and "Hub_Site"

"Spoke_Sites"

"Hub_Site"

No communities should be exported

The update is accepted and the route installed in the route table.

The update is accepted but the route will not be installed in the route table

The update is rejected

The peer session is dropped

Configuring iBGP sessions between PEs residing in different customer carrier sites,

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring a CSC VPRN on each CSC-PE with a SAP interface towards the attached CSC-CE.

Configuring an IES service on PEL

Static

RIP

OSPF

IS-IS

MP-BGP

BGP

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

PE2 pushes one label on the IP packet and forwards it to ASBR2.

ASBR2 forwards the IP packet with one label to ASBR1.

ASBR1 forwards the IP packet with two labels to PEL

PE1 forwards an unlabeled IP packet to CE1.

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

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

One Route Distinguisher per VRF route

One Route Distinguisher per VRF

One Route Distinguisher per VRF per site

One Route Distinguisher per VPN

ASBR1# show router 10 bgp routes vpn-ipv4

ASBR1# show router bgp routes

ASBR1# show router bgp routes vpn-ipv4

ASBR1# show router route-table

This is the base routing table from CE-1

This is the base routing table from PE-1

This is the customer vrf from CE-1

This is the customer vrf from PE-1D.This is the customer vrf from PE-1

This is the customer vrf from PE-2E.This is the customer vrf from PE-2E.This is the customer vrf from PE-2

This is the base routing table from PE-2F.This is the base routing table from PE-2F.This is the base routing table from PE-2

This is the base routing table from CE-2G.This is the base routing table from CE-2G.This is the base routing table from CE-2

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

A 32 bit IPv4 address followed by a 64 bit Route Target

A 32 bit IPv4 address followed by a 64 bit Route Distinguisher

A 64 bit Route Target followed by a 32 bit IPv4 address

A 64 bit Route Distinguisher followed by a 32 bit IPv4 address

A 32 bit Route Distinguisher followed by a 32 bit IPv4 address FA 32 bit Route Target followed by a 32 bit IPv4 address

The PE will install a maximum of 40 prefixes into the customer vrf and generate a log message when 40 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, and generate a log message both when 30 and 41 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and disable learning of new routes at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and drop the connection at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 4 routes are received and disable learning of new routes at 41

When sites of different VPRN customers use the same BGP AS number

When sites of the same VPRN customer use the same BGP AS number

When sites of different VPRN customers use different BGP AS numbers

When sites of the same VPRN customer use different BGP AS numbers

When the customer site AS number is the same as the provider AS number

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

To limit the number of routes advertised from a customer site

To limit the number of routes learned from other customer sites CTo limit the size of the VRF table

To limit connectivity to selected customer networks

To perform packet filtering

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.

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000

192.168.10.1

192.168.20.1

10.10.10.1

10.10.10.6

It is an 8 byte value containing 3 fields

The Route Distinguisher must have the same value as the Route Target.

The Administrator field contains either an AS number or an IP number

To ensure uniqueness, Route Distinguishers are assigned by the IANA.

The Route Distinguisher is not used if the customer addresses do not overlap

The Assigned Number field must contain a public IP address

Family vpn-ipv4

Family vprn-ipv4

Family vprn

Address-family vpn-ipv4

Address-family vprn-ipv4

Address-family vprn

CE1 forwards the data packet to PE1 via the VPRN 20 interface.

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

CSC-CE1 pops the LDP label and swaps the BGP label.

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

To reduce the number of VPRN tunnels required.

To allow routes to be exchanged between all, or selected, sites of one VPRN, and all, or selected, sites of a second VPRN.

To simplify the administration of multiple VPRNs.

To allow network access between the headquarter sites of each VPRN service and a shared VPRN service offered by a third party.

The SoO attribute can be used to uniquely identify the site from which a PE learns routes.

Before a PE redistributes a VPN-IPv4 route, it can assign an SoO attribute to the route.

The SoO attribute can be used to prevent loops from a single site with multiple CE-PE connections.

The SoO attribute can be used as matching criteria when redistributing routes from the CE to the PE.

1

3

5

7

10

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.

Show router bgp routes

Show router bgp routes address-family vpn-ipv4

Show router bgp routes

Show router bgp routes

Identify the egress PE in the MPLS domain

Signal the egress VPRN ID

Identify the ingress PE in the MPLS domain

Transport route updates between PEs

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

VRF configuration is not required on the ASBRs.

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

It is not necessary to run MPLS at the boundary between autonomous systems.

PE1

RR1

ASBR1

ASBR2

The AS-Path is not present because a policy is configured on PE2 to set it to null.

The AS-Path is not present because a policy is configured on CE1 to set it to null.

The AS-Path is not present because a policy is configured on PE1 to set it to null.

The AS-Path is not present because VPN-IPv4 routes do not propagate the IPv4 AS-Path BGP attribute.