Full; both routers are exchanging Helios to maintain the adjacency.

The adjacency is down.

The adjacency is in exstart state.

The adjacency is in the exchange state.

Incoming label

Outgoing label

Incoming interface

Outgoing interface

Broadcast

Non-Broadcast Multi-Access

Point-to-Point

Point-to-Multipoint

Router R3 rejects all updates originating in AS 65540.

Router R3 accepts updates received from router R1 and rejects updates transited through router R2.

Router R3 accepts updates transited through router R2 and rejects updates received from router R1.

Router R3 accepts updates from both routers R1 and R2.

R1-R3-R8

R1-R2-R4-R8

R1-R3-R4-R8

R1-R2-R4-R3-R8

It tests the IGP reachability of the far-end IP address of an SDP.

It tests that the MTU settings of a service are correct.

It tests in-band, uni-directional or round-trip connectivity of SDPs.

It tests the reachability of hosts connected to an SDP.

Show ospf neighbors

Show router ospf neighbors

Show router ospf adjacency

Show ospf adjacency

0

1

2

3

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.

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

An OSPF type 3 LSA is an intra-area LSA, generated by the ABR only when route summarization is configured.

An OSPF type 3 LSA is an inter-area LSA, generated by the ABR only when route summarization is configured.

An OSPF type 3 LSA is an inter-area LSA, generated by an ASBR to describe external routes.

An OSPF type 3 LSA is an inter-area LSA, generated by the ABR to describe a route to neighbors outside the area.

10.32.1.2

10.1.4.78

10.48.1.1

10.1.2.2

RIPv1 and RIPv2

OSPF

IS-IS

BGP

They both function as a Layer 2 switch from the service provider's perspective.

They both support SAP encapsulations of null, dot1Q and Q-in-Q.

They both use SAPs as the demarcation point between the customer and the provider.

MAC addresses are learned by VPLSes, but not by E-pipes.

Show route-table

Show router routing-table

Show router route-table

Show static

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.

Router R1 generates a Type 4 LSA that is flooded to areas 0, 1, and 2.

Router R3 generates a Type 4 LSA that is flooded to areas 0, 1, and 2.

Router R3 generates a Type 4 LSA that is flooded to areas 0 and 2.

Router R3 generates a Type 4 LSA that is flooded to area 0, and router R6 generates a Type 4 LSA that is flooded to area 2.

ISP 1 has a peering relationship with ISP 2 and ISP 4.

ISP 1 has a peering relationship with ISP 2 and a transit relationship with ISP 3.

ISP 1 has a peering relationship with ISP 2 and ISP 3.

ISP 1 has a transit relationship with ISP 2 and ISP 4.

ISP 1 has a transit relationship with ISP 2 and a peering relationship with ISP 3.

The protocol field of the transport layer header

The port field of the transport layer header

The protocol field of the network layer header

The port field of the network layer address

A route received from a BGP peer within the same AS.

A route originated by a router in a different cluster of the same AS.

A route received from a BGP peer from a different member AS of a confederation.

A route received from a BGP peer from the same member AS of a confederation.

They are type 7 within the area and are not modified at the ABR

They are type 5 within the area and converted to type 3 at the ABR

They are type 5 within the area and are not modified at the ABR

They are type 7 within the area and converted to type 5 at the ABR

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.

Area ID W B.

Hello and Dead intervals PC.

Stub flag

Checksum values

The list of neighbors

Type 1

Type 3

Type 4

Type 7

Label values may be dynamically assigned by LDP.

Label values may be dynamically assigned by RSVP-TE.

Label values may be reserved for special uses.

Label values may be dynamically assigned by IGP.

10 Gbps

7 Gbps

3 Gbps

2 Gbps

Advertising external networks into IGP.

Using system addresses for setting up iBGP sessions.

Exporting the networks associated with the external links of eBGP peers into BGP.

Optimizing BGP route table by exporting IGP routes into BGP.

The customer's Layer 3 header is removed at the iLER.

The customer's Layer 2 header is removed at the iLER.

The customer's Layer 3 header is removed at the eLER.

The customer's Layer 2 header is removed at the eLER.

Both PE1 and PE2 need a mirror source.

PE2 needs a mirror source with the remote source specified.

PE1 needs a mirror source with the remote source specified.

Both PE1 and PE2 need a mirror destination.

PE2 needs a mirror destination that specifies a SAP.

In multi-access networks, a DR and BDR are elected only if there are more than two routers connected to the network segment.

In multi-access networks, a DR and BDR are elected only if the subnet masks on the router interfaces are less than /30

In multi-access networks, a DR and BDR are elected. To ensure resiliency, both the DR and BDR send link-state advertisements describing the network.

In multi-access networks, a DR and BDR are elected. The DR sends link-state advertisements describing the network.

Traffic engineering information is carried in the extended TLVs.

Traffic engineering must be enabled on all IP/MPLS routers along the LSP path.

Traffic engineering information is stored in the opaque database,

Traffic engineering is required for constraint-based LSPs.

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.

The router sends a link-state update to its neighbor.

The router sends a link-state acknowledgement to its neighbor.

The router updates the information in its LSDB with the information received from its neighbor.

The router sends a link-state request to its neighbor.

The router takes no action.

The router will accept the update and send a notification.

The router will not accept the update and send a notification.

The router will accept the update and ignore the attribute.

The router will accept the update and propagate the attribute.

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.

RIPv2 supports basic and MD5 authentication only.

RIPv2 supports password and MD5 authentication only.

RIPv2 does not support authentication, password and MD5 authentication.

RIPv2 does not support authentication.

"client2" routes will be tagged with communities "West" and "North".

"client2" routes will be tagged with communities "West", "North" and "South".

"client2" routes will be tagged with community "West".

"client2" routes will be tagged with community "South".

Router R1forms an iBGP session with router R2, and an eBGP session with router R3.

Router R1forms iBGP sessions with routers R2 and R3.

Router R1forms eBGP sessions with routers R2 and R3.

The types of BGP sessions with routers R2 and R3 cannot be determined.

Type 1 Router LSA

Type 2 Network LS A

Type 3 Summary LSA

Type 5 External LSA

The corporate head office router will have a default route and the branch site will have a more specific static route.

The corporate head office router and the branch office router will both have specific static routes.

The corporate head office router and the branch router will both have default routes.

The corporate head office router will have a more specific static route and the branch office router will have a default route.

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.