4A0-103 Practice Exam Questions with Answers Alcatel-Lucent Multi Protocol Label Switching Certification

CSPF must be enabled at head-end on fast reroute protected loose path LSPs

Fast reroute must first be enabled on the downstream routers.

CSPF must be enabled on all downstream loose hop routers.

Global revertive path optimization must be enabled so the path will be re-optimized around a failed node.

It identifies the FEC.

It specifies the packet's header length

It identifies the origin of the packet.

It specifies the type of data contained in the packet

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.

An LER may answer requests for label mappings immediately, without waiting for a label mapping from the next-hop.

An LER may advertise label mappings to all peers for which it might be a next-hop for a given FEC.

An LER propagates a label mapping downstream for a FEC. only if it has a label mapping for the FEC next-hop.

An LER will only distribute a label for a FEC when it has been requested to do so.

Router R1

Router R2

Router R3

Router R4

Router R5

Router R1 is the LSP originator and is also a PLR.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R2-R3.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R3.

If the R2-R3 link fails, router R3 becomes a PLR

None of the nodes can be protected with FRR.

TRUE

FALSE

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.

Configure the T-LDP peers for tunneling.

Configure tunneled T-LDP sessions between PE routers.

Enable Idp-over-rsvp in the IGP configuration on the PEs and ABRs

Enable LSP stitching on the RSVP LSPs

Independent control mode

Ordered control mode

Liberal label retention

Conservative label retention

Downstream on demand.

CSPF looks for the delta bandwidth, taking down the first path if necessary.

CSPF looks for the delta bandwidth, implementing make-before-break.

After 5 failed attempts to find the bandwidth requested, the head end disables the LSP.

CSPF looks for the entire bandwidth requested, implementing MBB.

TRUE

FALSE

Each PLR signals a detour LSP that avoids the downstream node. If the downstream node cannot be avoided, a detour LSP that avoids the downstream link is signaled.

The detour LSP can take one or more hops before merging back on the protected LSP.

The merge point of the protected LSP must be the next-next-hop node

The ingress router will set the local protection desired flag in the session attribute object of the path message to inform all routers along the protected LSP path to establish detour LSPs.

The label recording desired flag must be set in the session attribute object in order for the PLR to know what label to swap when using the detour LSP.

Type 9 LSA ?Link local LSA

Type 10 LSA ?Area local LSA

Type 8 LSA ?TE router LSA

Type 11 LSA ?Network LSA

Disable route summarization on router R3

Enable LDP aggregate prefix match

Create an import policy to accept these FECs

Disable LDP exact match on the specified FECs

The PLR issues a RSVP path message to the destination router to request the address of the MP.

The PLR learns the address of the MP from the ERO.

The PLR learns the address of the MP from the RRO

The PLR learns the address of the MP from the targeted RSVP hello message.

The PLR does not need to know the address of the MP.

Targeted sessions must exist between all routers in the tunnel's path.

Each LDP interface must be configured to support LDP tunneling.

LDP prefixes resolve to an RSVP LSP, rather than to a physical egress interface.

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

The packet will be label switched; the outer label TTL will be 249 and the inner label TTL will be 250.

The packet will be label switched; the outer label TTL will be 249 and the inner label TTL will be 251.

The packet will be label switched; both the outer label TTL and the inner label TTL will be 250.

The packet will be label switched; both the outer label TTL and the inner label TTL will be 249, because they must be the same.

Router R1

Router R2

Router R3

Router R4

Router R5

The Hello protocol can speed up convergence without reducing refresh time.

Hello messages are sent after at least one RSVP session is active on the interface.

An interface with multiple RSVP sessions sends Hello messages for each session.

An RSVP neighbor is declared down if Hello messages are not received within the Hello timeout.

Label request message

Notification message

Address message

Keepalive message

Initialization message

Hello message

10.32.1.2

10.1.478

1048.1.1

Cannot tell from this configuration

10.1.2.2

Each PLR will signal a bypass tunnel that avoids the next-hop node or link.

When a failure occurs, the PLR will push an additional label onto the label stack and start forwarding traffic onto its bypass tunnel.

The ingress router will include a RRO object in the path message to indicate the routers that should be PLRs and MPs along the protected path.

The ingress router will set the local protection desired flag in the session attribute object of the path message to inform all routers along the protected LSP path to establish bypass tunnels.

When the bypass tunnel is in use, the MP will include the RRO object in its PathErr message, with the local protection in use flag set to notify the ingress router that it is using the bypass tunnel.

configure router mpls retry-timer 30

configure router mpls resignal-timer 30

configure router mpls retry-attempts 30

configure router mpls global-revertive 30

Liberal label retention mode

T-LDP enabled with peers to which load balancing is desired.

ECMP enabled in the config>router context.

Hashing used to select the egress label.

Export policy applied to advertise multiple labels for a given FEC.

Admin groups can be configured using the command "configure>router>mpls>admin-group".

CSPF uses the information defined by admin groups when paths are computed for constraint-based LSPs.

By default, interfaces for which MPLS has been enabled are in the default admin group.

A LSP can make use of admin groups for constraint-based path calculations by including or excluding the admin group

Send a PathTear message towards router R6.

Send a PathTear message towards router R1.

Send a ResvTear message toward router R6.

Send a ResvTear message toward router R1.

PE, P

LER,LSR

LSR,LER

iLER, eLER

eLER, iLER

P, PE

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

TRUE

FALSE

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

The PLR issues an RSVP PATH message to the tail-end requesting the address of the MP.

The PLR learns the address of the MP from the ERO.

The PLR learns the address of the MP from the RRO.

The PLR learns the address of the MP from the targeted RSVP Hello message.

The PLR knows the address of the MP is the same as the tail-end router.

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.

A single label is assigned to a FEC for all interfaces on the same router.

The same label can be used to forward a packet on an LSR regardless of which egress port is used.

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

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

Label space mode

Label retention

Control mode

Keepalive factor

Node protection tunnels detour around a failed next downstream router.

Node protection tunnels can only be requested for a primary LSP path.

Node protection tunnels are only used by one-to-one Fast Reroute.

Link protection tunnels are established if a router is unable to establish node protection tunnels.

After a new path for LSP-1 is established on R1-R3-R5-R6, the old path is torn down.

After the old path for LSP-1 is torn down, the new path is established on R1-R3-R5-R6.

LSP-1 will stay on R1-R2-R4-R6 because there is enough bandwidth on the existing path.

LSP-1 will be torn down because CSPF fails to find a new path.

Both LSP-3 and LSP-4 take R1-R2-R4-R6.

Both LSP-3 and LSP-4 take R1-R3-R5-R6.

LSP-3 takes R1-R3-R5-R6 and LSP-4 takes R1-R2-R4-R6.

LSP-3 takes R1-R2-R4-R6 and LSP-4 takes R1-R3-R5-R6.

CSPF randomly chooses one of the equal cost paths for the two LSPs.

Link TLVs are used to advertise administrative group information.

Link TLVs are exchanged once RSVP is enabled on the interfaces.

Link TLVs are used to advertise router-IDs.

Link TLVs are used to advertise bandwidth information.

An IGP route takes priority over a transport tunnel.

Both LDP and RSVP-TE based tunnels can be used.

MPLS tunnels can be used to resolve the prefixes learned via IGP.

Multiple MPLS tunnels can be installed in the FIB.

The TC field is set based on the value of the DSCP field inside the customer packet.

The TC field is set to a specific value via explicit administrative configuration.

The TC field is set to a system generated random number.

The TC field is set by the eLER.

Router R1

Router R2

Router R3

Router R4

Router R5

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.

They are multicast to the All Hosts address.

They are broadcast to the subnet broadcast address.

They are multicast to the All Routers address.

They are broadcast or multicast, depending on the physical media.

Hello message

Init message

Keepalive message

Label Mapping message

ACK message

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.

RSVP uses downstream on demand label distribution mode.

LDP uses conservative label retention mode.

LDP advertises label mappings to all peers for which it might be a next-hop for a given FEC.

RSVP distributes a label mapping for a FEC when it has been requested to do so.

The MPLS label value may be carried in an ATM header.

The MPLS label value may be carried in a shim header.

The MPLS label value may be carried in an OSPF header.

The MPLS label value may be carried in a Frame Relay header.

The time router R2 takes to receive a PATH Error message from router R4.

The time router R2 takes to find out a number of RSVP Hello messages have been missed.

The time router R2 takes to send a PATH Tear message to the head-end router.

The time router R2 takes to receive a PATH message from router R4 after a PATH refresh interval.

Each PLR signals a protection tunnel that avoids the downstream node.

A single protection tunnel can protect all LSPs that go through the same hop.

A link protection tunnel is signaled if a node protection tunnel cannot be established.

Protection tunnels used in this LSP are also detour tunnels.

PE-1 requires T-LDP sessions to both ABR-1 and ABR-2.

PE-1 requires a full mesh of RSVP-TE LSPs to all routers in area 1.

ABR-1 requires T-LDP sessions to all ABRs in area 0.

PE-1 requires fast reroute enabled on all RSVP-TE LSPs.

10 Gbps

7 Gbps

3 Gbps

2 Gbps

Enabling VPNs

Enabling traffic engineering

Enabling network security

Enhancing network resiliency

The LSP will stay on the current path indefinitely unless another failure occurs.

The LSP will stay on the current path until the resignal timer expires.

The LSP will switchover to R1-R2-R3-R5-R6 after the resignal timer expires.

The LSP will switchover to R1-R3-R5-R6 after the retry timer expires.

It makes use of MPLS resiliency features available within an AS.

It eliminates double route lookups on all routers within an AS.

It eliminates the need to run IGP on all routers within an AS.

It eliminates the need for an iBGP full mesh on all core routers.

When the reserved bandwidth goes above 80M.

When the reserved bandwidth goes above 40M.

When an additional 80M bandwidth is reserved.

When an additional 40M bandwidth is reserved.

Independent control mode, downstream on demand

Independent control mode, downstream unsolicited

Ordered control mode, downstream on demand

Ordered control mode, downstream unsolicited

Label swapping

Pushing a label on an unlabeled packet

Label allocation

Routing lookups

The router will switch to Path-2 because it is the first secondary path configured in the list.

The router will not switch to Path-2 because the current path has the longest uptime.

The router will switch to Path-2 because it is a more preferred path.

The router will not switch to Path-2 because the router will not revert to another secondary path.

The secondary path will take R1-R3-R2-R4-R6.

The secondary path will take R1-R2-R4-R6.

The secondary path will take R1-R2-R3-R5-R6.

The secondary path will take R1-R3-R2-R4-R5-R6.

An LSR may answer requests for label mappings immediately, without waiting for a label mapping from the next-hop.

An LSR may advertise label mappings to all peers for which it might be a next-hop for a given FEC.

An LSR propagates a label mapping downstream for a FEC, only if it has a label mapping for the FEC next-hop.

An LSR will only distribute a label for a FEC when it has been requested to do so.

Router R1 sends a PATH message and router R4 sends back a PATH Error message.

Router R1 does not send a PATH message because it detects an error.

Router R1 sends a PATH message and router R4 sends back a PATH Tear message.

Router R1 sends a PATH message and router R4 sends back a RESV Error message.

The LSP can use facility and one-to-one FRR simultaneously.

The LSP is limited to node protection.

A single protection tunnel is used for all LSPs with the same path.

A detour protection tunnel is created for the LSP.

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.

R1-R2 will have 300Mbps left and R2-R4 will have 400Mbps left.

R1-R2 will have 400Mbps left and R2-R4 will have 400Mbps left.

R1-R2 will have 600Mbps left and R2-R4 will have 600Mbps left.

R1-R2 will have 300Mbps left and R2-R4 will have 600Mbps left.

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 adjacency forms with the lower timeout value.

The adjacency forms with the higher timeout value.

The adjacency is in init state.

The adjacency times out after 30 seconds.

TE enabled OSPF routers

Backbone router only

ABR only

ASBR only

The router performs a unidirectional LSP test.

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

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

The MPLS TTL values are incremented at each request.