JN0-650 Enterprise Routing and Switching - Professional (JNCIP-ENT) Questions and Answers

In an EVPN-VXLAN environment using ESI-LAG (Ethernet Segment Identifier Link Aggregation) , the Core Isolation feature is a safety mechanism designed to prevent traffic blackholing. When a leaf switch (acting as a VTEP) loses its BGP peering or its link to the IP fabric core, it assumes it is " isolated " from the rest of the network. To protect the network, the switch automatically shuts down its local member links of any multi-homed ESI-LAG to force traffic to the peer switch that still has core connectivity.

However, during a migration or in specific transitional topologies where the core might be temporarily unreachable or not yet fully established, this feature can cause the leaf switches to shut down all downstream IDF (Intermediate Distribution Frame) connections, leading to a total loss of connectivity.

The Solution (Option C): By enabling the no-core-isolation statement under the [edit protocols evpn] hierarchy, you instruct the switch to disable this automatic shutdown behavior . This ensures that even if the BGP session or core links are not yet stable during the migration process, the ESI-LAG interfaces remain Up , allowing the IDFs to maintain connectivity to their local default gateways or other local resources.

Why others are incorrect: Enabling EVPN-VXLAN before migration (Option A) does not address the isolation logic. Removing MC-LAG/Virtual Chassis links prematurely (Option B) would cause an immediate outage. The network-isolation-profile (Option D) is typically used for different loop prevention scenarios and does not override the specific core-isolation check that affects multi-homed ESIs.

In Junos OS 24.4, Captive Portal is used as a web-based authentication method for Layer 2 network access control, often in environments where 802.1X is not feasible for all users.

Fallback Mechanism (Option D): On EX Series switches, Juniper supports a flexible authentication order. By default, the switch attempts authentication in the order of 802.1X, then MAC RADIUS, and finally Captive Portal. If a client fails both 802.1X and MAC RADIUS, the switch can fall back to Captive Portal to redirect the user to a login page.

MAC Allowlist (Option B): Captive Portal relies on intercepting HTTP/HTTPS traffic to redirect users. However, " headless " devices like printers or cameras lack web browsers and cannot interact with the portal. To accommodate these, Junos allows administrators to configure an authentication allowlist (or whitelist), which identifies these devices by their MAC addresses and permits them to bypass the portal entirely.

Precedence (Option A): This is incorrect because Captive Portal is generally the last method in the default sequence, not the first.

Layer 2 Participation (Option C): While Captive Portal requires a Layer 3 interface (RVI/IRB) for the redirection process, it is explicitly used to control Layer 2 access on EX Series switches.

The exhibit shows an OSPF network where Area 1 is configured as a Not-So-Stubby Area (NSSA). R5 is an Autonomous System Boundary Router (ASBR) injecting an External Route (203.0.113.0/24) into this area.

NSSA ASBR Behavior (Option D): Within an OSPF NSSA, external routes cannot be advertised as standard Type 5 LSAs because stubby areas do not support them. Instead, the ASBR (R5) advertises the external prefix using a Type 7 LSA (NSSA External LSA). This LSA is flooded throughout Area 1.

ABR Translation Behavior (Option C): When the Type 7 LSA reaches the Area Border Router (R1), the ABR is responsible for translating it into a Type 5 LSA (AS External LSA). This allows the external route to be propagated into the backbone (Area 0) and subsequently to the rest of the OSPF domain.

Incorrect Statements (A & B): Option A is incorrect because Type 7 LSAs are local to the NSSA and are never advertised into Area 0. Option B is incorrect because Type 5 LSAs are strictly prohibited within an NSSA.

In Junos OS routing policies, the order of evaluation and the impact of terminal actions are critical for predictable control.

Immediate Execution (Option D): When a route-filter contains an explicit action like accept or reject within its block, that action is considered terminal if a match is found.

Evaluation Flow: The policy engine processes terms and conditions from top to bottom. If a prefix matches a route-filter that has an embedded accept action, the policy executes that action immediately and stops further evaluation of that specific term. Consequently, any subsequent then clause in the same term is completely ignored.

Best Practice: To ensure a then clause (which might include modifications like changing a preference or community) is executed, the route-filter should be defined without an internal action, allowing the match to fall through to the term ' s common then statement.

When 802.1X server fail fallback is enabled with the vlan-name feature, the switch provides a specific survival mechanism for both existing and new sessions when the RADIUS server becomes unreachable.

Existing Clients (Statement B): Clients that have already successfully authenticated are unaffected by the server ' s unavailability in the short term. They maintain their current network access until their specific re-authentication timer expires. Only then will the switch attempt to contact the server again and trigger the fallback action if the server remains down.

New Clients (Statement D): For any new device attempting to connect while the RADIUS server is down, the switch cannot perform a standard authentication. Under the vlan-name fallback configuration, these new clients are automatically placed into the specified fallback VLAN and granted access based on the local policy defined for that VLAN.

Why others are incorrect: Statement A is incorrect because disconnecting active users would cause unnecessary service disruption. Statement C is incorrect because new clients cannot " request " a VLAN during the 802.1X handshake; the switch assigns it based on the fallback configuration.

The exhibit displays the default-switch.evpn.0 routing table, which is used on Juniper leaf devices to store EVPN Type 2 (MAC/IP) routes.

Route Distinguisher (Option C): In EVPN, the Route Distinguisher (RD) is an 8-byte prefix added to a route to make it unique within the BGP control plane. The RD format in the exhibit is < IP-Address > : < Identifier > .

For example, the prefix 2:192.168.100.1:1::5010::... indicates an EVPN Type 2 route (2:) where 192.168.100.1:1 is the Route Distinguisher.

This RD identifies the specific routing instance on the originating VTEP that advertised the MAC/IP address.

Option A is incorrect: The RD 192.168.100.2:1 does not necessarily mean the host device has that IP; it means the originating switch has that router ID/IP used for its RD.

Option B is incorrect: While the RD often incorporates the router ID, the RD itself is the full string (e.g., 192.168.100.1:1), which is distinct from the raw Router ID used in the BGP summary.

Option D is incorrect: Looking at the entries for 10.1.1.1 and 10.1.2.3, they are associated with different identifiers in the RD strings (5010 and 5020 respectively), which typically map to different VNIs or bridge domains.

In Junos OS, the supplicant-mode configuration under protocols dot1x determines how the switch handles multiple MAC addresses on a single physical port. According to the exhibit, the current mode is set to Single, and the Number of connected supplicants is 2. This indicates that the port is currently allowing multiple devices, which contradicts the goal of limiting access to only one device at a time.

Here is the breakdown of why Option C is the correct solution based on Juniper’s standard behavior:

Supplicant Mode: Single (Current State): In this mode, the first device to authenticate opens the port for all subsequent devices. As long as the first device remains authenticated, other devices can send traffic through the port without individual authentication. This is why the exhibit shows 2 connected supplicants despite the mode being " Single. "

Supplicant Mode: Single-Secure (The Solution): This mode strictly limits the port to only one MAC address. Once a device successfully authenticates via 802.1X, the switch drops any traffic coming from any other MAC address on that port. If the authenticated device logs off or the session times out, the port becomes available for a new device, but never more than one simultaneously. * Supplicant Mode: Multiple (Option B): This mode allows multiple supplicants to authenticate individually. Each MAC address must go through its own authentication process. This would allow more than one device, which is the opposite of the user ' s requirement.

MAC RADIUS Restrict (Option A): This feature is used to force MAC-based authentication and does not inherently limit the number of devices to one in the same way that changing the supplicant mode does.

Maximum EAPOL requests (Option D): This parameter defines how many times the switch will send an EAP-Request/Identity frame to a supplicant before giving up. Changing this to 1 does not restrict the number of devices allowed on the port; it only changes the retry logic for a single authentication attempt.

Configuration Example for Junos OS 24.4: To implement this change, you would use the following command: set protocols dot1x edit interface ge-0/0/10.0 supplicant-mode single-secure

To provide IP phones with geographic location details (such as civic addresses or coordinates) automatically, Juniper EX Series switches utilize the LLDP-MED (Link Layer Discovery Protocol - Media Endpoint Discovery) protocol.

VoIP Specifics: While standard LLDP (C) is for general device discovery, LLDP-MED is an enhancement specifically designed for network-to-endpoint communication for VoIP devices.

Location Identification: LLDP-MED supports Location Identification TLVs (Type-Length-Values). These allow a switch to push geographic or civic location data to an IP phone, which is critical for E911 services and asset tracking.

Junos Implementation: On EX Series switches, this is typically configured under protocols lldp-med to ensure the switch advertises the necessary location information to connected endpoints.

Private VLANs (PVLANs) allow for granular port isolation within a single broadcast domain. When extending a PVLAN across multiple switches (S1 to S2), the secondary VLANs (Community or Isolated) must be preserved across the trunk links.

802.1Q Tagging (Option B): For traffic from a Community VLAN (RND) to reach members on a different switch, the Community VLAN must have its own 802.1Q VLAN tag (VLAN ID) associated with it. When a frame from a community port on S1 traverses the trunk to S2, it is tagged with this specific secondary VLAN ID. S2 receives the tagged frame, identifies it as belonging to the RND community, and forwards it to the appropriate community or promiscuous ports.

Why it fails without a tag: If the RND community is only defined locally on S1 without a global VLAN ID, the trunk port will not know how to distinguish that traffic from the Primary VLAN or other communities.

Incorrect Options: Option A is incorrect because the community VLAN must have a different tag than the parent (Primary) VLAN to maintain the internal PVLAN logic. Option C is incorrect because stripping tags would lead to the traffic being merged into the native VLAN or dropped. Option D is incorrect because RND is a community VLAN; changing it to an isolated VLAN would change its behavior (preventing communication between members of that same group).

OSPFv2 (IPv4) and OSPFv3 (IPv6) share many fundamental concepts, such as the SPF algorithm and the use of areas, but they have distinct differences in how they handle prefix information and LSA headers in Junos OS.

Backbone Requirement (Option C): Both OSPFv2 and OSPFv3 utilize a hierarchical structure. In both versions, all areas must connect to a central Area 0 (the backbone) to allow for inter-area routing. If an area is not physically connected to Area 0, a virtual link must be established.

Flooding Scope (Option D): One of the significant architectural changes in OSPFv3 is the inclusion of the flooding scope directly into the LSA header. In OSPFv3, the LS Type field is expanded to 16 bits, where the top three bits define the flooding scope (e.g., Link-local, Area, or AS scope). This allows routers to understand how far an LSA should be propagated without needing to understand the specific LSA type itself.

LSA Prefix Information (Option A): This statement is misleading. In OSPFv2, Router and Network LSAs (Type 1 and 2) carry both topology and prefix information. However, a key design goal of OSPFv3 was to separate topology from prefix information. In OSPFv3, Type 1 and 2 LSAs only describe the topology, while prefixes are carried in new LSA types: Intra-Area-Prefix-LSAs (Type 9) and Link-LSAs (Type 8).

Processing (Option B): OSPFv2 is processed " per-subnet " because it forms adjacencies based on IPv4 subnets. OSPFv3 is processed " per-link " , meaning it forms adjacencies between interfaces on the same physical link regardless of whether they share a common IPv6 prefix.

In BGP path selection, the Local Preference attribute is one of the most common ways to influence outbound traffic from an Autonomous System (AS). It is a well-known discretionary attribute that is propagated throughout the AS to tell internal routers which path is preferred for a specific destination.

Priority Rule: In the BGP selection algorithm, a higher local preference value is always preferred over a lower one. The default value in Junos OS is 100.

Influencing Outbound Traffic (Option A): To ensure that Provider A is always preferred, you would apply an import policy on R1 (the router connected to Provider A) to set the local preference of all received routes to a value higher than the default (e.g., 200). Since 200 > 100, R3 and R4 will prefer the path via R1.

Alternative Method (Option C): Conversely, you can achieve the same result by applying an import policy on R2 (the router connected to Provider B) to set the local preference to a value lower than the default (e.g., 50). Since the routes from R1 remain at the default of 100, and 100 > 50, the path via R1 (Provider A) is preferred.

Why B and D are incorrect: Setting a higher local preference on R2 (Option B) would make Provider B the preferred exit point. Setting a lower local preference on R1 (Option D) would make Provider A the least preferred exit point.

The IETF standards for EVPN-VXLAN define the scalability and forwarding behavior of the architecture.

VXLAN Scale (Statement B): The Virtual Network Identifier (VNI) is a 24-bit field in the VXLAN header. This allows for up to $2^{24}$ unique identifiers, which translates to approximately 16 million distinct VXLAN broadcast domains (segments) within a single fabric. * Forwarding Behavior (Statement D): VXLAN is a MAC-in-UDP encapsulation technology. When a Layer 2 frame enters the tunnel at a VTEP, the original Layer 2 frame (including the original source and destination MAC addresses) is encapsulated into a UDP/IP packet and transported across the IP underlay. When it reaches the egress VTEP, the header is removed and the Layer 2 frame is forwarded unchanged to the destination host.

Why others are incorrect: Statement A is incorrect because EVPN itself can technically support more than 16 million domains, but the data plane (VXLAN) is the limiting factor in this specific deployment scenario. Statement C is incorrect because VXLAN encapsulates Layer 2 frames, not just " IP packets, " and it treats the entire frame as a payload.

The exhibit illustrates an EVPN-VXLAN fabric using multi-homing. Server1 is dual-homed to Leaf1 and Leaf2 using an Ethernet Segment Identifier (ESI) in an active-active or active-standby configuration. Server2 is single-homed to Leaf3.

In EVPN environments, specific mechanisms are used to prevent loops and duplicate traffic when dealing with Broadcast, Unknown Unicast, and Multicast (BUM) traffic:

Broadcast Propagation (Option A): When Server2 (connected to Leaf3) generates a broadcast frame, Leaf3 encapsulates this traffic into a VXLAN tunnel and forwards it to all other VTEPs (Virtual Tunnel End Points) that participate in that specific Virtual Network Instance (VNI). Therefore, both Leaf1 and Leaf2 will receive the broadcast frame from the core fabric.

Designated Forwarder (DF) Election (Option C): To prevent a multi-homed device (like Server1) from receiving duplicate copies of the same broadcast frame from multiple leaf switches, EVPN utilizes a Designated Forwarder (DF). For a given ESI, only one leaf switch is elected as the DF.

The exhibit explicitly states that Leaf2 is the Designated Forwarder.

According to the Junos EVPN implementation, only the DF is responsible for decapsulating BUM traffic received from the core and forwarding it to the local access segment.

While Leaf1 receives the frame (Option A), it will see that it is not the DF for that segment and will drop the frame rather than forwarding it to Server1. This ensures Server1 receives exactly one copy of the broadcast, delivered by Leaf2.

Option B is incorrect because in a standard ingress replication or multicast-based underlay, all VTEPs in the VNI receive the broadcast.

Option D is incorrect because Leaf1 is the non-designated forwarder (non-DF) for this segment and is prohibited from forwarding BUM traffic to the ESI.

For maintenance scenarios where a router must remain operational but should not be used as a transit path for OSPF traffic, Junos OS uses the overload functionality.

OSPF Overload (Option B): When you enable overload under protocols ospf, the router advertises its own Link-State Advertisements (LSAs) with a maximum metric (65535) for all of its transit links.

Traffic Diversion: Because OSPF uses the Shortest Path First (SPF) algorithm to find the lowest-cost path, other routers in the network will see the overloaded router as an extremely high-cost path. They will calculate alternate routes, effectively moving transit traffic off the router while still allowing management traffic directed to the router ' s own interfaces.

Timeout Options: You can configure this to be permanent or set a timeout so that the router automatically resumes normal metric advertisements after a set period.

When integrating a QFX Series switch into an EVPN-VXLAN IP fabric, specific BGP and EVPN hierarchy configurations are required to establish the control and data planes:

EVPN Encapsulation (Option A): In Junos OS, the encapsulation vxlan statement must be explicitly configured under the protocols evpn hierarchy. This defines that the EVPN control plane will use VXLAN as the data plane encapsulation method rather than MPLS.

BGP Address Family (Option C): EVPN uses Multiprotocol BGP (MP-BGP) to distribute reachability information. For the control plane to function, you must enable the EVPN signaling address family under the BGP protocol using the command set protocols bgp group < name > family evpn signaling.

Incorrect Options: Option B is incorrect because family vpls is used for traditional VPLS signaled by BGP, not for EVPN-VXLAN. Option D is incorrect because while the loopback interface must be reachable, it is typically advertised via an IGP (like OSPF or IS-IS) to provide the underlay connectivity that BGP then rides upon; BGP itself does not " advertise " the loopback to establish the initial peerings.

OSPF determines the best path to a destination by calculating the metric (cost) of each link. By default, Junos OS uses a reference bandwidth of 100 Mbps to calculate this cost using the formula:

When the reference bandwidth is left at the default 100 Mbps, any interface with a speed of 100 Mbps or higher (including 1 GbE and 10 GbE) is assigned a cost of 1 because the minimum OSPF cost is 1. This results in equal-cost paths, preventing the router from preferring the faster 10 GbE link.

To ensure 10 GbE interfaces are preferred, you must create a cost differential:

Option A (Reference Bandwidth): By increasing the reference bandwidth to 10G (or higher), the calculation changes. For a 10 GbE link, the cost becomes $10,000 / 10,000 = 1$. For a 1 GbE link, the cost becomes $10,000 / 1,000 = 10$. Since OSPF prefers the path with the lowest cumulative cost, the 10 GbE link is now preferred.

Option D (Manual Metric): You can manually override the automatic cost calculation by assigning a higher metric specifically to the 1 GbE interfaces. If a 1 GbE interface is manually set to a cost of 50 and the 10 GbE interface remains at 1 (or is set to a lower value), the router will prioritize the 10 GbE path.

Option B is incorrect because a higher metric makes a path less preferred. Option C is incorrect because a 1G reference bandwidth would still result in both 1 GbE and 10 GbE interfaces having a cost of 1.

In Junos OS 24.4, the no-loss forwarding class is used for traffic that requires lossless delivery, such as iSCSI or FCoE, typically in a Data Center Bridging (DCB) environment.

Priority-Based Flow Control (Option C): To guarantee " no-loss " behavior, the switch must support and use Priority-based Flow Control (PFC). PFC allows the switch to send " pause " frames for a specific priority (forwarding class) to prevent buffer overflow and packet drops without affecting other traffic on the same link.

Forwarding Class Sets (Option B): In enhanced Layer 2 software (ELS) versions used by modern QFX and EX series switches, lossless traffic must be managed within forwarding class sets (also known as priority groups). This grouping is necessary to apply specific DCB properties, such as PFC and specific bandwidth guarantees, to the lossless traffic class.

Why A and D are incorrect: Default scheduler maps and default drop profiles do not provide the specialized buffer management or lossless signaling required for this class. Lossless traffic specifically requires the suppression of tail drops rather than standard drop profiles.

This question focuses on port security and preventing " rogue switches " or multiple devices from accessing a single physical port simultaneously.

Single-Secure Supplicant Mode (Option A): This is the most restrictive 802.1X mode in Junos OS. It allows exactly one MAC address to be authenticated on the port at a time. If a device successfully authenticates, the switch will drop any traffic coming from any other MAC address on that same physical interface. If a user tries to plug in a switch, only the first device that authenticates will have access; all other devices behind that switch will be blocked.

Single Supplicant Mode (Option C): This mode allows the first authenticated user to " open " the port for all other users. This would actually allow a rogue switch to function once the first device is authorized.

Multiple Supplicant Mode (Option B): This allows multiple devices to connect, provided each one authenticates individually. While secure, it does not prevent a user from connecting multiple devices to the port, which violates the requirement to allow only one.

MAC-RADIUS (Option D): This is an authentication method, not a port-access mode that limits the number of supplicants.