TRUE

FALSE

Shut down all SAPs associated with the service.

Shut down all SDPs associated with the service.

Delete all SAPs and SDPs associated with the service.

Shut down all physical ports that are bound to a SAP.

Delete the Customer ID.

Shut down the service.

The VC-IDs used between the E-pipe and VPLS must match.

The E-pipe must maintain a MAC FDB in order to connect to the VPLS.

The service ID of the E-pipe can be different from that of the VPLS.

The service MTU of the VPLS and E-pipe must match.

configure ies 5 customer 1000 create

configure router ies 5 customer 1000 create

configure service ies 5 customer 1000 create

configure router ies 5 customer 1000

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

It results in forwarding based on the next packet header.

It indicates that the label is the bottom of the MPLS label stack.

It indicates that the label is the top of the MPLS label stack.

Any LSR that receives an S bit set to 1 must discard the packet.

The router sends a copy of the LSP from its database to its neighbor.

The router sends a PSNP to its neighbor describing the LSP in its database.

The router updates its database with the LSP and floods a copy to its other neighbors.

The router sends a PSNP to its neighbor to request the LSP.

Router address

Traffic engineering metric

Maximum bandwidth

Link

Admin Group

To reduce the size of each routing update.

To allow interoperability between routing protocols.

To allow different subnet masks for different subnets.

To reduce the size of the routing table.

2001::FF:FE:14:6CAE

2001::1:FF:14:6CAE

FF02.DB8::30A:216:4DFF:FE14.6CAE

FF02::1:FF14:6CAE

show router mpls Isp "LSP 1" originate

show router mpls Isp "LSP 1" path detail

show router rsvp session originate

show router rsvp session "LSP 1"

Router R1

Router R2

Router R3

Router R4

Router R5

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

It discards packets based on the source address.

It discards packets that match the destination prefix.

It returns ICMP unreachable messages.

It discards packets based on the egress port.

Add "stub no summaries" to the area 1 configuration on router R1.

Add the "originate-default-route" option in the area 1 configuration on router R1.

Add a default static route on router R3.

Include the system interface in the area 1 configuration on router R3.

Add a static route on router R3 to 192.168.3.1.

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Inter-Area Router LSA

AS External LSA

TRUE

FALSE

IS-IS uses the concept of Level 1 and Level 2 routers to implement hierarchy.

An IS-IS router belongs to one or more areas.

All Level 2 routers belong to the same area.

A Level 1 router forwards traffic to other areas through the nearest Level 1/2 router.

The primary and backup routes are to the same destination.

The primary and backup routes appear in the routing table.

The backup route is configured with a higher preference value.

The next-hop of the primary and backup routes are different.

Router R1

Router R2

Router R3

Router R4

Router R5

Exchange

Up

Down

2-Way

A VPLS service does not use a MAC FDB.

A single MAC FDB is shared by all VPLS services on a PE.

A separate MAC FDB is used on the PE for each VPLS service.

Each VPLS service uses a separate MAC FDBs for unicast and multicast traffic.

TRUE

FALSE

Only the mirror source must be re-configured.

Only the mirror destination must be re-configured.

Both the mirror destination and mirror source must be re-configured.

Neither the mirror destination nor the mirror source must be re-configured.

The system ID.

The loopback address.

The sequence number of the Hello packet.

The device that first initiated communication becomes the DIS

The highest interface MAC address.

Option A

Option B

Option C

Option D

The source IP address will be the address of the PC, and the destination IP address will be the system IP address of router R1; the source MAC address will be the MAC address of the PC, and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

The source IP address will be the address of the PC, and the destination IP address will be the IP address of the router R1 port connected to the PC, the source MAC address will be the MAC address of the PC, and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

The source IP address will be the address of the PC, and the destination IP address will be the IP address of the server, the source MAC address will be the MAC address of the PC, and the destination MAC address will be the MAC address of the server.

The source IP address will be the address of the PC, and the destination IP address will be the IP address of the server; the source MAC address will be the MAC address of the PC, and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

With a Router LSA originated by R1

With a Router LSA originated by R5

With a Router LSA originated by R4

With an Inter-Area Prefix LSA originated by R1

With an Inter-Area Prefix LSA originated by R5

With an Inter-Area Prefix LSA originated by R4

Not So Stubby Areas

Level 1 Areas

Stub Areas

Partially Stubby Areas

Show isis neighbors

Show router isis neighbors

Show router isis adjacency

Show isis adjacency

Use split horizon by default.

Send information about directly connected links to neighbors at periodic intervals.

Use holddown timers when topologies change to allow for convergence.

Maintain multiple databases: neighbor, topology and routing.

RIPv1, RIPv2, and BGP are distance vector protocols.

OSPF and IS-IS are distance vector protocols.

Routing tables are exchanged between neighbors; however, no routing table is transmitted beyond the immediate neighbor.

Distance vector protocols use the Dijkstra SPF algorithm.

Routers that participate in distance vector routing protocols maintain full knowledge of distant routers and how they interconnect

Source IP address

TCP source port

Prefix list

Protocol type

The term backbone router has the same definition as the term area border router.

An OSPF network needs at least one area border router to function.

Area border routers connect the backbone area to other areas in an OSPF network.

By definition, an area border router must perform route summarization between areas.

The packet is flooded out all router interfaces.

The packet is dropped and an ICMP unreachable message is sent back to the source.

The packet is silently discarded.

The packet is flooded out all interfaces and an ICMP unreachable message is sent.

Broadcast

Non-broadcast multi-access

Point-to-point

Point-to-multipoint

1

2

3

4

6

7

config> static-route 0.0.0.0/0 next-hop 10.1.2.2

config>router> static-route 0.0.0.0 255.255.255.255 next-hop 10.1.2.1

config>router> static-route 0.0.0.0/0 next-hop 10.1.2.2

config>router> static-route 0 0.0 0/0 next-hop 10.1.2.1

traceroute 10.2.3.1

traceroute 10.2.3.1 next-hop 10.1.2.1

traceroute next-hop 10.1.2.1

traceroute does not work on the Alcatel-Lucent 7750 SR.

traceroute 10.1.2.1

They are sent using multicast MAC addresses 0180:0200:0014.

They are sent using multicast MAC addresses 0180:c200:0015.

They are sent using a unicast address.

None of the above.

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.

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.

MPLS Echo Request packets are sent unlabeled to the prefix 192.10.1.2.

MPLS Echo Request packets are sent within the LDP tunnel that are signaled for 192.10.1.2.

MPLS Echo Request packets are sent within the RSVP-TE tunnel that are signaled for 192.10.1.2.

MPLS Echo Request packets are sent over TCP.

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.

The inner label is the IPv4 Explicit Null. The outer label is the MPLS transport label,

The inner label is an MPLS transport label. The outer label is the IPv4 Explicit Null.

The inner label is the IPv6 Explicit Null. The outer label is an MPLS transport label.

The inner label is an MPLS transport label. The outer label is the IPv6 Explicit Null.

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 generates a summary refresh message for each LSP.

Message-IDs replace individual refresh messages.

An LSP state change causes the Message-ID to be incremented.

RSVP refresh reduction is disabled by default.

The VPN label is signaled between PE devices using MP-BGP.

The VPN label is swapped at each P router as a packet crosses the service provider network.

The VPN label is also known as the inner label or service label.

The VPN label indicates which VPRN a packet should be sent to once it reaches the egress PE.

All of the above

Only C and D.

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family vpn-ipv6

neighbor 10.10.10.2/32

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

-------------------------------------------

group "multi-bgp"

family ipv6 vpn-ipv4

neighbor 10.10.10.2

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family vpn-ipv6

neighbor 10.10.10 2

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family ipv6 vpn-ipv6

neighbor 10.10.10.2/32

local-address 10.10.10.1

peer-as 64496

exit

exit

Enabling VPNs

Enabling traffic engineering

Enabling network security

Enhancing network resiliency

0

1

2

3

4

They periodically exchange copies of routing tables between adjacent routers and do not maintain any knowledge of links on non adjacent routers.

They use shortest path first algorithms, do not exchange copies of routing tables between routers and do maintain knowledge of links on non adjacent routers.

They periodically exchange copies of routing tables between adjacent routers and maintain knowledge of links on non adjacent routers.

They use shortest path first algorithms, exchange copies of routing tables between routers and maintain knowledge of links on non adjacent routers.

It is always a random 16-bit number.

It is always zero for per-interface label space.

It is always non-zero.

It is always zero for per-platform label space.

It is always non-zero for per-platform label space.

The router must also have an active static route to the next-hop specified in the static route command.

The system address of the next-hop router must be included in the static route command.

The command option "indirect" must be used in the static-route command.

The system address of the router connected to the destination must be included in the static route command

The router has a system interface, two point-to-point interfaces and one broadcast interface.

The router has a system interface, two passive interfaces, two point-to-point interfaces and one broadcast interface.

The router has a system interface, two point-to-point interfaces and one virtual link.

The router has a system interface, two passive interfaces, two point-to-point interfaces and one virtual link.

ping

Isp-ping

traceroute

Isp-trace

1

5

10

20

The matching outer tag is removed, and the frame is forwarded.

The inner tag is removed, and the frame is forwarded.

The inner tag is changed to match the SAP, and the frame is forwarded.

The frame is dropped.

The E-pipe can support a maximum MTU size of 1578.

The ports of the link PE2-PE3 have an MTU of 1578.

An svc-ping of the E-pipe will succeed.

If the step size was 2, the maximum response size would be the same.

A-pipe

F-pipe

C-pipe

E-pipe

The IES's interface must be an IGP peer with the CE.

The IES must use an IP address that is different than the C£.

The IES can only include one SAP for the CE.

The IES must include a network port.

1514

1526

1548

1556

1536

The default service MTU on a VPLS service is 1514 bytes.

The default IP MTU of an IES is set based on the network port MTU.

During VC label signaling, the VC MTU is verified and must match.

All of the above.

A VPLS service does not use an FDB.

The router reads the destination MAC address of packets passing through the service.

The router reads the source MAC address of packets passing through the service.

The router uses reverse ARP (RARP) to resolve the MAC addresses for unknown destinations.

The router is programmed with MAC addresses by the network administrator.

Option A

Option B

Option C

Option D

TRUE

FALSE

sdp-ping

Isp-ping

svc-ping

sdp-mtu

A PE uses the same VRF table for all the VPRN services on it.

A PE uses a VRF to maintain forwarding information.

Information for VRFs can be advertised between PEs by MP-BGP.

A PE uses a VRF to route traffic to CEs.

More than one SAP can be configured on a physical port that is configured for null encapsulation.

Dot1Q Ethernet encapsulated access ports can support multiple SAPs and services.

SAPs can be created on ports designated as "Network".

SAPs can only be created on Ethernet ports.

sap 1/1/1

sap 1/1/1:*.0

sap 1/1/1:0.*

1/1/1:0

The Ethernet port must be set to network mode, and the service must have a spoke SDP.

The Ethernet port must be set to network mode.

The Ethernet port must be set to access mode.

The Ethernet port must be set to access mode, and the service must have a spoke SDP.

The frame is dropped.

The frame's outer tag is changed to match the SAP, and it is accepted.

The frames outer tag is dropped, and the frame is accepted.

The frame's tags are removed, and the frame is accepted.

DLC Header

Control Word

Transport Label

Service Label

Traffic is flooded to all SAPs in the service.

Traffic is flooded to all SAPs and spoke SDPs in the service.

Traffic is flooded to all SAPs and mesh SDPs in the service.

Traffic is flooded to all SAPs, spoke SDPs. and mesh SDPs in the service.

The traffic is not flooded.

ADSPEC

CSPF

Service ping

LSP trace

A virtual routing/forwarding table is created per IES service.

Only one IES service can be created for a single customer ID.

More than one IP interface can be created within a single IES service.

All IP interfaces created within the same IES service belong to the same customer

A mirror source with a defined source type.

A mirror source defined with an SDP destination.

A mirror destination with a SAP defined.

A mirror destination and a mirror source with the same service ID.

The SDP itself (outside of the epipe context).

The SAP in the E-pipe.

The mesh SDP in the E-pipe.

The spoke SDP in the E-pipe.

The PE routers of the service are responsible for learning MAC addresses.

Flooding ensures that all PEs in a fully-meshed VPLS will learn the source address of all traffic.

MAC learning reduces flooding of frames with previously learned addresses.

Multiple VPLSes on the same PE share the same MAC FDB.

Option A

Option B

Option C

Option D

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

The old primary path and its detours are torn down after the new primary path is established.

CSPF must be enabled to find a more optimal path.

The traffic is switched to R1-R3-R5-R6 in an MBB fashion.

PSNPs are used on point-to-point links to acknowledge the receipt of an LSP.

There are three types of PSNPs: Level 1, Level 2, and Level 1/2.

A PSNP lists some of the LSPs in the router's database.

PSNPs are used by an IS-IS router to request LSP information from a neighboring router.

100Mbps

200Mbps

300Mpbs

600Mbps

700Mbps

The PLR sends it downstream with the RRO.

The PLR sends it downstream with the ERO.

It associates all detours with the source PLR.

The MP sends it upstream with the RESV message.

Message-IDs replace individual refresh messages.

Refresh reduction applies only to reservation messages.

RSVP generates a summary-refresh message for each LSP.

An LSP state change causes an incremented Message-ID.

By defining new LSAs for the IS-IS protocol.

By utilizing the OSPF opaque LSAs to maintain interoperability with OSPF routing domains

By defining new TE extension TLVs to the IS-IS protocol.

By enabling CSPF algorithm extensions that allow link state TE to be implemented.

The MTU does not match on both interfaces.

OSPF is not enabled on one of the routers.

The router ID is the same on both routers.

An OSPF Hello has not been received from the neighbor.

The interfaces are configured as point-to-point on one side and broadcast on the other.

configure router tunnel

configure router gre

configure router rsvp-te

configure router transport-tunnel

configure router mpls

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.

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.

VPLS supports point-to-point connections.

VPLS supports multipoint-to-multipoint connections

VPLS supports a distributed service

VPLS supports a local service on a single node.

There are three types of LSPs: L1, L2 and L1/L2.

An LSP packet contains the ATT bits and the IS-type bits.

The lower the LSP sequence number, the more current the update.

Separate databases are maintained for L1 „ L2, and L1/L2 LSPs.

Priority of 0

Priority of 1

Priority of 64

Priority of 255

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment. The DR for this segment would be the router with router ID 10.10.10.5.

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment; however, this command does not indicate whether 10.10.10.3 or 10.10.10.5 is the DR or BDR.

The router R6 interface is in a multi-access segment. It is the BDR, which is why it is not adjacent to the other routers.

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment. The DR for this segment would be the router with router ID 10.10.10.3.

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.

Not so stubby area

Stub area

Backbone area

Normal area

Routers R1 and R2 are in different areas,

Routers R1 and R2 are in the same area.

Routers R1 and R2 will send a Level 1 Hello PDU and Level 2 Hello PDU, if the interface type between them is point-to-point.

Routers R1 and R2 will send a Level 1 Hello PDU and Level 2 Hello PDU, if the interface type between them is broadcast.

Routers R1 and R2 will send a Level 1/2 Hello PDU, if the interface type between them is broadcast.

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

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

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

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

RIPv2-TE

CSPF

OSPF-TE

ISIS-TE

RSVP-TE

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.

An IES requires a spoke SDP.

A virtual route table must be configured for an IES service.

An IES service must use static routes to communicate with customer networks.

An IES must have at least one SAP defined.

3

4

6

8

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:0

sap 1/1/1:1

IPCP

LDP

PPP

TLDP

Initializing

Up

Down

2-Way

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.

The router 10.10.10.1 is a PLR providing node protection for the router 10.10.10.3.

One-to-one fast reroute protection is requested by an LSP.

The bypass-link tunnel is used to avoid the link with the egress interface address 10.3.4.4.

The bypass-node tunnel is used to avoid the next-hop downstream router 10.10.10.3.

Configure an autonomous system number in the global context.

Configure a BGP group and peer parameters.

Configure a VPN-IPv4 address family.

All of the above steps are mandatory.

None of the above steps are mandatory.

6VPE is a tunneling technology that makes use of MPLS tunnels to transport IPv6 information over an IPv4 MPLS infrastructure.

Customers connected to 6VPE could run native IPv6 or IPv4.

On the PE router, the next hop for a VPN IPv6 address is an IPv6 address, regardless of the nature of the network between the PEs.

6VPE requires an IPv6-aware MPLS core.

Both C and D are false.

All of the above statements are true.

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.

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

Link protection tunnels are only requested for a primary LSP path.

Link protection tunnels can be created for both one-to-one or facility Fast Reroute.

Link protection tunnels detour around a failed next downstream router.

Service ID

Customer ID

SAPID

VC-ID

SDPID

The router does not have a route to reach to the peer 10.10.10.2/32.

The router does not have a route to reach to the prefix 192.10.1.2/32.

The router does not have an export policy defined to export the prefix 192.10.1.2/32 into LDP.

The router receives an invalid label for the prefix 192.10.1.2/32 from its peer.

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.

config>router#

config>qos#

config>port#

config>service#

A physical port.

ASAP.

Ingress MPLS frames with a specific label.

Entries that match an IP filter.

Entries that match a MAC filter.

All of the above can be used as a mirror source.

Conservative label retention

Liberal label retention

Downstream on demand

Downstream unsolicited

The customer maintains complete control over routing.

The adding of new sites is simplified; no re-configuration is required at existing sites.

The clear demarcation of functionality between service provider and customer makes troubleshooting easier.

All of the above.

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.

L1 routers in the same area

L1 routers in other areas

L2 routers in the same area

L2 routers in other areas

L1/L2 router in the same area

L1/L2 routers in other areas

IPv6 uses the Address Resolution Protocol to resolve the address to a MAC address.

A Neighbor Discovery message is sent to the broadcast MAC address. The host with the IPv6 address responds with a Neighbor Advertisement message.

A Neighbor Discovery message is sent to the solicited-node multicast address. The host with the IPv6 address responds with a Neighbor Advertisement message.

A Neighbor Discovery message is sent to the anycast address for the LAN. The host with the IPv6 address responds with a Neighbor Advertisement message.

IPv6 addresses do not need to be resolved to a MAC address.

Hello, link state update, link state packet, link State acknowledgement, database description.

Link state update, link state refresh, link state acknowledgement, database description, notification.

Hello, link state refresh, link state update, link state acknowledgement, link state authentication.

Hello, link state update, link state request, link state acknowledgement, database description.

5 and 15 seconds

10 and 30 seconds

5 and 20 seconds

10 and 40 seconds

Convergence is triggered when the adjacency between routers R1 and R2 drops as a result of Hello timeouts. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.

Convergence is triggered when the physical interfaces between routers R1 and R2 go down. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.

Convergence will not be triggered because switches cannot run routing protocols between them.

Convergence is triggered when the switches notify the routers about the link state information. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged

Convergence is triggered when an LSA is sent from router R1 to router R2 to indicate that the link is down. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.