4A0-C04 Nokia NRS II Composite Exam: OSPF version Questions and Answers

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping

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

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

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

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

They reduce the number of SDPs that need to be configured.

They can be used to work around physical topologies that prevent a fully meshed deployment.

They prevent loops that can be introduced by mesh deployments.

They can simplify the implementation of security policy enforcement and packet inspection.

When a link state update is received in response to a link state request.

When a router receives a Hello packet that contains its own router ID in the neighbor list from a neighbor.

When a router receives a database description packet from a neighbor.

When a link state acknowledgement is received in response to a link state update.

Frame mode requires multiple sessions between peers.

The lower transport address initiates the session.

Established LDP sessions run over a TCP connection.

An LDP session is established immediately after Init messages are exchanged between peers.

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.

AS Path of 65200 65100, Next Hop of router A.

AS Path of 65200 65100, Next Hop of router E.

AS Path of 65100, Next Hop of router E.

AS Path of 65100, Next Hop of router A.

Service tunnels are unidirectional.

Transport tunnels are unidirectional.

A service will use the same service label for every hop.

A local service requires a transport tunnel.

IP packets sent to an IP multicast address.

TCP packets sent to an IP multicast address.

IP packets sent to an IP unicast address.

UDP packets sent to an IP multicast address.

Import policies affect ingress data flow.

Export policies affect ingress data flow.

Both import and export policies affect ingress data flow.

Policy direction and data flow are independent.

The original VLAN tag is removed.

The original VLAN tag is kept.

The VLAN tag is replaced by a provider tag.

The VLAN tag is kept and a provider tag is added.

iLER

LER

LSR

PE

eLER

The prefix list reject should be "192.168.3.0/16 exact".

Router R1 should be configured as an OSPF "asbr".

The policy "reject" should be set for import rather than export.

The policy was likely not "committed" after creation.

This is not possible because OSPF cannot use import policies.

Hello message

Init message

Keepalive message

Label Mapping message

ACK message

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.

The LSP will switchover to another path if a failure occurs.

The LSP will switchover to a better path as soon as it is available.

CSPF must be enabled for this LSP to attempt to find a better path.

The LSP will switchover to a better path in a MBB fashion.

ISIS, RIP, OSPF, static routes

BGP, ISIS, RIP, OSPF, static routes

BGP, RIP, OSPF, static routes, OSPF3

ISIS, RIP, OSPF, static routes, OSPF3

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.

An echo request is sent based on the LSP's label stack.

Echo reply packets may not take the same path as the LSP.

The IP destination address is used to initiate echo requests,

The test fails if the LSP is not operationally up.

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.

Well-known mandatory

Well-known discretionary

Optional transitive

Optional non-transitive

All routers along the path, R1, R2, and R3 can be PLRs.

If the R1-R2 link fails, router R4 becomes an MP.

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

Router R1 is the LSP head-end and can be a PLR.

To protect external networks from instability.

To communicate the architecture of an AS to external ASs.

To protect the local AS and other external ASs from bad NLRI.

To optimize ingress and egress traffic patterns to best serve the users of the AS.

Conservative label retention

Liberal label retention

Downstream on demand

Downstream unsolicited

Router B propagates the BGP update to routers D and C.

Router B propagates the BGP update to router D.

Router B detects duplicates in its BGP database and discards the update.

Router B propagates the update to routers A, C and D.

From the last 32 bits of the chassis MAC address

From the first 32 bits of the chassis MAC address

The loopback IP address

By using the command "config router ospf rid X.X.X.X"

From the system IP address

From the highest interface IP address

0

5

10

15

Option A

Option B

Option C

Option D

With the same method and attribute as 16-bit AS numbers.

With the same method as 16-bit AS numbers, but using the AS4_Aggregator attribute.

Aggregation is not yet supported with 32-bit AS numbers.

By using a dummy value of 23456 in the 16-bit AS aggregator field. This value lets the router know it needs to read the 32-bit AS number that is contained in the nextTLV.

Router R1 generates a type 5 LSA that is flooded through all OSPF areas.

Router R1 generates a type 7 LSA that is flooded through all OSPF areas.

Router R1 generates a type 5 LSA that is flooded through area 1. Router R2 generates a type 7 LSA that is flooded through areas 0 and 2.

Router R1 generates a type 7 LSA that is flooded through area 1. Router R3 generates a type 5 LSA that is flooded through areas 0 and 2.

PE, P

P, PE

PE, CE

CE, PE

CE, P

Send a PATH Tear message toward router R6.

Send a PATH Tear message toward router R1.

Send a PATH Error message toward router R6.

Send a PATH Error message toward router R1.

None

2

3

4

Path-ID is a four-octet identifier pre-pended to the NLRI field of a BGP update.

Path-ID is an optional transitive attribute used to advertise multiple paths.

Path-ID uniquely identifies each path advertised to a neighbor.

A BGP speaker that re-advertises a route must generate its own Path-ID.

It modifies the BGP advertisement logic.

It improves convergence times and allows for better load sharing.

It allows a router to advertise multiple external paths for a single prefix.

It supports both IPv4 and IPv6.

LDP Hello messages are sent over TCP.

LDP Hello messages are sent to the All Routers address 224.0.0.2.

LDP Hello messages are exchanged between all directly connected LDP enabled routers.

Each LDP enabled router must have its own unique system IP address.

7958

7978

8022

8042

Router LSA

Network LSA

C Summary network LSA

Summary router LSA

Type 5 (AS external) LSAs

5000

5004

5008

5014

The options field is set to router alert.

The source address is R1's egress interface address.

The destination address is R2's ingress interface address.

The HOP object includes R2's system address.

1

32

64

255