Juniper JN0-650 Exam Dumps - Actual Questions Answers

The exhibit shows a BGP routing process where anImport Policyis being applied to routes received in theRIB-IN. Specifically, Policy 1 states:"Reject 0.0.0.0/0 from AS 64512."

In Junos OS, when a routing policy rejects a route, that route is not placed in the main routing table (inet.0) for active use. Instead, it becomes ahidden route. To verify that a specific peer is actually sending a route that is subsequently being rejected by your policy, you must use specific diagnostic commands:

Understanding "Hidden" Routes:When a BGP route is received but fails to meet policy requirements (or has an unreachable next-hop), Junos keeps it in the BGP RIB-IN but marks it as "hidden." It will not appear in a standard show route command.

Command Logic (Option D):The command show route receive-protocol bgp hidden allows an administrator to view all routes received from a specific neighbor, including those that wererejected by import policies.

show route receive-protocol bgp : Shows only the routes that passed the import policy and were accepted into the table. Since the 0.0.0.0/0 route from AS 64512 is explicitly rejected in the exhibit, it would not show up here.

Adding the hidden keyword is the essential step to see the rejected default route and verify that AS 64512 is indeed sending it before the policy drops it.

Other Options:

Option Ais incorrect because it only shows accepted routes.

Option B and Care used to filter the existing active routing table based on gateway or next-hop attributes, but they cannot show routes that have been rejected and excluded from that table.

In a three-stage EVPN-VXLAN fabric (Spine-Leaf architecture) where leaf devices perform the gateway services (Edge-Routed Bridging or ERB):

VTEP Functionality (Option B):Leaf devices act asVXLAN Tunnel End Points (VTEPs). They are responsible for encapsulating Ethernet frames from locally connected hosts into VXLAN packets for transport across the IP fabric and de-encapsulating incoming VXLAN packets.

Fabric Support (Option C):In a standard Juniper IP fabric design, both theleaf and spine devicesare typically expected to support VXLAN and EVPN capabilities. While spines in an ERB design might only perform IP forwarding in the underlay, they often participate in the BGP control plane (as Route Reflectors) or provide the ability to transition to Centrally-Routed Bridging (CRB) where spines would act as gateways.

Incorrect Options:Option Ais incorrect because the entire fabric infrastructure must be "VXLAN aware" in terms of MTU settings and routing capability to support the overlay.Option Dis incorrect because in an ERB design, the spine devices are high-speed transit nodes and do not terminate VXLAN tunnels; only the edge (leaf) devices act as VTEPs.

In standard BGP operations, a router typically selects only one "best path" for a given destination prefix and installs that single path into the forwarding table. To utilize multiple paths for traffic forwarding (load-balancing), specific multipath features must be enabled.

BGP Multipath:This feature allows a router to install multiple equal-cost paths into the routing and forwarding tables. However, by default, BGP multipath requires that all candidate paths have the same neighboring Autonomous System (AS).

Multipath Multiple-AS (Option B):In the exhibit, R1 is receiving routes fromISP A (AS 65501)andISP B (AS 65502). Since these are two different neighboring ASs, the standard multipath feature is not sufficient. You must use the multipath multiple-as statement under the BGP group or neighbor hierarchy. This tells Junos to consider paths as equal even if they originate from different neighboring ASs, provided all other BGP path selection attributes (Local Preference, AS Path length, Origin, MED, etc.) are identical.

Why other options are incorrect:*Option A (multihop)is used for peering with routers that are not directly connected.

Option C (prefix limit)is a security and stability feature to limit the number of prefixes received from a neighbor.

Option D (damping)is used to penalize unstable, "flapping" routes to prevent constant routing table churn.

Configuration Example for Junos OS 24.4:To implement this on R1, you would use the following configuration:

set protocols bgp group multipath multiple-as