350-401 Cisco Implementing Cisco Enterprise Network Core Technologies (350-401 ENCOR) Free Practice Exam Questions (2026 Updated)

The correct answer is A. It encapsulates IP packets from non-LISP sites with a LISP header.

In Cisco LISP, a PITR (Proxy Ingress Tunnel Router) provides connectivity between non-LISP sites and LISP sites. Cisco documentation states that a PITR performs ITR mapping database lookups and LISP encapsulation functions on behalf of non-LISP-capable sites. Cisco also explains that the PITR attracts traffic from non-LISP sites that is destined for LISP EID space, then encapsulates and forwards that traffic to LISP sites.

That is exactly what option A describes.

A PITR acts like an ingress tunnel router for non-LISP sources. When traffic comes from a non-LISP site toward a LISP destination, the PITR:

receives the traffic,

performs the mapping lookup,

adds the LISP header,

and forwards the encapsulated packet toward the correct LISP site.

B. It accepts registration requests and aggregates successfully registered EID prefixes to client ITRs. This describes the role of a Map Server (MS), not a PITR. Cisco states that the MS receives registrations from ETRs and advertises aggregates for registered EID prefixes into the mapping system.

C. It is responsible for publishing the site EID-to-RLOC mappings. This is also associated with the Map Server / mapping system, not the PITR. The PITR uses mappings for encapsulation; it does not publish them.

D. It forwards encapsulated messages to the MS to the authoritative ITR for the EID. This is incorrect terminology and mismatched function. Cisco explains that a Map Resolver (MR) accepts encapsulated Map-Request messages from ITRs and forwards them toward the appropriate Map Server or authoritative ETR, not an authoritative ITR.

ENCOR exam point:

Remember these LISP roles clearly:

ITR = encapsulates traffic toward LISP sites

ETR = decapsulates traffic arriving at LISP sites

PITR = performs ITR function for non-LISP to LISP traffic

MS/MR = mapping-system control-plane components

The correct answer is D. The WLC configuration maps user data ToS level priorities to IP precedence levels.

The exhibit shows the QoS Map feature enabled on the WLC and, under Up Stream, the option UP to DSCP Map is selected.

This means the controller is taking 802.1p User Priority (UP) values and mapping them to DSCP values for upstream traffic. Since 802.1p is a Layer 2 priority marking and DSCP/IP precedence are Layer 3 QoS markings in the IP header, the WLC is performing a priority-marking translation from user priority into IP QoS markings.

In ENCOR terms:

802.1p UP = Layer 2 Class of Service marking

DSCP / IP precedence = Layer 3 QoS marking

The WLC is configured to map UP values to DSCP values

A. The WLC configuration prioritizes traffic based on access group assignment. This is unrelated to the exhibit. QoS mapping here is based on 802.1p UP values, not access group assignment.

B. The WLC uses the Platinum, Gold, Silver, and Bronze levels for traffic classification based on priority. Those are older WLAN QoS profile names, but the exhibit is specifically showing UP-to-DSCP mapping, not profile-based classification.

C. The WLC configuration inherits DSCP values from an upstream AP. This would align with Trust DSCP Upstream, but that option is not selected in the exhibit.

For wireless QoS questions, remember these mappings:

802.1p / CoS / UP = Layer 2 priority

DSCP / IP precedence = Layer 3 priority

If UP to DSCP Map is selected, the controller is converting Layer 2 priority markings into Layer 3 QoS markings.

The correct answer is A. Interface FastEthernet0/0 is configured in VRF CUST-A, so the ARP entry is also in that VRF.

In Cisco VRF implementations, ARP entries are maintained separately per VRF, not in the global routing table. Cisco documentation states that with Multi-VRF CE, ARP entries are learned in separate VRFs, and the user can display them for a specific VRF. Cisco also documents the command show ip arp vrf <</b> vrf-name > to display the ARP table for a specified VRF.

That means if the interface belongs to VRF CUST-A, a normal global show ip arp 192.168.12.2 may not display the entry, even though ping vrf CUST-A 192.168.12.2 succeeds. The ARP entry exists, but it is stored under the CUST-A VRF ARP table, not the global ARP table.

B. When VRFs are used, ARP protocol is disabled in the global routing table. This is incorrect. ARP is not disabled; it is simply VRF-aware and tracked separately per VRF.

C. When VRFs are used, ARP protocol must be enabled in each VRF. This is incorrect. There is no separate requirement to manually enable ARP in each VRF for normal operation in this context.

D. The ping command must be executed in the global routing table. This is incorrect because Cisco supports pinging within a specific VRF, and the exhibit already shows the use of ping vrf CUST-A .

ENCOR exam point:

With VRF-aware services, always remember:

Routing table = per VRF

ARP table = per VRF

Verification commands often require the VRF keyword