4A0-C01 Sample Questions Answers

configure router static-route 139.120.121.0/24 next-hop 138.120.199.2

configure router static-route 139.120.121.0/24 next-hop 138.120.199.1

configure router static-route 138.120.199.2/24 next-hop 138.120.199.1

configure router static-route 139.120.121.0/24 next-hop 139.120.121.2

When a router receives updates from its neighbors, it adds them to its link state database, performs an SPF computation, and sends the results to its neighbors.

An SPF computation is done by each router to determine the best path to destination networks. All the best paths determined by the SPF calculation will be seen in the route table.

Each router constructs its own link state database with updates received from neighbors.

An SPF computation is done by each router to determine the best path to destination networks. All the best paths determined by the SPF calculation will be offered to the route table manager.

0

5

10

15

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.

The router installs two routes for the destination with two different next hops. A hashing algorithm is used to distribute traffic over the two paths.

The router installs two routes for the destination with two different next hops. Traffic is evenly distributed over the two paths.

The router installs four routes for the destination with four different next hops. A hashing algorithm is used to distribute traffic over the four paths.

The router installs four routes for the destination with four different next hops. Traffic is evenly distributed over the four paths.

The router installs one route for the destination. Traffic is evenly distributed over the two paths.

Router R1

Router R2

Routers R1 and R2

Router R4

Use a prefix list on router R1 to discard all ingress IS-IS routes.

Use an export policy and prefix list on router R1.

Use an import policy and a prefix list on router R1.

This is not possible because IS-IS cannot use import policies.

0

5

10

15

IES does not support QoS.

IES has a configurable IP-MTU

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

An IES interface has an IP address assigned to it.

Use an import policy and a prefix list on router R1 to reject this route.

Use a prefix list on router R1 to discard all ingress IS-IS routes.

Use an export policy and prefix list on router R1 to reject this route.

This is not possible because RIP cannot use import policies.

MPLS Echo Request packets are sent within the RSVP-TE tunnel that is signaled for "lsp-toR2".

MPLS Echo Request packets are sent within the LDP tunnel that is signaled for Mlsp-toR2".

MPLS Echo Request packets are IP-routed to the destination address of "lsp-toR2".

MPLS Echo Request packets are sent to the destination address of "lsp-toR2" over TCP.

MAC learning.

Maintain a different Forwarding Data Base for each service

ARP mediation.

Maintain a different Routing Information Base for each service.

49.0012.1234

49.0012

12.1234

1234

49.1234

Router LSA

Network LSA

C Summary network LSA

Summary router LSA

Type 5 (AS external) LSAs

Area ID W B.

Hello and Dead intervals PC.

Stub flag

Checksum values

The list of neighbors

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

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

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

The router updates its database with the LSP and acknowledges it with a PSNP.

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.

1

49

83

0

Not So Stubby Areas

Level 1 Areas

Stub Areas

Partially Stubby Areas

The router with the lowest priority is the DR.

The router with the highest priority is the DR.

If priorities are the same, the DR is chosen based on the lowest RID.

If priorities are the same, the DR is chosen based on the highest RID.

Router R6 to router R3 will follow (R6-R5-R2-R3). Router R3 to router R6 will follow (R3- R2-R5-R6).

Router R6 to router R3 will follow (R6-R5-R2-R3). Router R3 to router R6 will follow (R3-R4-R2-R5-R6).

Router R6 to router R3 will follow (R6-R5-R2-R3). Router R3 to router R6 will follow (R3-R4-R7-R5-R6).

Router R6 to router R3 will follow (R6-R5-R7-R4-R3). Router R3 to router R6 will follow (R3-R4-R7-R5-R6).

The OSPF internal preference

The IS-IS Level 1 internal preference

The IS-IS Level 2 internal preference

The OSPF external preference

The IS-IS Level 2 external preference

The IS-IS Level 1 external preference

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.

Option A

Option B

Option C

Option D

The neighbor's link-state database has newer information than what it received in the update.

The neighbor sends the update as an acknowledgement.

The neighbor's update indicates that it has run out of space in its LSDB.

The neighbor's update indicates that the sequence number received is the same as the one already in its link-state database.

10.10.10.2

10.10.10.3

10.10.10.4

10.10.10.6

There is no ASBR configured in the network.

Next Header

Traffic Class

Hop Limit

Fragment Offset

Flow Label

LSR

LER

eLER

iLER

CE

1

2

3

4

Route redistribution is only needed if Internet access is a requirement.

Route filtering is the process of attaching data path filters to router interfaces.

Route filtering involves deciding whether to permit or deny certain routing updates from being accepted into, or distributed out of, the route-selection process.

Redistribution is needed for exchanging routes from one routing protocol to another.

OSPF routers that are redistributing routes must be configured as ABRs.

0

1

2

3

4

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 router with the highest system ID.

The router with the highest loopback address.

The Hello packet with the highest sequence number.

The existing DIS remains the DIS.

The router with the highest interface MAC address.

Different authentication types are not possible because IS-IS only supports password authentication.

An adjacency will not be formed.

The two routers negotiate the authentication type and then reach the up state.

Only an L2 adjacency will form, as long as both routers are L2 capable.

Router R1

Router R2

Router R3

Router R4

Router R5

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

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.

Router R3 will install the OSPF route in its routing table.

Router R3 will install the IS-IS route in its routing table

Router R3 will install an OSPF route and an IS-IS route in its routing table.

There is not enough information to answer the question.

Administrative Groups

Shared Risk Link Groups

Strict hop LSP paths

Fast reroute

A Type 4 LSA is originated by an ABR to describe a route to an ASBR to routers outside the area.

A Type 4 LSA is originated by an ASBR to describe a route to itself to routers outside the area.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the backbone area to provide routing information.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the stub area to provide routing information.

0

1

2

3

4

Tunnel ID

Name

LSP ID

To

The vc-id on the mesh-sdp must be explicitly configured.

The vc-id on the mesh-sdp is automatically assigned by a PE using the service id.

The VPLS service id, on all PE routers, does not have to match.

The VPLS service id, on all PE routers, must match.

If dynamic signaling is required, the signaling on all PE routers must be set to TLDP in the configuration of the SDPs.

The signaling on all PE routers will default to TLDP in the configuration of the SDPs; therefore, no configuration change is required for dynamic signaling.

The router can reach prefix 192.10.1.2/32 through a RSVP-TE tunnel.

The router can reach prefix 192.10.1.2/32 through an LDP tunnel.

The router 10.10.10.2 is the egress router of the prefix 192.10.1.2/32.

The Isp-ping tool is used to perform a unidirectional LSP test.

iLER

LER

LSR

PE

eLER

show service id 5

show service ies

show service service-using ies

show service id 5 base

Router R3 will install the IS-IS route in it's routing table.

Router R3 will install the OSPF route in it's routing table.

Router R3 will install an OSPF route and an IS-IS route in it's route table.

There is not enough information to answer the question.

The router with the least number of links.

The router with the lowest router ID.

The router's closest neighbor.

The router doing the calculation.

Fixed filter

Shared explicit

Standby explicit LSP

Preemptive filter

Link capacity filter

Incoming label

Outgoing label

Incoming interface

Outgoing interface

IOM

CPM

FIB

SPF

The adjacency state is two way because both routers have received a database description packet.

The adjacency is in the exchange state. The next step is to exchange link state request and link state update packets.

The adjacency is in the ex start state. The routers have exchanged database description packets, but still have to negotiate the starting sequence number.

The adjacency state is full. The routers are exchanging database description packets to notify each other that all link state advertisements have been received.

MTU mismatch

Incorrect subnet mask

System interface not included in OSPF

Area ID not the same

Different metric set on each end of the link

Router ID not defined

Area addresses TLV

Intermediate system neighbors

TLV Authentication information TLV

Intermediate system neighbors

TLV Area addresses

TLV LSP entries TLV

The IP internal reachability information

TLV Area Addresses

TLV Authentication Information TLV

The IP external reachability information

TLV Area addresses

TLV Intermediate system neighbors TLV

Data traffic from network 192.168.1.0/24 to 192.168.3.0/24 will be forwarded through router R2.

Data traffic from network 192.168 3.0/24 to 192.168.1.0/24 will be forwarded from router R3 directly to router R1.

The system interface of routers R1 and R3 must be included into OSPF for traffic to flow between the 192.168.1.0/24 and 192.168.3.0/24 networks.

The OSPF adjacency between router R1 and router R3 is operationally up.

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.

Router R2 needs a static route to the PC.

Router R2 needs a default to router R1.

Router R1 needs a default route to router R2.

The static route should use a next-hop of 172.31.1.2

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

100Mbps

200Mbps

300Mpbs

600Mbps

700Mbps

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

TRUE

FALSE

The router's system address.

The next-hop prefix.

The interface's global prefix.

The next-hop system address.

Label allocation and management.

Label swapping.

Pushing a label on an unlabeled packet.

Label signaling.

Routing lookups.

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

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

The policy was not "committed" after creation.

Router R1 cannot reject the route because OSPF does not support import policies

Yes. A routing policy is required to advertise routes between PE routers in a VPRN

No. A routing policy is not required; the default behavior on the 7750 SR is to advertise all VPRN routes between PE routers.

A routing policy is required only when BGP is used as the PE-CE routing protocol, as shown in the exhibit.

A CE1 system interface can not be advertised to PE2 since the CE routers are not aware of the VPRN.

Router R4 will have a route to router R6's system address with router R2 as the next-hop.

Router R4 will have a default route with router R2 as the next-hop.

Router R4 will have a default route with router R3 as the next-hop.

Router R4 will not have a route to router R6's system address, nor will it have a default route.

1

2

3

4

6

7

It represents a group of routers on the same non-broadcast network.

It represents the topological database of the backbone network in an IS-IS network.

It represents a broadcast sub-network.

It represents the complete topology of an IS-IS area.

A BDR is always required on point-to-point links.

The second highest RID is always the BDR.

The BDR only listens for link-state updates sent to 224.0.0.5.

The BDR always acknowledges link-state updates from the DR

Initializing

Up

Down

2-Way

show router route-table

show router Idp bindings

show service service-using

show service egress-label

show router rsvp session

The OSPF internal preference

The IS-IS Level 1 internal preference

The IS-IS Level 2 internal preference

The OSPF external preference

The IS-IS Level 2 external preference

The IS-IS Level 1 external preference

5000

5004

5008

5018

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.

The head office has a default route and the branch office has a specific static route.

The head office and the branch offices both have specific static routes.

The head office and the branch office both have default routes.

The head office has a specific static route and the branch office has a default route

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.

Independent control mode.

Ordered control mode.

Liberal label retention.

Conservative label retention.

Downstream on demand

Fixed total of 128 bits, where 64 bits are used for routing and 64 bits are used as an interface identifier.

Fixed total of 128 bits, where 32 bits are used for the global prefix, 32 bits are used for the subnet and 64 bits are used as an interface identifier.

Variable total length, where at least 48 bits are used for the global prefix, 48 bits are used for the subnet and 64 bits are used as an interface identifier.

Variable total length, where at least 64 bits are used for routing and 64 bits are used as an interface identifier

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.

Liberal label retention mode

Conservative label retention mode

Ordered control mode

Independent control mode

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

By default, the VC ID on the mesh SDPs of a VPLS are set to the service ID.

A VPLS appears to the customer as a direct Ethernet connection.

Mesh SDPs are used for VPLSes to avoid loops.

By default, T-LDP is used for signaling service labels.

A "remote-source" needs to be added to the mirror destination on PEL

A mirror source needs to be added to PE1 with a "remote-source".

This is not possible since the protocol analyzer is located at the Central Office. It needs to be at the customer site.

A mirror source with SAP 1/1/2 needs to be added on PEL

A route target is used to distinguish to which VRF table a prefix belongs.

A route target appended to an IPv4 prefix produces a VPN-IPv4 prefix.

Multiple route targets can be part of a single MP-BGP update.

Route targets must be configured for VPRNs.

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.

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

It tests the reachability of hosts that are using an SDP.

It tests the reachability of the far-end IP address of an SDP through its tunnel.

It can be used by specifying only an SDP ID.

Mesh SDPs assist MAC learning by flooding traffic to other mesh SDPs.

A PE keeps a single FDB for all VPLSes it has.

Frames received on a SAP that are broadcast, multicast or unknown are flooded.

The FDB only stores the MAC addresses of remote sites.

Black hole

Default gateway

Gateway path

Proxy ARP

Neighbor, adjacency, route table

Neighbor, topology, forwarding

Topology, routing, forwarding

There are only two databases: adjacency and topology

Label space mode

Label retention

Control mode

Keepalive factor

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.

LSA flooding mechanism.

Totally stubby areas.

MD5 authentication.

DR and BDR election.

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"

OSPFv3 uses MD5 Authentication.

Router LSAs carry IPv6 prefix information.

NSSA is supported in OSPFv3.

OSPFv3 uses a 64-bit router ID.

10.10.10.2

10.10.10.3

10.10.10.6

There is not enough information given to determine the designated router.

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

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

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

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

The egress RSVP interface has 80 percent bandwidth unreserved.

LSPs can reserve an additional 9.9 Gbps bandwidth on this RSVP interface.

The head end reserves 100Mbps for the LSP

The egress RSVP interface has 1 Gbps bandwidth unreserved.

Backbone

NSSA

Stub

Totally stubby

Type 1 Router LSA

Type 2 Network LS A

Type 3 Summary LSA

Type 5 External LSA

Exchange

Up

Down

2-Way

Router R2 needs a static route to the PC.

Router R2 needs a default to router R1.

Router R1 needs a default route to router R2.

The static route should use a next-hop of 172.31.1.2

Router R1 to router R7 will follow (R1-R2-R4-R6-R7). Router R7 to R1 will follow (R7-R6-R4-R2-R1)

Router R1 to router R7 will follow (R1-R2-R4-R6-R7). Router R7 to R1 will follow (R7-R6-R5-R3-R1)

Router R1 to router R7 will follow (R1-R3-R5-R6-R7). Router R7 to R1 will follow (R7-R6-R4-R2-R1)

Router R1 to router R7 will follow (R1-R3-R5-R6-R7). Router R7 to R1 will follow (R7-R6-R5-R3-R1)

There are five broadcast links and there are no point-to-point links.

There are five broadcast links and there are five point-to-point links.

There are five broadcast links. It's not possible to say how many point-to-point links there are.

It's not possible to say how many broadcast or point-to-point links there are.

Intra-Area Prefix LSA

Router LSA

AS External LSA

NSSA LSA

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

AS External

Inter-Area Prefix

Inter-Area Router

Intra-Area Prefix

AFI

IDI

HO-DSP

NSEL

Router R2 has two IS-IS-adjacencies and two LSPs.

Router R2 has two IS-IS-adjacencies and four LSPs.

Router R2 has two IS-IS-adjacencies and three LSPs.

Router R2 has four IS-IS-adjacencies and six LSPs.

Mirror slicing is used to logically separate a port that is being monitored.

Mirror slicing configuration is earned out in the mirror destination.

By default, mirror slicing is enabled so that only the protocol headers of data traffic are replicated to a mirror port.

The maximum number of mirror slices that can be made on a network and access port are 256 and 8, respectively

Customer ID and SAP ID.

Customer ID and Service ID.

SAP ID and Service ID.

SDP ID and Service ID.

SDP ID and SAP ID.

SDP ID and VC ID.

Service providers can apply QoS, ingress/egress traffic shaping and policing on a per service basis.

Different customers with overlapping address space can be accommodated.

There is a clear demarcation of customer and service provider networks.

Customers can connect to the same service using different subnets.

The VRF is a virtual router on the PE router that contains the customer's routes for the VPRN

Each PE maintains multiple VRFs based on the number of PE peers it connects to.

Each PE has a VRF for each VPRN service provisioned on the router.

All of the above.

Only A and C.

Only A and B

P routers run IPv4 only. PE routers run IPv4 only and exchange IPv6 routes using MP-BGP.

P routers run IPv4 only. PE routers run both IPv4 and IPv6 and exchange IPv6 routes using MP-BGP.

P routers run IPv6 only. PE routers run both IPv4 and IPv6 and exchange IPv4 routes using MP-BGP.

P routers run IPv6 only. PE routers run IPv6 only and exchange IPv4 routes using MP-BGP.

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.

LSP-3 takes R1-R3-R5-R6 and LSP-4 has no available path.

LSP-3 takes R1-R2-R4-R6 and LSP-4 has no available path.

0

2

3

4

CAC is used when the LSP path has not been computed by CSPF.

CAC is used when the LSP path has been computed by CSPF.

CAC is used to perform a bandwidth check on each egress interface of the downstream router.

CAC is used to perform a bandwidth check based on the router's LSDB.

sap 1/1/1:0.*

sap 1/1/1

sap 1/1/1:*.4

sap 1/1/1:4.*

Enable traffic engineering on all routers along the LSP path.

Enable CSPF on the head-end router.

Configure a path definition on all routers along the LSP path.

Enable MPLS and RSVP on all routers along the LSP path.

TRUE

FALSE

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.

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.

R1, R2, and R4 can be PLRs; R6 is the MP.

R1, R2, and R4 can be PLRs; R2, R4, and R6 are MPs.

R1, R2, R3, R4, and R5 can be PLRs; R6 is the MP.

R1, R2, R3. R4, and R5 can be PLRs; R2, R4, and R6 is the MP.

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.

The path must include at least one hop.

The path may be used for multiple LSPs.

The path may be used multiple times in a single LSP.

The path must define a tunnel destination IP address.

TRUE

FALSE

LDP

BGP

MP-BGP

MPLS

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

Customers connected to 6VPE can run IPv6 or IPv4.

On a PE router, if the MP-BGP next hop is an IPv4 address, a mapped IPv6-compliant address will be used.

6VPE implements its own VPN-IPv6 address family and is a replacement for MP-BGP.

VPN-IFV4 allows multiple customers to have overlapping IP addresses.

CE routers use VPN-IPv4 prefixes to differentiate between services.

PE routers are responsible for creating VPN-IPv4 prefixes.

A VPN-IFV4 prefix is composed of a route distinguisher (RD) and an IPv4 address.

An IES provides a Layer 3 interface to a customer.

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

An IES supports QoS.

An IES interface's IP address, if bound to a port, will appear in the routing table.

TRUE

FALSE

Customers must use the same routing protocol as the service provider.

Customers belonging to the same VPRN service must use the same subnet.

Service providers only need to perform configurations on the PEs to add additional VPRNs.

For each VPRN, only one customer can be connected at each PE.

F-pipes use SAPs in the form of port: DLCI (e.g. 1/2/3:65).

To the customer, the PE appears as a native Frame Relay UNI (User Network Interface).

Multiple Frame Relay circuits can be mapped to a single F-pipe service on the Alcatel-Lucent 7750 SR.

The MPLS control word is required because the Frame Relay header is not encapsulated in the frame.

Configuring an Epipe service with a customer ID

Defining a SAP or SAPs.

Binding to an SDP if it is a distributed service.

Enabling the service using the no shutdown command.

Creating and assigning an IP filter to the SAP.

Configuring QoS parameters

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.

Route distinguishes are appended to IPv4 prefixes to form IPv6 prefixes.

CE routers use a route distinguisher to indicate which VPRN they are associated to.

A route distinguisher combined with an IPv4 prefix produces a VPN-IPv4 prefix.

Route distinguishes are used to determine which routes a VPRN should import.

The frame is dropped.

The service ID is added as the provider VLAN tag.

A VLAN tag of 0 is added as the provider VLAN tag.

The frame is forwarded with no provider VLAN tag.

Option A

Option B

Option C

Option D

A-pipe

E-pipe

I-pipe

F-pipe

C-pipe

The labels are of local significance only, so other routers can use the same value.

10.10.10.1 has yet to send its own unique label.

Router R4 is using the same tunnel to send and receive to 10.10.10.1.

The service on 10.10.10.1 is down, so it is rejecting packets.

They are signaled between PE devices using MP-BGP.

They are swapped at each P router as a packet crosses the service provider network.

They are also known as the inner label or service label.

They indicate to the egress PE the VPRN to which a packet belongs.

sap 1/1/1:0

requires both sap 1/1/1:0 and sap 1/1/1:*

sap 1/1/1:0-4096

sap 1/1/1:*

3

4

6

12

It will show the hops taken between service endpoints.

It will test the delay across the service.

It will test the SDPs of a service in both directions.

It will test the round-trip connectivity of the service.

Tunnel Label

VC Label

Operational Control Word

VPI

VCI

The router has new entries added for the given FEC in its LIB.

The router has new entries added for the given FEC in its FIB.

The router generates a single label for the given FEC and advertises it to all its peers,

The router has multiple LSP tunnels for the given FEC.

Apipe

Fpipe

Cpipe

Epipe

Bridge service

Label

Frame check sequence

Traffic Class (previously called Experimental)

Time To live

Bottom of stack bit

LDP is not configured on R2.

R2 does not have a route to 10.10.10.3.

LDP is not configured on R3's interface to R2.

The targeted session is not configured on R2.

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.

A VPLS service does not use an FDB.

An FDB is maintained on the PE router to track MAC addresses learned from all traffic through the router.

An FDB is maintained on the PE router to track MAC addresses learned from all VPLS services on the router.

A separate FDB is maintained for each VPLS service to track MAC addresses learned from each service.

For each VPLS service, two FDBs are maintained to track MAC addresses; one for unicast traffic and one for multicast and broadcast traffic.

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

A OSPF Hello has not been received from the neighbor

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

Not so stubby areas

Level1 area WC

Stub areas

Partially stubby areas

Level 2 areas

An L1/L2 router can have neighbors in different areas.

An L1/L2 router calculates separate SPF trees for the Level 1 and Level 2 topology.

An L1/L2 router advertises its L2 routes to its L1 neighbors.

An L1/L2 router sets the ATT bit in L1 LSPs to identify itself as an L1 router.

224.0.0.5

224.0.0.6

224.0.0.9

224.0.0.10

RIPv2 does not have support for multicast

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.

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.

To support classful routing protocols.

To allow IP routes to be defined using any number of bits for the network portion of the address.

To allow interdomain routing between an IGP and EGP such as OSPF and BGP.

To simplify the allocation of IP address space by defining a fixed size for the network portion of the address for each of the address classes.

The router with router ID 10.10.10.5 is an ASBR.

The router with router ID 10.10.10.3 is an ASBR.

The router with router ID 10.10.10.5 originated the AS summary LSA in its own area.

The router with router ID 10.10.10.4 is in the same area as the router with router ID 10.10.10.5.

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.

Hello, Link State Update, Link State Packet, Link State Acknowledgement, Database Descriptor

Link State Update, Link State Refresh, Link State Acknowledgement, Database Descriptor, 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 Descriptor

A policy statement within the router identifying what is to be advertised

Access-lists denoting what is to be advertised

Default metrics for each link

A group and neighbor statement for each peer

Level 0

Level 1

Level 2

Level 0/1

Level 1/2

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

A packet with a destination anycast address is sent to all nodes on the local link.

A packet with a destination anycast address is sent to all nodes on the local network.

A packet with a destination anycast address is sent to all nodes that have joined the anycast group.

A packet with a destination anycast address is sent to the nearest node that is assigned the anycast address

A packet with a destination anycast address is sent to all nodes that are assigned the anycast address.

True

False

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.

Router LSA

Network LSA

Summary Network LSA

Summary Router LSA

Router R3's routing table can only contain one of the routes, which will result in route flapping.

Router R3's routing table will have one entry for 10.1.1.0/24 and one entry for 10.1.2.0/24.

The networks will be represented with one entry of 10.0.0.0/8 in router R3's routing table.

The networks will be represented with one entry of 10.0.0.0/24 in router R3's route table.

Whatever the advertised metric happens to be.

A value of 1.

This must be administratively set as there is no default value.

A value of 15.

Router R2 does not have a route to the system address of router R1 and therefore cannot respond to the ping.

There is no default route configured on the PC.

Router R2 does not have a route configured to the PC.

Router R1 needs to be configured with a default route.

224.0.0.5

224.0.0.6

The unicast IP address of the interface the update is being sent on.

The system address of the router

OSPF uses TCP, so the protocol number is 6.

OSPF uses UDP, so the protocol number is 17.

OSPF does not use IP.

OSPF has its own protocol number of 89.

5 and 15 seconds

10 and 30 seconds

5 and 20 seconds

10 and 40 seconds

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.

The DIS creates a logical node to represent a group of routers on the same non-broadcast network; this node is the pseudonode

The DIS creates a logical node to represent the topological database of the backbone network in an IS-IS network; this node is the pseudonode

The DIS creates a logical node to represent a broadcast sub-network; this node is the pseudonode

The DIS creates a logical node to represent the complete topology of an IS-IS area; this node is the pseudode

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.

DSCP marking

Class of Service Marking

DSAP marking

ICMP type

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.

Show ospf neighbors

Show router ospf neighbors

Show router ospf adjacency

Show ospf adjacency

As soon as the LSP is transmitted.

When an acknowledgment is received in the form of PSNP.

When an older LSP is received.

When a newer or same aged LSP is received.

Only when a newer LSP is received

Option A

Option B

Option C

Option D

The route policy should be applied as in import policy

The no-redistribute-external command is used on router R1

The route policy is incorrect. It should say "from protocol ISIS" rather than "from protocol direct".

It is not possible to be an ASBR and an NSSA. The ASBR configuration should be removed.

The interface between routers R1 and R3 needs to be in OSPF area 0 rather than OSPF area 1 because a backbone area must always exist.

One.

One for each of the routers in area 0

One for each of the external routes exported by router R1.

Type 4 LSAs are not generated in this network topology.

Manual route summarization can only be done on autonomous system border routers.

Manual route summarization must be done on all the backbone routers to be effective. Manual route summarization is optional on the routers in non-backbone areas.

Manual route summarization is done on the ABRs. By default, automatic summarization is done; however, it may not be optimal for all networks.

Manual route summarization is done on the ABRs. By default, no route summarization is done and all routes are advertised to all areas.

When two areas need to communicate and there is no area 0.

When an area needs to traverse another area to reach area 0.

When two areas are connected to area 0, but there is no direct path between them.

When an area needs to connect directly to another area without using area 0.

The LSP can use protection tunnels used by other LSPs.

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

The LSP is limited to link protection.

A detour protection tunnel is created for this LSP.

A mechanism that implements opaque LSAs.

A mechanism that computes routes based on specified requirements.

A mechanism that ensures the IGP best route is used.

A mechanism that enables LDP signaling to use a route other than the IGP best route.

R4 (10.10.10.4) has established a link protection tunnel.

R6 (10.10.10.6) has established a link protection tunnel.

R2 (10.10.10.2) has established a node protection tunnel.

R1 (10.10.10.1) has not established a node protection tunnel.

The frame is dropped.

The service ID is added as the VLAN tag.

A VLAN tag of 0 is added as the provider VLAN tag

The frame is forwarded with no VLAN tag

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.

Local FECs not included in the 192.168.1.0/24 address space and the system IP FEC.

Only the system IP FEC appears in the LIB.

Any local FECs, except those with a 24-bit mask.

Local FECs in the 192.168.1.0/24 address space.

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.

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.

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.

A packet arriving with label 131066 will be forwarded out interface 1 /1 /4 with label 131070.

The router is an egress router for FEC 10.10.10.221/32.

There are multiple LSPs to reach FEC 10.10.10.244/32.

The router's system address is 10.10.10.242/32.

Configure service sap sap-id access

Configure port port-id Ethernet mode access

Configure port port-id Ethernet mode network

Configure port port-id mode access

Configure port port-id mode network

A logical entity that provides a uniform, end-to-end configuration, management and billing model for provisioning either Internet or VPN connectivity.

Provides connectivity between customer access points.

A service that can either be local or distributed.

All of the above

Link-based and T-LDP sessions may be configured on the same LSR.

T-LDP supports sessions between non-directly connected devices.

T-LDP can be configured between directly connected devices.

T-LDP Hello messages are sent to a multicast address.

LSP 1 will follow R1-R3-R4-R5. LSP 2 will follow R1-R2-R5.

LSP1 will follow R1-R2-R5. LSP 2 will follow R1-R3-R4-R5.

Both LSP 1 and LSP 2 will follow R1-R2-R5.

Both LSP 1 and LSP 2 will follow R1-R3-R4-R5.

Provides a mechanism to determine the hops an SDP traverses.

Provides in-band uni-directional connectivity tests.

Provides in-band round-trip connectivity tests.

Tests ability of reaching the far-end IP address of an SDP ID within the SDP encapsulation.

Provides information regarding the exact MTU supported between service ingress and service termination.

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.

The mirror destination configuration on PE5 is missing the "remote-source" command.

There needs to be a mirror source configuration on PE5 with the "remote-source" command.

This is not possible since the protocol analyzer is located at the Central Office. It needs to be at the customer site.

There needs to be a configuration command to put sap 1/1/3 on the mirror destination of PE5.

There needs to be a configuration command to put sap 1/1/3 on the mirror source of PE5

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:*.0

sap 1/1/1:0*

sap 1/1/1:0

An SDP does not have a path-mtu

The path-mtu must be set by the administrator.

By default, the path-mtu is calculated automatically from the network port MTU of the PE router.

The path-mtu is calculated based on the service MTU of the service using the SDP.

The path-mtu is signaled between the PE endpoints when the service is established.

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.

Label space mode

Label retention

Control mode

Keepalive factor

Router R3 starts the LDP-Sync timer after recovering the LDP session on R3-R6.

Router R1 continues to use R1-R2-R4-R6 until the LDP-Sync feature is disabled.

Router R3 advertises the maximum metric for the link to router R6.

Router R1 receives a label from router R3 after the LDP session is established on R3-R6.

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.

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.

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.

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.

MPLS data traffic will be discarded until the IGP finds a new next-hop to router R3.

MPLS data traffic will be discarded unless the LDP tunnel has a standby secondary path.

MPLS data traffic will not be discarded because router R1 received labels from both next-hops, routers R2 and R3.

MPLS data traffic will not be discarded because of fast reroute capability on router R2.

1

2

3

4

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 is not a fully strict path.

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

Per-platform label space, conservative retention mode

Per-interface label space, conservative retention mode

Per-platform label space, liberal retention mode

Per-interface label space, liberal retention mode

distributed/virtual

local/sub

routed/Layer 3

distributed/routed

Layer 2/loopback

Assign an admin group to a MPLS interface.

Configure CSPF on the LSP.

Configure at least one strict hop on the LSP path.

Configure an "include" or "exclude" statement on the LSP path.

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.

All routes in the VRF are advertised to the PEs and CEs.

No routes in the VRF are advertised to the PEs or to the CEs.

All routes in the VRF are advertised to the PEs, but not to the CEs.

All routes in the VRF are advertised to the CEs, but not to the PEs.

Yes, A routing policy is required to advertise routes between PE routers in a VPRN regardless of the CE-PE routing.

Yes, A routing policy is required in this case because BGP is used as the PE-CE routing protocol.

No, a routing policy is not required. By default, the Alcatel-Lucent 7750 SR will advertise all VPRN routes between PE routers.

No, a routing policy is not required on PE1, but an import policy is required on PE2.

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.

It drops the frame.

It floods the frame to all PEs participating in the service.

It sends a destination unreachable message back to the originating host.

It sends the frame to the closest neighbor.

Option A

Option B

Option C

Option D

1500

1508

1514

1522

7958

7978

8022

8042

The frame egresses 1/1/1:6.7 with an outer VLAN tag of 6 and inner tag of 7.

The frame is dropped at the egress SAP 1/1/1:6.7.

The frame egresses 1/1/1:6.7 with VLAN tag 5.

The frame egresses 1/1/1:6.7 with VLAN tag 6.

Route distinguishes are used to ensure that VPRN IP prefixes are globally unique.

Route distinguishes are appended to IPv4 prefixes to form IPv6 prefixes.

Route distinguishes are used to determine which routes a VPRN should import.

CE routes use a route distinguisher to indicate which VPRN they are associated to.

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

M-BGP

1

4095

None. This encapsulation is not supported.

The number is limited only by the capacity of the router

LDP

BGP

MP-BGP

MPLS

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.

The traceroute will only show one hop: R5-R6.

The traceroute will only show 2 hops; R5-R1 and R4-R6.

The traceroute will only show 3 hops: R5-R1, R1-R4 and R4-R6.

The traceroute will show one hop for each router in the provider core and one for each CE-PE hop.

A-pipe

F-pipe

C-pipe

E-pipe

Change the service MTU of the VPLS to match the IES.

Set the ip-mtu of the IES service to match the service MTU of the VPLS service.

Change the MTU of the SDP attached to the VPLS to match the service MTU of the VPLS.

Set the DNF flag on the IES service.

An Ipipe is a point-to-point Layer 2 VPN capable of only carrying Ethernet payloads. An Epipe interworking refers to the transportation of ATM/FR traffic over an Epipe.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs.

None of the above.

Option A

Option B

Option C

Option D

Configuring an autonomous system number in the global context.

Configuring a BGP group and peer parameters.

Configuring a VPN-IPv4 address family.

Configuring an export policy to advertise routes between PEs.

DLC Header

Control Word

Transport Label

Service Label

Route targets are carried in MP-BGP updates.

Route targets identify the VRF that a VPN-IFV4 prefix is associated with.

Route targets are communicated between PEs that are part of a specific VPRN.

Route targets identify the egress SAP of a service towards a CE.

A SAP can only be used by one service on a router.

A dedicated SDP needs to be created for each service.

A service is created on each site before the customer is created.

SAPs must be created before a service is created.

To mirror service requirements of a customer with a single branch office and multiple remote sites

To utilize unused ports of a service router until they are required for a service.

To replicate traffic from a service port to another port for debugging or monitoring functions

To ease the configuration burden of services that support a large number of subscribers

All of the above

To advertise VPN-IPv4 and VPN-IFV6 routes, two MP-BGP sessions are required.

PE routers must support both IPv4 and IPv6 addresses; customer routers can use either one.

MP-BGP is used to advertise IPv6 prefixes and the associated VPRN labels.

The provider core routers are IPv6-unaware.

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.

Configuring the physical port in access mode.

Configuring the physical port in network mode.

Enabling the port using the no shutdown command.

Ports are enabled by default, thus no need to use the no shutdown command.

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.

IPCP

LDP

PPP

TLDP

When a PE router receives an IPv4 prefix from its local CE it creates a VPN-IPv4 prefix.

The route distinguisher (RD) is appended to the IPv4 prefix to form a 16 byte VPN-IPv4 prefix.

VPN-IPv4 allows BGP to distinguish multiple routes with the same prefixes originated from distinct customers

VPN-IPv4 addresses are only present within the service provider network.

In VPRN, data traffic is carried in VPN-IPv4 packets.

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:0

sap 1/1/1:1

All SAPs of a VPLS belong to the same broadcast domain.

When a new site is added, all the existing sites need to be shutdown and re-provisioned.

An additional T-LDP session is required between PEs for each additional VPLS that is provisioned.

Multiple VPLSes on the same router share a single MAC FDB.

SAPs can be defined on Ethernet, POS, Sonet/SDH, or TDM channels.

Only one SAP is required for a service that originates and terminates on the same Alcatel-Lucent 7750 SR.

SAPs can have QoS policies assigned to them.

Multiple SAPs can be defined on the same port.

ping

sdp-ping

svc-ping

Isp-ping