Nokia Nokia Ethernet Virtual Private Network Services 4A0-115 Exam Dumps: Updated Questions & Answers (October 2025)

1

2

3

4

The local AC tag ID configured on PE2 must match the local AC tag ID configured on PEI.

The remote AC tag ID configured on PE2 must match the remote AC tag ID configured on PE3.

The local AC tag ID and the remote AC tag ID configured on PE2 must match.

The local AC tag ID configured on PEI must match the local AC tag ID configured on PE3.

VPLS 10 must be configured with two BGP instances on PE3 and PE4.

On PE3 and PE4, VPLS 10 must be configured with two different route-distinguisher values: one for VXLAN and another for MPLS.

On PE3 and PE4, VPLS 10 must be configured with two different route-target values: one for VXLAN and another for MPLS.

A BGP export policy is required on PE3 and PE4 to ensure that IMET routes originated with VXLAN encapsulation are not advertised to the peer across the core network.

The updates include an Ethernet segment identifier label that is used in loop prevention.

The updates advertise the Ethernet segment availability in a given EVPN service.

The updates include an MPLS label that is set to a non-zero value.

The updates include an Ethernet tag ID that is set to zero.

PEI advertises an auto-discovery per EVPN instance (A-D per EVI) route to PE3 as soon as the SAP becomes operationally

PE3 advertises an IMET route to PEI as soon as VPWS 4 is administratively enabled.

PEI and PE3 exchange their service labels using A-D per EVI routes.

PE3 and PE4 exchange their service labels over an established targeted LDP session.

The PE has proxy-ARP and dynamic-populate enabled for the VPLS.

The proxy-ARP table is populated by snooping IP packets received from remote PEs.

When the PE learns a local host IP address, it adds an entry into its proxy-ARP table.

The PE advertises a MAC/IP route that includes the MAC and IP address of a local host.

All VPLS instances must be configured on all PES regardless of whether they have a local host or not.

EVPN IP-Prefix routes are used to populate the VPRN VRF tables.

The egress PE does not perform any Layer-3 route look up to forward traffic.

The ingress PE performs both Layer-2 and Layer-3 look ups when forwarding traffic between subnets.

Allows Tx unicast, blocks Rx unicast, allows Tx BUM, blocks Rx BUM

PEI advertises an A-D per EVI route that includes a tag ID set to 40.

PEI advertises an A-D per EVI route that includes a non-zero Layer-2 MTLJ.

PE2 advertises an A-D per EVI route that includes a P flag set to I.

All PES advertise a MAC route that includes a non-zero MPLS label.

A supplementary broadcast domain (SBD) is configured as a routed VPLS.

A VPRN service is configured and has an interface bound to the local VPLS.

The advertisement of IP-Prefix routes is enabled in the SBD VPLS.

An IP address is configured in the VPRN interface that is bound to the SBD VPLS.