The Implementing Cisco Enterprise Network Core Technologies (350-401 ENCOR) (350-401)

The correct answer is B. to connect wired endpoints to the SD-Access fabric.

In Cisco SD-Access, the fabric edge node is the device that provides access for endpoints into the fabric. It is the point where user devices such as PCs, phones, printers, and access points attach to the SD-Access network. The edge node handles endpoint onboarding into the fabric and applies the appropriate segmentation and policy.

A fabric edge node is specifically responsible for:

Connecting wired endpoints to the fabric

Serving as the access-layer entry point into the SD-Access fabric

Enforcing policy and segmentation for connected endpoints

Extending the fabric to end hosts

This is the main role of the edge node in the SD-Access architecture.

A. to connect the fusion router to the SD-Access fabric This is not the role of the fabric edge node. The fusion router is used outside the fabric to provide connectivity between the fabric and external networks.

C. to advertise fabric IP address space to external networks This function is associated with the border node, not the edge node. The border node connects the fabric to external domains and exchanges reachability information.

D. to connect external Layer 3 networks to the SD-Access fabric This is also the function of the border node, not the edge node.

Remember these SD-Access node roles clearly:

Edge node = connects endpoints

Border node = connects to external networks

Control-plane node = maintains endpoint-to-location mappings

Fusion router = external routing/services outside the fabric

Edge node = endpoint access into the fabric

The input service policy shown in the exhibit matches traffic with DSCP value 1 and applies a QoS set action to rewrite that marking to DSCP 63. Therefore, packets entering interface Fa7/0/2 with DSCP 1 are remarked to DSCP 63, making option B correct. The second part of the configuration defines a class map matching DSCP 63 and a policy map using bandwidth percent 50. That behavior belongs to class-based queuing/scheduling, where DSCP63-marked traffic is placed into a class that receives a bandwidth allocation. In the given option set, option C best represents this queuing behavior. Option D is wrong because the service policy explicitly changes the DSCP value. Option E is not accurate because classification is not triggered by reaching 50 percent bandwidth; classification occurs by matching packet fields such as DSCP. Option A is less precise than C because the shown policy behavior is class-based queuing with a bandwidth allocation. The important ENCOR concept is the separation between marking on ingress and queuing/scheduling on egress. References/topics: ENCOR Infrastructure, QoS, MQC, class maps, policy maps, DSCP marking, CBWFQ, bandwidth percent.

The correct answer is D.

OSPF and EIGRP use different multicast addresses for exchanging routing information:

OSPF uses:

224.0.0.5 → AllSPFRouters

224.0.0.6 → AllDRouters

EIGRP uses:

224.0.0.10

This is a well-known operational difference between the two protocols and is commonly tested in Cisco ENCOR.

A. OSPF uses IP protocol number 88. EIGRP uses IP protocol number 89. This is reversed.

EIGRP = IP protocol 88

OSPF = IP protocol 89

B. OSPF uses a default hello timer of 5 seconds. EIGRP uses a default hello timer of 10 seconds. This is incorrect.

On most broadcast and point-to-point networks, OSPF default hello = 10 seconds

EIGRP default hello = 5 seconds on high-speed links

C. OSPF uses an administrative distance of 115. EIGRP uses an administrative distance of 160. This is also incorrect.

OSPF AD = 110

EIGRP internal AD = 90

EIGRP external AD = 170

Memorize these protocol identifiers:

OSPF

Protocol number: 89

Multicast: 224.0.0.5 / 224.0.0.6

EIGRP

Protocol number: 88

Multicast: 224.0.0.10

In Locator/ID Separation Protocol, the ingress tunnel router is responsible for encapsulating traffic from an endpoint identifier toward the correct routing locator. When the ITR does not already have an EID-to-RLOC mapping in its local map cache, it must request that mapping through the LISP control plane. The component that receives map requests from ITRs is the Map Resolver. Therefore, option A is correct. A routing locator is not a query target; it is the routable address representing the location of an EID in the underlay or routing infrastructure. A proxy ingress tunnel router is used to connect non-LISP sites toward LISP sites by acting on behalf of non-LISP sources. A proxy egress tunnel router provides reachability in the reverse direction, helping LISP sites communicate with non-LISP destinations. Neither PITR nor PETR is the normal answer to an ITR mapping-resolution request. The core ENCOR point is the separation between endpoint identity and routing location, with map resolution handled by the LISP control plane. References/topics: ENCOR Architecture, LISP, ITR, Map Resolver, EID-to-RLOC mapping, SD-Access control plane concepts.

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