Nokia 4A0-103 Nokia Multi Protocol Label Switching Exam Practice Test

Router R1 updates its FIB after a new SPF calculation.

Router R1 switches to a secondary path.

Router R4 switches to a FRR path.

Router R4 switches to a standby secondary path.

The PLR attempts to provide link protection.

The PLR disregards the request after three failed attempts.

The PLR changes the PATH message to request link protection.

The PLR brings down the primary LSP-path.

T-LDP is used to provide an end-to-end session between two PE routers.

T-LDP is used to signal service labels for Layer 2 services.

T-LDP is used to establish transport tunnels for Layer 2 services.

T-LDP is used in LDP over RSVP solution.

The MPLS TTL values are incremented at each request.

The router uses MPLS Echo Request packets that are IP-routed.

The router collects hop information along the tunnel's path.

The router performs an unidirectional LSP test.

Configure BGP with the IPv6 address family.

Configure BGP to add IPv6 Explicit Null labels.

Configure a route policy to export IPv6 routes into BGP.

Configure the nexthop core router as a BGP peer.

RRO is used to report the protection tunnel status to the head-end router.

RRO contains the MP information that is required by a PLR for facility protection.

RRO contains the label information that is expected by an MP for facility protection.

RRO is used to inform downstream routers about the protection type requested.

It uses a UDP connection with an arbitrary port number.

It uses a UDP connection with well-known port number 646.

It uses a TCP connection with an arbitrary port number.

It uses a TCP connection with well-known port number 646.

Router R1 will switch traffic to the secondary path immediately.

Router R1 will discard traffic until a new IGP route to router R6 is re-calculated.

Router R1 will discard traffic because the secondary path isnot a fully strict path.

Router R1 will signal the secondary path and switch traffic to it.

RSVP LSPs must exist between each PE-ABR pair, or ABR-ABR pair in each area.

When LDP-over-RSVP is active, the LDP prefixes are resolved to a physical egress interface.

Targeted sessions must exist between all routers along the tunnel path.

Link LDP sessions must exist between each ABR-ABR pair in each area.

Fast reroute is used when redundant links are not available.

Fast reroute provides path protection close to the failure point.

Fast reroute provides fast failure detection to the head-end router.

Fast reroute protects both primary and secondary paths.

configure router mpls retry-timer 30

configure router mpls resignal-timer 30

configure router mpls retry-attempts 30

configure router mpls global-revertive 30

PE, P

LER,LSR

LSR,LER

iLER, eLER

eLER, iLER

P, PE

TE enabled OSPF routers

Backbone router only

ABR only

ASBR only

A POP label stack operation may be performed.

The outgoing interface and next-hop address will be determined from the FIB.

The packet can be forwarded as a labeled or unlabeled packet.

A PUSH label stack operation may be performed.

Label bindings are distributed to other routers when explicitly requested.

Label bindings are distributed to all neighbors including non-downstream routers.

Label bindings are distributed if labels have not been received from downstream routers.

All labels received from downstream neighbors are stored in the LIB.

RSVP-TE is a routing protocol.

RSVP-TE requests end-to-end resources for unidirectional data flow.

RSVP-TE consults the local RSVP database to determine the path from source to destination.

RSVP-TE generates a TED for storing traffic engineering information.

A separate label is used for each interface that the FEC is advertised on.

It uses fewer label resources than a per-interface label space.

It is typically used when the device has ATM or Frame Relay interfaces.

It uses more label resources than a per-interface label space.

A single label may be assigned to an FEC and used across all interfaces of the same router.

It is only valid when the LDP peers are directly connected over an interface, and the label is only going to be used for traffic sent over that interface.

The LSP is in the administrative down state.

The router's router ID overlaps another.

The router's interfaces do not have LDP running.

The router's system interface requires an IP address

1

2

3

4

IP routing protocols do not always select the best route to a destination.

IP routing protocols always select multiple routes to a destination.

IP routing protocols do not make use of all available network attributes to select a path

Improper network design results in limited network path redundancy.

The peer with the higher physical address.

The peer with the higher transport address.

The peer with the lower physical address.

The peer with the lower transport address.

The peer that generated the first Hello message.

ERO is used by downstream routers to determine the next-hop for the LSP.

ERO contains label information used to signal an LSP path.

ERO is not always present in the PATH message.

Each downstream router updates information inside the ERO.

A group of packets that will be forwarded by the router in the same manner, over the same path.

A group of packets that arrive at the router on the same interface,

A group of packets that leave the router on the same interface.

A group of packets that arrive at the router on the same interface, from the same source.

Selected labels from the FIB are populated to the LFIB.

Selected labels from the RIB are populated to the FIB.

Selected labels from the LIB are populated to the FIB.

Selected labels from the LIB are populated to the LFIB.

PE, P

P, PE

PE, CE

CE, PE

CE, P

All FECs that are in the 192.168.1.0/24 address space.

Local FECs that are in the 192.168.1.0/24 address space.

All FECs that are not in the 192.168.1.0/24 address space.

All FECs except the local FECs that are in the 192.168.1.0/24 address space.

Enabling VPNs

Enabling traffic engineering

Enabling network security

Enhancing network resiliency

Each PLR signals a bypass tunnel that avoids the next-hop downstream router.

When a failure occurs, the PLR pushs an additional label onto the label stack.

No bypass tunnel is established if the PLR cannot provide node protection.

The head-end router sets the local protection desired flag in the session attribute object.

Enable the Idp-over-rsvp feature on all PEs and ABRs along the LSP tunnel.

Configure Link-LDP sessions between each PE-ABR and ABR-ABR pair.

Configure RSVP-TE LSPs in each area between each PE-ABR and ABR-ABR pair.

Configure T-LDP sessions with the tunneling option.

The tail-end router performs the CSPF calculation for an LSP.

CSPF calculations are always performed on RSVP-TE based LSPs.

The head-end router performs the CSPF calculation for an LSP.

Each downstream router performs its own CSPF calculation for an LSP.

The adjacency forms with the lower timeout value

The "show router Idp session" command output displays the adjacency in state "init"

The adjacency forms with the higher timeout value

The adjacency times out after 30 seconds

Each implementation can use them as they see fit.

They are used to carry the Ethertype value.

They are used to carry the TTL value.

They are used to carry QoS classification.

They are used to carry fragmentation flag information

Router R1

Router R2

Router R3

Router R4

Router R5

The path message's IP header options field sets the router alert option.

The IP header source address is the sender's egress interface address.

The IP header destination address is the next-hop interface address.

The IP header HOP object reflects the upstream router's egress interface address.

4

1

5

6

The LSP can also use facility backup.

The LSP is limited to node protection.

You cannot request bandwidth on the protected LSP.

Node protection can be disabled.

Fixed filter

Shared explicit

Standby explicit LSP

Preemptive filter

Link capacity filter