4A0-C01 Practice Exam Questions with Answers Nokia NRS II Composite Exam Certification

Ordered control mode; downstream on demand.

Ordered control mode; downstream unsolicited.

Independent control mode; downstream on demand.

Independent control mode; downstream unsolicited.

IS-IS supports VLSM and CIDR.

IS-IS uses OSI addressing.

IS-IS supports manual summarization

IS-IS uses periodic Hello messages.

Router R2 sends an update to 224.0.0.5 on its broadcast and point-to-point interfaces. The DR does not send any updates.

Router R2 sends an update to 244.0.0.5 on its point-to-point interfaces. The DR sends an update to 224.0.0.6 on the broadcast network.

Router R2 sends an update to 224.0.0.5 out its point-to-point interfaces and an update to 224.0.0.6 out its broadcast interface. The DR sends updates to 224.0.0.5 on the broadcast network.

Router R2 sends an update to 224.0.0.6 out its point-to-point interfaces and an update to 224.0.0.5 out its broadcast interface. The DR sends an update to 224.0.0.6 on the broadcast networks.

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Inter-Area Router LSA

AS External LSA

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 1Gbps bandwidth unreserved.

The route learned from IS-IS will be installed.

The route learned from OSPF will be installed.

Both routes will be installed.

There is not enough information to answer the question

Label space mode

Label retention

Control mode

Keepalive factor

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

Administrative Groups

Shared Risk Link Groups

Strict hop LSP paths

Fast reroute

Link State PDUs

Link State Updates

Link State Advertisements

Intermediate System Update Packets

Default path

Default gateway

Gateway path

Proxy ARP

CPM

MDA

Switch Fabric

IOM

Disable route summarization on router R3

Enable LDP aggregate prefix match

Create an import policy to accept these FECs

Disable LDP exact match on the specified FECs

Source IP address

TCP source port

Prefix list

Protocol type

The router is correctly configured.

Neither a reference-bandwidth nor wide-metrics is configured on the router.

A reference-bandwidth is configured on the router but wide-metrics is not.

Wide-metrics is configured on the router but a reference-bandwidth is not.

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

10.10.10.99

10.10.10.66

10.10.10.2

10.10.10.1

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.

TRUE

FALSE

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.

RSVP-TE operates in a downstream unsolicited label advertisement mode.

RSVP-TE makes use of ordered control mode.

RSVP-TE is an MPLS signaling protocol, based on the resource reservation protocol.

RSVP-TE enables the establishment of explicitly routed LSPs that can be automatically routed away from network failures

RSVP-TE supports explicitly routed LSPs using either loose or strict route definitions.

Local FECs, not including those in the 192.168.1.0/24 address space.

Only system ID FECs may appear in the LIB.

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

Local FECs in the 192.168.1.0/24 address space

AFI

IDI

HO-DSP

NSEL

Option A

Option B

Option C

Option D

To give IPv6 traffic preferential routing over IPv4 routes.

To allow core routers running only IPv6 protocols to carry IPv4 traffic.

To give IPv4 only routers the ability to route based on IPv6 addresses.

To allow IPv6 traffic to pass through an IPv4 network.

'asbr' is missing from router R1's configuration.

Router R1 needs to have an export policy added to it.

Router R5 does not have an export policy for these prefixes.

Router R1 needs to have an import policy added to it.

Conservative label retention

Liberal label retention

Downstream on demand

Downstream unsolicited

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.

The LSR regenerates and forwards a new PATH message.

The LSR stores the PATH message in the PSB.

The LSR forwards the PATH message based on the HOP object in the RSB.

The LSR looks up the PATH message's destination IP address in the FIB.

sap 1/1/1:0.*

sap 1/1/1

sap 1/1/1:*.4

sap 1/1/1:4.*

They are multicast to the All Hosts address.

They are broadcast to the subnet broadcast address.

They are multicast to the All Routers address.

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

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

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

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

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

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

No primary path is established. The secondary path will take R1-R2-R4-R6.

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

The primary path will take R1-R2-R4-R6. No secondary path is established.

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

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

Enable fast-reroute on all routers along the path. R1, R2, R4, and R6.

Enable both link-protection and node-protection on router R1.

Enable fast-reroute with either one-to-one or facility mode on this LSP.

Enable link-protection only on router R4.

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

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

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

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

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

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

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

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

Push an additional label onto the label stack.

Pop the label.

Swap the label.

Pop the label and push an additional label onto the label stack.

By default, a 7750 SR does not advertise all routes in the VRF to a CE router.

The default 7750 SR behavior describes all routes in a VRF that are advertised to other PE routers.

By default, a 7750 SR does not advertise all routes in the VRF to other PE routers.

By default, a 7750 SR advertises all routes in the VRF to a CE router.

distributed/virtual

local/sub

routed/Layer 3

distributed/routed

Layer 2/loopback

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

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

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

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

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.

MTU must match on both services,

Mesh-SDP with matching vc-id configured,

Spoke-SDP with matching vc-id configured.

Spoke-SDP.

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.

0x4

0x5

0x10

0xa

1

2

3

4

The router performs a unidirectional LSP test.

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

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

The MPLS TTL values are incremented at each request.

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

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

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

The outer label TTL will be 251 and the inner label TTL will be 251.

The outer label TTL will be 251 and the inner label TTL will be 252.

Each router requires 1 VPLS service.

Each router requires 2 VPLS services.

Each router requires 1 SDP with 2 LSPs, one to each of the other 2 routers.

Each router requires 2 SDPs.

Each router requires 3 SDPs

An OSPF adjacency can be established on an IES interface.

IES allows provider MP-BGP sessions to be extended to customers.

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

An IES interface supports OSPF and IS-IS in passive mode only.

Multiple MP-BGP sessions are required to carry VPN-IPv4 and VPN-IPv6 routes.

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

In 6VPE, MP-BGP is used to advertise IPv6 prefixes and the associated VPRN label.

In 6VPE, the provider core routers are IPv6-unaware.

All of the above statements are true.

All of the above statements are false.

An Epipe that has 2 or more SDPs configured.

An Epipe that has 3 or more SAPs configured.

An Epipe that has 2 SAPs on the same node but no SDPs configured

An Epipe that is configured between two nodes, each having 1 SAP and 1 SDP configured.

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

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

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

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

config>service# epipe service-id enable

config>service# vpws service-id enable

config>service# service-id no shutdown

config>port# port-id no shutdown

config>service# epipe service-id no shutdown

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"

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.

Independent control mode

Ordered control mode

Liberal label retention

Conservative label retention

Downstream on demand.

Link

Intra-Area Prefix

Inter-Area Prefix

Inter-Area Router

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.

Label request message

Notification message

Address message

Keepalive message

Initialization message

Hello message

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.

Tunnel Label

VC Label

Operational Control Word

VPI

VCI

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

125 Mbps

500 Mbps

625 Mbps

2000 Mbps

An IGP route takes priority over a transport tunnel.

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

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

Multiple MPLS tunnels can be installed in the FIB.

They list the RSVP session names that the router is refreshing,

They list the Message IDs that the router is refreshing,

They list the Tunnel IDs that the router is refreshing.

They list the LSP I Ds that the router is refreshing.

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.

Layer 3 direct Internet access service.

Layer 2 point-to-point service.

Layer 2 multipoint-to-multipoint service.

Layer 3 IP multipoint-to-multipoint VPN service.

A data packet will receive a service label at the CE and a transport label at the ingress PE.

A data packet intended for a remote CE will have its service label swapped at each P router along the path towards the egress PE.

At the egress PE, the transport label will be popped and the data packet forwarded with the service label.

The service label is popped by the remote CE. The unlabeled packet is forwarded based on the longest match lookup algorithm in the VRF.

All of the above statements are false.

All of the above statements are true.

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 mirror destination on the local and remote Alcatel-Lucent Service Router,

A mirror source on the local and remote Alcatel-Lucent Service Router.

A mirror source with the remote source specified on the remote Alcatel-Lucent Service Router.

A mirror source with the remote source specified on the local Alcatel-Lucent Service Router.

An SDP between the local and remote Alcatel-Lucent Service Routers.

Tunnel Label

VC Label

Operational Control Word

UNI

NNI

vc-type null

vc-type ether

vc-type vlan

vc-type none

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.

The LSP will go through the path R1-R2-R4-R6.

The LSP will go through the path R1-R3-R5-R6.

The LSP is down because router R1 detects that no path can meet its constraints.

The LSP is down because router R4 detects that no path can meet its constraints.

A route target is a BGP extended community used to identify the VRF table for a prefix at the receiving PE

A route target is a mechanism from which VPRN controls the distribution of VPN routing information.

Route target attributes are earned in a MP-BGP as attributes of the route.

A route target is used by the PE router to identify the VRF that a VPN-lPv4 prefix is associated with.

All of the above statements describe a route target

None of the above statements describe a route target

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 router will switch to Path-2 because it is the first secondary path configured in the list.

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

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

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

Route distinguishes are 12 bytes in length

Route distinguishes are appended to IPv4 prefixes to form 16 byte VPN-IFV1 prefixes.

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

CE routes must be configured with the proper route distinguishes for the VPRN they are associated to

All of the above statements are true.

All of the above statements are false.

It allows link LDP to be configured on the edge devices only.

It is used to signal the transport labels in the provider core.

It allows selective control over which devices are configured for LDP.

It is used to signal the service labels in the provider core.

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.

ISIS, RIP, OSPF, static routes

BGP, ISIS, RIP, OSPF, static routes

BGP, RIP, OSPF, static routes, OSPF3

ISIS, RIP, OSPF, static routes, OSPF3

The number of VPRN routes can become very large. MP-BGP can support a very large number of routes.

MP-BGP can carry routing information for a number of different address families.

MP-BGP is designed to exchange information between routers that are not directly connected. This feature keeps VPRN routing information out of P-routers.

MP-BGP can carry additional information attached to a route as an optional BGP attribute.

All of the above statements are valid reasons for using MP-BGP as a VPRN routing protocol.

Admin groups

Hop-limit

Strict hops

TE-Metric

Path MTU is always calculated from the MTU of the egress network port on the head end PE.

oam sdp-mtu

adspec

cspf

To reduce the number of LDP sessions

To reduce the number of LIB and LFIB entries

To bypass the LDP exact prefix match rule

To export summarized routes from OSPF to LDP

The time router R4 takes to send a PATH Error message toward the head-end router.

The time router R4 takes to detect RSVP Hello message timeout from router R6.

The time router R4 takes to send a RESV Error message to the head-end router.

The time router R1 takes to signal an alternate path through router R3.

Router R1

Router R2

Router R3

Router R4

Router R5

Layer 3 direct Internet access service.

Layer 2 point-to-point service.

Layer 2 multipoint-to-multipoint service.

Layer 3 IP multipoint-to-multipoint VPN service.

OSPF internal preference and IS-IS Level 1 internal preference.

OSPF internal preference and IS-IS Level 1 external preference.

OSPF external preference and IS-IS Level 1 internal preference.

OSPF external preference and IS-IS Level 2 internal preference.

OSPF external preference and IS-IS Level 1 external preference.

Router LSA

Network LSA

Intra-Area Prefix LSA

Link LSA

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

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

Set the SDP MTU of the IES to match the SDP MTU of the VPLS.

Set the MTU of the IES's network port to match the service MTU of the VPLS.

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.

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.

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.

ADSPEC

CSPF

Service ping

LSP trace

TRUE

FALSE

L1 routers

L2 routers

L1/L2 routers

L1 and L2 routers

DSCP marking

Class of Service Marking

DSAP marking

ICMP type

The system interface is configured with IPv6 address 2001DB8 1:100:1/128

All interfaces are configured for IPv4 and IPv6.

Interface "toR2" is configured with a globally routed IPv6 address.

Interface "toR3" is not configured for IPv6 with a global IPv6 address.

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.

The LSP must be enabled with CSPF on the head-end router.

Fast reroute must be enabled on the downstream routers.

A mixture of strict and loose hops must be defined in the primary path.

CSPF and fast reroute must be enabled on all downstream routers.

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.

configure router tunnel

configure router gre

configure router rsvp-te

configure router transport-tunnel

configure router mpls

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.

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.

LSPs must always terminate on a system ID.

MPLS and RSVP must be enabled on all LSRs.

CSPF must be enabled.

Path definitions must include at least one hop entry.

1

4

6

8

12

24

Not so stubby area

Stub area

Backbone area

Normal area

1

2

3

4

6

7

Show isis neighbors

Show router isis neighbors

Show router isis adjacency

Show isis adjacency

Broadcast

Non-broadcast multi-access

Point-to-point

Point-to-multipoint

It is unidirectional.

It is bidirectional.

It must always have a secondary path.

It provides a specific tunnel for a FEC through the network.

It always follows the IGP best path.

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

The router receives a link-state update in response to a link-state request.

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

The router receives a database description packet from its neighbor.

The router receives a link-state acknowledgement in response to a link-state update

1

2

3

4

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

CSPF chooses a link that is a member of both administrative groups

CSPF chooses only those links that are NOT members of the green admin group

CSPF prunes the green links and uses these links for the secondary path

CSPF signals the LSP path over the green links only, and prunes all other links

Convergence is triggered when the adjacency between routers R1 and R2 drops as a result of hello timeouts.

Convergence is triggered when the physical interfaces between routers R1 and R2 go down.

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 info.

Convergence is triggered when an LSA is sent from router R1 to router R2 to indicate that the link is down.

Router R1 generates a Type 5 LSA that is flooded to area 1 only.

Router R1 generates a Type 5 LSA that is flooded to areas 1 and 0. Router R6 generates a Type 5 LSA that is flooded to area 2.

Router R1 generates a Type 5 LSA that is flooded to areas 0.1, and 2.

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

Type 5 LSAs are not generated in this network topology.

PE, P

LER, LSR

LSR, LER

iLER, eLER

eLER, iLER

P, PE

TRUE

FALSE

The route policy should be applied as an import policy.

The route policy should say "from protocol isis" instead of "from protocol direct".

The ASBR configuration should be removed.

The interface between routers R1 and R3 must be in OSPF area 0.

The penultimate router will POP the top label from the packets.

The eLER will receive packets with a top label value of 3.

The eLER will receive packets with a top label value of 0.

The penultimate router will always receive unlabeled packets.

The penultimate router performs a double lookup on the packet.

0

1

2

3

4

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.

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.

1514

1528

1536

1540

1560

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.

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.

Option A

Option B

Option C

Option D

Router LSA

Network LSA

Summary Network LSA

Summary Router LSA

0

5

10

15

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.

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

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

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.

L1 and L2 routers elect separate DIS's.

DIS uses multicast address 0180x200:0015 to communicate with other routers on the broadcast network.

If a new router starts up in a LAN and has a higher interface priority, the new router preempts the original DIS and becomes the DIS.

In broadcast multi-access networks, such as Ethernet, a single router is elected as the DIS. There is no backup DIS

True

False

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.

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

A packet receives a service label and a transport label at the ingress PE.

A packet has its service label swapped at each P router.

The egress PE pops the service label, and the transport label is forwarded.

The service label is popped by the remote CE.

The service is a local service.

The service requires a second spoke SDP on this router.

The service's VC ID is 44.

The service will accept VLAN tag 100.

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.

An Epipe service that has 1 SAP and 1 SDP configured.

An Epipe service that has 3 or more SAPs configured.

An Epipe service that has 2 SAPs on the same router and has no SDPs configured.

An Epipe service that is configured between two routers, each having 1 SAP and 1 SDP configured

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.

Tunnel Label

VC Label

Operational Control Word

VPI

VCI

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.

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.

"ping 192.168.20.1"

"oam vprn-ping 100 source 192.168.10.1 destination 192.168.20.1"

"oam vprn-ping 100 source 192.168.20.1 destination 192.168.10.1"

"ping 10.10.10.6" (router R6's system IP)

config>service= epipe enable

config>service~ vpws enable

config>service= no shutdown

config>port= no shutdown

config>service= epipe no shutdown

Customer ID

SDP ID

Service ID

VC ID

The SDP to 10.10.10.1 on router R4 is shutdown.

Router R4 has not sent a label to router R1 (10.10.10.1) yet.

10.10.10.1 has a different service MTU set.

10.10.10.1 has not sent a label to router R4 yet.

mac-trace

svc-ping

Isp-trace

traceroute

ping

Isp-ping

traceroute

Isp-trace

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.

0

2

3

6

IP filter

MAC filter

Egress label

Ingress label

Option A

Option B

Option C

Option D

ADSPEC sets an SDP's MTU to the smallest MTU value found along the LSP path.

RSVP must be enabled on all MPLS routers of a path to use ADSPEC.

ADSPEC can automatically adjust the service MTU.

ADSPEC can be enabled on individual LSPs.

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.

A-pipe

E-pipe

I-pipe

F-pipe

C-pipe

The frame egresses from 1/1/1:6 with no VLAN tag.

The frame egresses from 1/1/1:6 with VLAN tag 5.

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

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

A PUSH label stack operation must 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 POP label stack operation may be performed.

When link-state information reaches the maximum age on a router, the router will flood that information to its neighbors.

When a router detects that any of its link-state information has reached the maximum age, it will request a new update from the source router.

Aging helps ensure that links, which are no longer part of the topology, will eventually get removed from the LSDB.

The age value is updated as the information is flooded throughout the network and when it is in the LSDB.

Next Header

Traffic Class

Hop Limit

Fragment Offset

Flow Label

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.

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.

A default route on router R2 to router R1.

A default route on the PC to router R2.

A static route on the PC to router R2 and a static route on router R2 to the PC.

A default route on router R1 to router R2.

OSPFv3 uses MD5 Authentication.

Router LSAs carry IPv6 prefix information.

NSSA is supported in OSPFv3.

OSPFv3 uses a 64-bit router ID.

The area ID does not have to match.

The value of the E bit in the options field does not have to match.

The value of the Hello interval does not have to match.

The value of the network mask does not have to match.

The area ID, the E bit value, the Hello interval and network mask must all match.

10Mbps

20Mbps

30Mpbs

60Mbps

70Mbps

The use of Broadcast messages in combination with Neighbor Advertisement messages.

The use of Anycast addresses in combination with Neighbor Advertisement messages.

The use of Solicited-node multicast addresses in combination with Neighbor Advertisement messages.

The use of Anycast addresses in combination with Link-Local Advertisement messages.

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

When a router performs an SPF computation, it sends the results to its neighbors.

An SPF computation is done by each router to determine the best path to destination prefixes

The link-state database is identical for all routers in a single area routing domain.

Router LSA

Network LSA

Inter-Area Prefix LSA

Link LSA

The IGP FIB.

The Reservation State Block (RSB)

The Path State Block (PSB)

The opaque database.

On a point-to-point link, there is no need for a DR and BDR election; all routing updates are sent to 224.0.0.5.

On a point-to-point link, a DR and BDR are elected. The DR sends link-state advertisements describing the network.

On a point-to-point link, a DR and BDR are elected. To ensure resiliency, both the DR and BDR send link-state advertisements describing the network.

On a point-to-point link, there is no need for a DR and BDR election. All routing updates are sent to the unicast address of the neighbor's interface.

Only router R1 will generate Type 4 LSAs.

Only router R3 will generate Type 4 LSAs.

Routers R3 and R6 will generate Type 4 LSAs.

Routers R1.R3 and R6 will generate Type 4 LSAs.

The IPv6 header has a header checksum field, header length field and no fragmentation offset field.

The IPv6 header has no header checksum field, no header length field and does have a fragmentation offset field.

The IPv6 header has a header checksum field, no header length field and no fragmentation offset field.

The IPv6 header has no header checksum field, no header length field and no fragmentation offset field.

fe80::2416:4dff:fe16:b53d

fe80::2616:4dff:fe16:b53d

ff80::2416:4dff:fe 16:b53d

ff80::2616:4dff:fe 16:b53d

fd80::2416:4dff:fe16:b53d

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.

A mirror source listing port 1/1/4.

A mirror destination listing port 1/1/4.

A remote source command indicating the IP address of the service router he is configuring a local mirror on.

Verification that his IP/MPLS infrastructure is in place

None of the above.

1

3

6

12

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.

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.

LDP

BGP

MP-BGP

MPLS

1586

1596

1600

1614

7958

7978

8022

8042

Sdp-ping

Isp-ping

Svc-ping

Sdp-mtu

Spoke SDPs prevent loops in a VPLS.

Mesh SDPs and spoke SDPs can be used in the same VPLS.

A spoke SDP does not require the routers at both ends to be directly connected.

A mesh SDP is identical to a spoke SDP except for its flooding behavior.

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.

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.

family ipv4 ipv6

family vpn-ipv4ipv6

family vpn-ipv4 vpn-ipv6

family ipv6 vpn-ipv6

0

2

3

6

4078

4986

5014

5022

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.

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.

vc-type ether

vc-type vlan

vc-type dotlq

vc-type null

An outer label and a transport label.

An inner label and a service label.

A transport label and a service label.

An MPLS transport label

Each router requires 1 SDP.

Each router requires 2 SDPs.

Each router requires 3 SDPs.

Each router requires 6 SDPs.

VPRN is an IP service that connects multiple sites in a single routed domain over the provider-managed IP/MPLS network.

Each VPRN consists of a set of customer sites that must connect to the same PE router

In a VPRN service, each customer router becomes a routing peer to other customer routers

VPRN provides customer routers with transparent IP connectivity without knowledge of the MPLS core

sap 1/1/1

sap 1/1/1:*.0

sap 1/1/1:0.*

1/1/1:0

Option A

Option B

Option C

Option D

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping

1

5

10

20

A-pipe

C-pipe

E-pipe

F-pipe

An IES can only have one interface.

An IES interface can have an SDP or a SAP.

An IES can perform fragmentation.

An IES must have an IP address assigned to it.

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.

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.

dot1q

null

qinq

atm

ipcp

bcp-null

Show route-table

Show router routing-table

Show router route-table

Show static

None

1

2

3

4

The system ID

The loopback address

The sequence number of the hello packet

The device that first initiated communication becomes the DIS

Non-broadcast

Broadcast

Point-to-multipoint

Point-to-point

Not So Stubby Area

Stub Area

Backbone Area

Standard Area

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.

RIPv1 and RIPv2

OSPF

IS-IS

BGP

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

Hop count and 16

Hop count and 15

Link cost and 15

Link cost and 16

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.

ff00::1:2

fe80::216:4dff:fe13:5cae

::ffff:0:0.240.0.0.1

2001:db8::30a:216:4dff:fe13:5cae

fd01:2234:5678::1

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.

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.

Option A

Option B

Option C

Option D

The router must receive an acknowledgment

The router must receive a Hello

The router must receive a new sequence number

The router must receive a Link State Packet

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.

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

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

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

Link Local LSA

Router LSA

Network LSA

Inter-Area Router LSA

Intra-Area Prefix LSA

None of the above LSAs have an AS scope.

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

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.

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.

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.

224.0.0.5

224.0.0.6

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

The system address of the router.

Router LSA

AS External LSA

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Network LSA

None of the statements are correct.

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

Area Border Router

Autonomous System Boundary Router

Designated Router

All routers within an OSPF area.

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

Both routers will generate OSPF Hello packets.

The system interface is missing in one configuration so OSPF will not operate correctly.

The interface type settings differ, but OSPF will still operate correctly.

Metric values differ, but this does not prevent OSPF operation.

5 and 15 seconds

10 and 30 seconds

5 and 20 seconds

10 and 40 seconds

Area ID W B.

Hello and Dead intervals PC.

Stub flag

Checksum values

The list of neighbors

IS-IS routers exchange updates by sending UDP packets to a multicast address.

IS-IS routers exchange updates using IP multicast packets.

IS-IS routers exchange updates using Ethernet multicast packets.

IS-IS routers exchange updates by sending packets to the subnet broadcast address.

traceroute 2.3.4.1

traceroute 2.3.4.0/24 next-hop 1.2.3.4

traceroute next-hop 1.2.3.4

traceroute does not work on the Alcatel-Lucent 7750 SR

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

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.

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.

One

Two

Three

Four

show router ospf area

show router ospf neighbor

show router ospf interface

show router ospf status