4A0-C01 Exam Dumps - Nokia NRS II Composite Exam

LSPs must always terminate on a system ID.

MPLS and RSVP must be enabled on all routers.

Interfaces must be individually created in RSVP.

Path definitions must include at least one hop entry.

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

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

Add a default static route on router R3.

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

Add a static route on router R3 to 192.168.3.1.

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.

The ARP functionality has been replaced by the Neighbor Discovery protocol.

The ARP functionality is not needed due to the increased IPv6 address space.

ICMPv6 reduced its role to connectivity checking and auto-configuration only.

ICMFV6 replaced the ARP functionality with Multicast Listener Discovery (MLD).

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.

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.

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.

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping