Free Practice Questions for Nokia 4A0-C02 Exam

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

The Alcatel-Lucent 7750 SR accepts routes containing AS_PATH loops by default.

When the CLI command "config>router>bgp# loop-detect discard-route" is used, the Alcatel-Lucent 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.

PE1 advertises spoke routes to CE1.

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

The secondary VRF on PE1 contains routes learned from the spoke sites.

Spoke sites do not learn routes from other spoke sites directly.

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.

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.

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.

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

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.

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

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.

A 32-bit Route Target followed by a 32-bit IPv4 address.

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

PE1 pushes an LDP transport label.

CSC-CE1 pops the LDP label and pushes a BGP label.

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

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

Customer carrier PE routers residing in different sites must run iBGP between them to exchange customers' routes.

MPLS can be used in the customer carrier network to improve scalability.

The customer carrier network can be a pure IP network.

A CSC VPRN is configured on the CSC-CE to forward data packets to the network provider.

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

In the routing updates exchanged from CE to PE

In the routing updates exchanged from PE to PE

In the routing updates exchanged from P to PE

In customer packets as they traverse the provider core

In all route tables of the VPRN control plane