Free 4A0-106 Exam Dumps Preview

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PE1.

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

Memory exhaustion in the provider core

CPU utilization for route processing

The As-Path is not present as it was removed with the s-override configuration command

The As-Path is not present as it was removed with the o-as-path configuration command

The As-Path is not present as VPN-IPv4 routes do not propagate the IPv4 As-Path BGP attribute

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.

The SDP path-MTU minus 14

The configured service-mtu of the VPLS service

The LMTU found in how router ldp bindings on the VPLS side of the spoke SDP minus14

The SDP path-MTU

Show router bgp routes

Show router route-table summary

Show router route-table

On the CE under the OSPF context

On the PE under the BGP context

On the PE under the OSPF context

On the CE under the BGP context

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.

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

A

C

D

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.

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

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

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.

0

5

10

45

The route reflector receives two routes for prefix 10.1.1.0/24; one from PE1 and one from PE2.

The route reflector reflects two routes for prefix 10.1.1.0/24.

PE3 receives two routes and is able to load balance traffic across PE1 and PE2.

It is the customer responsibility to ensure their address space is unique

The Route Target ensures that addresses are unique between customers

The provider will advise the customers to change their addresses

The provider will use NAT to ensure that addresses are unique between customers

The customer carrier does not learn any network provider internal routes.

The network provider learns customer carrier PE system addresses.

Routes exchanged between the customer carrier and the network provider are labeled.

The ingress PE router may forward customer packets to their destination without the presence of a route to that destination

The egress PE router may forward customer packets to their destination without the presence of a route to that destination

Any provider core router (P or PE) may forward customer packets to their destination without the presence of a route to that destination

The LDP identifier

The Service identifier

The Route Target

The tunnel label

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

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

Must be aware of the VPRNs

PE1

RR1

ASBR2

It defines the VPN membership

It defines which routes are imported into the vrf

It defines which routes are exported from the vrf

It is used as the VPN label

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

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

OSPF is not configured on the CE router

There is a problem with OSPF authentication

The PE and CE router have different OSPF interface types configured

None of the above

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

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

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

The ASBR redistributes VPN-IPv4 updates to its ASBR eBGP peers.

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

The advertising ASBR assigns a new label to the route before sending it via an MP-eBGP update to its ASBR peer.

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

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

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

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

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

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

Each customer site has a logically direct route to every other customer site.

It provides optimal routing between all sites.

It allows access between all CE devices and all sites participating in the same VRF.

It will be placed into the customer VRF and then be propagated to the BGP table only if BGP is used as
the PE-CE protocol

It will be placed into the customer VRF and require an export policy to be propagated to the BGP table

It will be placed into the customer VRF and require an export policy to be propagated to the BGP table if RIP is used as the PE-CE protocol

It will be placed into the customer VRF and require an export policy to be placed into the BGP table if a protocol other than BGP is used as the PE-CE protocol