Free and Premium Nokia 4A0-C04 Dumps Questions Answers

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.

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

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.

The Standby with the highest next-hop IP.

The first Standby in the list.

The Standby with the longest uptime.

The Standby with the lowest next-hop IP.

Three primary paths,

Two primary paths and one backup path.

One primary path and two backup paths.

One primary path and one backup path.

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.

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

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

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

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

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

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

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

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

Link protection tunnels detour around a failed next downstream router.

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

OSPFv3 uses MD5 Authentication.

Router LSAs carry IPv6 prefix information.

NSSA is supported in OSPFv3.

OSPFv3 uses a 64-bit router ID.

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

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

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

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

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.

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 Nokia 7750 SR.

traceroute 10.1.2.1

Add the "originate-default-route" option in the NSSA area configuration on router R3

Add the "summaries" option to the NSSA area configuration on router R1

Make a static route on router R1 to 192.168.3.1

Make a default route on router R2

1

2

3

None

The link state information is not populated in the database but is forwarded to all neighbors

The link state information already in the database is overwritten and the age is reset

The link state information is not populated in the database and an acknowledgement is sent

The link state information is regarded as old and nothing is done.

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.

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.

The peer with the higher physical address.

The peer with the higher transport address.

The peer with the lower physical address.

The peer with the lower transport address.

The peer that generated the first Hello message.

Incoming label

Outgoing label

Incoming interface

Outgoing interface

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

The router 10.10.10.2 is the egress router of the LSP.

The router can reach the far-end of the LSP through an RSVP-TE tunnel.

The router can reach the far-end of the LSP through an LDP tunnel.

The penultimate router will forward packets to the eLER, based on the IP header.

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

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

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

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.

A separate label is used for each interface on which the FEC is advertised.

A single label is assigned to a FEC for all interfaces on the same router,

It is typically used when the device has ATM or Frame Relay interfaces.

It uses more label resources than a per-interface label space.

A new LDP session is established on R1-R3-R6 as soon as the FIB is updated.

The LDP session remains unchanged until the existing path R1-R2-R4-R6 goes down.

A new LDP session is established on R1-R3-R6 as soon as router R1 receives a new label for router R6.

The LDP session remains unchanged until router R3 stops advertising the maximum metric for the link to router R6.

family ipv4 ipv6

family vpn-ipv4ipv6

family vpn-ipv4 vpn-ipv6

family ipv6 vpn-ipv6

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.

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.

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

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

MAC learning reduces flooding of frames with previously learned addresses.

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

Use split horizon by default.

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

Use holddown timers when topologies change to allow for convergence.

Maintain multiple databases: neighbor, topology and routing.

The router must receive several BGP routes to compute a backup path.

BGP FRR can be triggered by BFD.

The backup path can use the same next hop as the primary path.

BGP peer-tracking can be used to improve BGP FRR failure detection times.

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.

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

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

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

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

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.

Router C sends the update to routers E and F only.

Router C sends the update to routers D, E and F.

Router C sends the update to routers A, B, E and F.

Router C sends the update to routers A, B, D, E and F.

1

3

6

12

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

140000 137000

137000 140000

23456 23456

200 140000 137000

The local system has received a Keepalive message and is ready to exchange updates.

The local system is exchanging Update messages with its neighbor.

The local system has sent a Keepalive message to its neighbor and is waiting to receive one back.

The local system has sent an Open message to its neighbor and is waiting to receive one back.

They provide both peering and transit services.

They provide services only to Tier 1 service providers.

They can be either public or private.

They provide services at the local, regional and continental levels.

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 routes are in the RIB-In.

The routes are in the Loc-RIB.

The routes are in the RIB-Out.

The routes are not in any of the BGP databases.

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