100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 480
A network change is required for the following specific situation: A new IPv6 peering uses OSPFv3 on a retired VLAN unit rather than the active routed transit interface. Which corrective action is most appropriate?
- Inspect the active local default and export term conditions; match only the authorized static default source.
- Compare OSPF interface timers and align the two peers to approved Hello and dead values.
- Move OSPFv3 participation to the correct active interface and verify neighbor and IPv6 RIB state.
- Compare configured interface areas with the approved topology and put both interfaces in the intended matching area.
Explanation
Correct Answer
C:OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication. Verify this by checking that an OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0.
Incorrect Answers
A:“Inspect the active local default and export term conditions; match only the authorized static default source” belongs to a separate Interior Gateway Protocols (IGPs) issue: a branch default-route injection stops after a policy matches OSPF-learned routes instead of the intended local static. It does not explain the condition tested here.
B:“Compare OSPF interface timers and align the two peers to approved Hello and dead values” belongs to a separate Interior Gateway Protocols (IGPs) issue: an access-area adjacency drops after one device is changed to shorter OSPF Hello timers but its peer keeps prior settings. It does not explain the condition tested here.
D:“Compare configured interface areas with the approved topology and put both interfaces in the intended matching area” belongs to a separate Interior Gateway Protocols (IGPs) issue: a campus OSPF interface is accidentally placed in area 0 while its neighbor advertises a nonbackbone area, preventing a Full adjacency. It does not explain the condition tested here.
Question 481
Select THREE complementary corrective, verification, or preventive controls for this scenario: A VXLAN overlay's BGP EVPN routes are present, but the underlay cannot route to a remote VTEP loopback.
- Treat a single learned MAC/IP Type 2 route as guaranteed proof of correct BUM participation for every VTEP.
- Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address.
- Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies.
- Increase a tenant VLAN identifier and expect it to fix an unreachable underlay VTEP IP.
- Include underlay loopback reachability and MTU checks in VXLAN overlay deployment QA.
- The remote VTEP becomes reachable and encapsulated packets cross the fabric as intended.
Explanation
Correct Answers
C:Correction: VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state.
E:Prevention of recurrence: VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state.
F:Confirmation: Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies.
Incorrect Answers
A:“Treat a single learned MAC/IP Type 2 route as guaranteed proof of correct BUM participation for every VTEP” is an unsafe response to a different problem: a bridge domain has valid unicast Type 2 entries yet remote VTEPs do not discover a new participating segment for BUM forwarding. It is not a valid fix here.
B:“Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address” is an unsafe response to a different problem: a fabric advertises Type 3 routes and claims this proves specific remote host MACs are reachable. It is not a valid fix here.
D:“Increase a tenant VLAN identifier and expect it to fix an unreachable underlay VTEP IP” does not address VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state.
Question 482
A Junos enterprise team investigates this incident: A VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side. Which technical explanation most directly identifies the cause or design principle?
- VXLAN adds encapsulation overhead, so underlay MTU must accommodate the intended overlay frame size.
- EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops.
- EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set.
- VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
Explanation
Correct Answer
C:EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set. The appropriate response is to inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement.
Incorrect Answers
A:“VXLAN adds encapsulation overhead, so underlay MTU must accommodate the intended overlay frame size” belongs to a separate EVPN issue: an EVPN-VXLAN frame is dropped over a path where the IP underlay MTU was sized only for unencapsulated Ethernet payloads. It does not explain the condition tested here.
B:“EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops” belongs to a separate EVPN issue: a dual-attached Ethernet segment experiences persistent duplicates during link recovery because multihoming election or ESI state differs. It does not explain the condition tested here.
D:“VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic” belongs to a separate EVPN issue: a fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. It does not explain the condition tested here.
Question 483
A network change is required for the following specific situation: A VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side. Which corrective action is most appropriate?
- Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration.
- Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement.
- Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
- Test larger encapsulated frames and align supported underlay and overlay MTUs without disabling unrelated protections.
Explanation
Correct Answer
B:EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set. Verify this by checking that BUM traffic reaches only participating VTEPs and the remote endpoint can be discovered.
Incorrect Answers
A:“Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration” belongs to a separate EVPN issue: an EVPN multihomed endpoint creates duplicate forwarding when two leafs both forward the same BUM traffic without appropriate split-horizon behavior. It does not explain the condition tested here.
C:“Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map” belongs to a separate EVPN issue: a fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. It does not explain the condition tested here.
D:“Test larger encapsulated frames and align supported underlay and overlay MTUs without disabling unrelated protections” belongs to a separate EVPN issue: an EVPN-VXLAN frame is dropped over a path where the IP underlay MTU was sized only for unencapsulated Ethernet payloads. It does not explain the condition tested here.
Question 484
A network change is required for the following specific situation: Two equal LOCAL_PREF and AS-path candidates remain tied until MED influences the choice under the applicable comparison rules. Which corrective action is most appropriate?
- Read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence.
- Restore permitted next-hop reachability via IGP or adjust next-hop policy where appropriate; recheck route detail.
- Check the advertised AS sequence and correct the peering or routing design instead of bypassing loop checks.
- Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Explanation
Correct Answer
A:MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions. Verify this by checking that the chosen best path follows the documented attribute ordering rather than a single observed MED value.
Incorrect Answers
B:“Restore permitted next-hop reachability via IGP or adjust next-hop policy where appropriate; recheck route detail” belongs to a separate Border Gateway Protocol (BGP) issue: an iBGP route is received from a reflector but hidden because its third-party next hop is unreachable in inet.0. It does not explain the condition tested here.
C:“Check the advertised AS sequence and correct the peering or routing design instead of bypassing loop checks” belongs to a separate Border Gateway Protocol (BGP) issue: a carrier changes an upstream routing arrangement and a downstream Junos router detects its own AS in the advertised AS path. It does not explain the condition tested here.
D:“Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy” belongs to a separate Border Gateway Protocol (BGP) issue: an IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement. It does not explain the condition tested here.
Question 485
A network change is required for the following specific situation: A customer access switch trusts external CoS bits and redistributes high-priority markings to all guest traffic. Which corrective action is most appropriate?
- Map the two packet categories to the intended PLP levels and verify drop-profile response.
- Assign the intended service class and scheduler priorities with measured bandwidth needs, then validate.
- Apply an approved behavior-aggregate classifier with the intended DSCP-to-class mapping on the real ingress interface.
- Define a controlled rewrite map for each class and verify high-priority markings remain restricted.
Explanation
Correct Answer
D:CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings. Verify this by checking that only approved media streams leave with high-priority code points; backup traffic uses its designated mark.
Incorrect Answers
A:“Map the two packet categories to the intended PLP levels and verify drop-profile response” belongs to a separate Class of Service (CoS) issue: a business wants out-of-profile marked traffic to drop earlier than in-profile traffic within one forwarding class. It does not explain the condition tested here.
B:“Assign the intended service class and scheduler priorities with measured bandwidth needs, then validate” belongs to a separate Class of Service (CoS) issue: two queues use the same scheduler priority, but the business expects one to always win during contention. It does not explain the condition tested here.
C:“Apply an approved behavior-aggregate classifier with the intended DSCP-to-class mapping on the real ingress interface” belongs to a separate Class of Service (CoS) issue: a campus uplink transmits marked video as ordinary data because no behavior-aggregate classifier is attached at ingress. It does not explain the condition tested here.
Question 486
A Junos enterprise team investigates this incident: A redundant L2 topology creates a broadcast storm after an edge port connected to another switch is treated as an endpoint. Which technical explanation most directly identifies the cause or design principle?
- Spanning-tree edge-port assumptions are intended for non-switching endpoints, not redundant bridging connections.
- Private VLAN isolated ports are designed to limit lateral L2 communication while still reaching the permitted promiscuous uplink.
- Overbroad match conditions can cause unauthorized VLAN steering and affect both security and reachability.
- A private VLAN community allows permitted communication within its community; isolated behavior is stricter.
Explanation
Correct Answer
A:Spanning-tree edge-port assumptions are intended for non-switching endpoints, not redundant bridging connections. The appropriate response is to remove incorrect edge treatment, validate BPDU reception and restore loop-free port roles.
Incorrect Answers
B:“Private VLAN isolated ports are designed to limit lateral L2 communication while still reaching the permitted promiscuous uplink” belongs to a separate Ethernet Switching and Spanning Tree issue: a shared guest access VLAN allows two untrusted hotel-room ports to communicate directly, violating the isolation design. It does not explain the condition tested here.
C:“Overbroad match conditions can cause unauthorized VLAN steering and affect both security and reachability” belongs to a separate Ethernet Switching and Spanning Tree issue: a filter-based VLAN security design uses a rule that catches too many packets and steers legitimate devices into quarantine. It does not explain the condition tested here.
D:“A private VLAN community allows permitted communication within its community; isolated behavior is stricter” belongs to a separate Ethernet Switching and Spanning Tree issue: members of the same trusted workgroup are accidentally placed in isolated rather than community PVLAN ports and lose peer communication. It does not explain the condition tested here.
Question 487
Which suggested shortcut would be especially unsafe for this exact situation? A controlled one-source data feed requires group membership constrained by both source and group, not arbitrary senders.
- Document whether multicast RPF uses inet.0 or inet.2 and verify after topology changes.
- Check multicast and unicast topology alignment whenever routing paths or metrics change.
- Include routed-interface PIM enrollment in the multicast deployment checklist.
- Assume an ASM (*,G) join identifies and restricts a unique approved source by itself.
Explanation
Correct Answer
D:The tempting alternative fails because source-specific multicast uses (S,G) membership semantics and generally avoids ASM rendezvous-point discovery for that flow. The supported action is to select an appropriate SSM group range and verify source-specific IGMPv3/PIM signaling on the supported platform.
Incorrect Answers
A:That prevention measure relates to a campus uses a separate inet.2 multicast RPF table and investigators inspect only inet.0, overlooking a stale source route.; it is not the unsafe shortcut described here.
B:That prevention measure relates to multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a PIM sparse-mode segment cannot maintain neighbor state because PIM is configured on the wrong routed interface.; it is not the unsafe shortcut described here.
Question 488
A network change is required for the following specific situation: A route with a permissive policy term is accepted before a later deny term can block it. Which corrective action is most appropriate?
- Inspect per-route local preferences and import policy; set the intended exit's LOCAL_PREF consistently.
- Use precise route-filter match conditions and explicit rejection of unauthorized more-specific routes.
- Put specific deny conditions before broad acceptance, and test the policy with representative routes.
- Document and test terminal accept or reject behavior along with next-term and next-policy handling.
Explanation
Correct Answer
C:Routing-policy term order and terminal actions determine whether later conditions are evaluated. Verify this by checking that the unauthorized route is rejected while intended export cases still match the proper terms.
Incorrect Answers
A:“Inspect per-route local preferences and import policy; set the intended exit's LOCAL_PREF consistently” belongs to a separate Border Gateway Protocol (BGP) issue: an enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path. It does not explain the condition tested here.
B:“Use precise route-filter match conditions and explicit rejection of unauthorized more-specific routes” belongs to a separate Border Gateway Protocol (BGP) issue: a prefix-list matches a broad aggregate but accepts unwanted subprefixes from a new external neighbor. It does not explain the condition tested here.
D:“Document and test terminal accept or reject behavior along with next-term and next-policy handling” belongs to a separate Border Gateway Protocol (BGP) issue: a route policy lacks an explicit intended default action, and unmatched BGP prefixes behave differently than planned. It does not explain the condition tested here.
Question 489
The team believes it has resolved this Junos issue: A trading-data sender needs to serve many local subscribers, but each listener receives its own redundant copy over the backbone. Which observation best verifies the specific intended result?
- Remote ASM receivers can discover the intended source and request multicast delivery through the proper tree.
- Backbone utilization reflects one upstream multicast copy per tree branch while interested receivers obtain the stream.
- Subscribed receivers get the stream without unnecessary flood to ports that did not join.
- RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
Explanation
Correct Answer
B:Backbone utilization reflects one upstream multicast copy per tree branch while interested receivers obtain the stream. This checks the relevant result after design a multicast distribution tree with explicit receiver memberships and test only the subscribed delivery paths.
Incorrect Answers
A:“Remote ASM receivers can discover the intended source and request multicast delivery through the proper tree” belongs to a separate IP Multicast issue: a multicast source is active in a different PIM domain but the local ASM RP never learns the source mapping. It does not explain the condition tested here.
C:“Subscribed receivers get the stream without unnecessary flood to ports that did not join” belongs to a separate IP Multicast issue: an access VLAN floods every multicast packet because IGMP snooping state was lost during migration. It does not explain the condition tested here.
D:“RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces” belongs to a separate IP Multicast issue: multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core. It does not explain the condition tested here.
Question 490
To prevent recurrence of this precise networking failure, which practice should be adopted? A distribution node learns connected subnets but never sends Hello packets on its OSPF transit port due to passive-interface policy.
- Test one allowed and one forbidden route against each export policy term before deployment.
- Classify loopbacks and user-facing links separately from peer links when applying passive templates.
- Keep IPv4 and IPv6 routing verification separate for dual-stack maintenance.
- Record both LSDB presence and local RIB installation in OSPF troubleshooting runbooks.
Explanation
Correct Answer
B:Classify loopbacks and user-facing links separately from peer links when applying passive templates. This guards against making a link passive suppresses OSPF adjacency formation even when its prefix remains eligible for advertisement.
Incorrect Answers
A:“Test one allowed and one forbidden route against each export policy term before deployment” belongs to a separate Interior Gateway Protocols (IGPs) issue: a branch default-route injection stops after a policy matches OSPF-learned routes instead of the intended local static. It does not explain the condition tested here.
C:“Keep IPv4 and IPv6 routing verification separate for dual-stack maintenance” belongs to a separate Interior Gateway Protocols (IGPs) issue: an OSPFv3 adjacency on a dual-stack campus changes state because engineers treat IPv4 interface reachability as proof of IPv6 control-plane health. It does not explain the condition tested here.
D:“Record both LSDB presence and local RIB installation in OSPF troubleshooting runbooks” belongs to a separate Interior Gateway Protocols (IGPs) issue: a core node shows a missing route while remote LSDBs include the corresponding external LSA after a local policy change. It does not explain the condition tested here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests