100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 500
Select THREE complementary corrective, verification, or preventive controls for this scenario: A branch uplink uses area 0.0.0.6 on one router and area 0.0.0.9 on its peer after a template copy.
- Validate per-interface OSPF area assignments from an approved topology matrix before commit.
- OSPF neighbor state reaches Full and the expected area LSDB receives the neighbor advertisements.
- Change only router IDs while leaving the mismatched interface areas intact.
- Add a catch-all accept at the end of the policy to bypass the source-type error.
- Restart the entire OSPFv2 process and assume this fixes a missing OSPFv3 loopback.
- Compare configured interface areas with the approved topology and put both interfaces in the intended matching area.
Explanation
Correct Answers
A:Prevention of recurrence: OSPF neighbors must agree on the area context to form adjacency on the common link.
B:Confirmation: Compare configured interface areas with the approved topology and put both interfaces in the intended matching area.
F:Correction: OSPF neighbors must agree on the area context to form adjacency on the common link.
Incorrect Answers
C:“Change only router IDs while leaving the mismatched interface areas intact” does not address OSPF neighbors must agree on the area context to form adjacency on the common link.
D:“Add a catch-all accept at the end of the policy to bypass the source-type error” is an unsafe response to a different problem: an OSPF export term filters routes based on the wrong protocol, so an intended static default is not originated. It is not a valid fix here.
E:“Restart the entire OSPFv2 process and assume this fixes a missing OSPFv3 loopback” is an unsafe response to a different problem: OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout. It is not a valid fix here.
Question 501
A Junos enterprise team investigates this incident: A new endpoint MAC is learned at a remote VTEP but never reaches the receiving leaf's EVPN control-plane table. Which technical explanation most directly identifies the cause or design principle?
- VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
- VXLAN adds encapsulation overhead, so underlay MTU must accommodate the intended overlay frame size.
- EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane.
- EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops.
Explanation
Correct Answer
C:EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane. The appropriate response is to check relevant BGP EVPN Type 2 advertisements, MAC mobility updates and import policy for the affected bridge domain.
Incorrect Answers
A:“VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic” belongs to a separate EVPN issue: a campus extension carries the right VXLAN outer header but directs frames to the wrong tenant bridge domain due to bad VNI mapping. It does not explain the condition tested here.
B:“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.
D:“EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops” 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.
Question 502
A Junos enterprise team investigates this incident: Two OSPF routers on a shared transit segment report different Hello and dead intervals and never establish adjacency. Which technical explanation most directly identifies the cause or design principle?
- An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology.
- Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate.
- OSPF neighbors require compatible Hello and dead interval settings on the shared interface.
- OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
Explanation
Correct Answer
C:OSPF neighbors require compatible Hello and dead interval settings on the shared interface. The appropriate response is to compare OSPF interface timers and align the two peers to approved Hello and dead values.
Incorrect Answers
A:“An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology” belongs to a separate Interior Gateway Protocols (IGPs) issue: OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout. It does not explain the condition tested here.
B:“Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate” belongs to a separate Interior Gateway Protocols (IGPs) issue: a team wrongly concludes OSPFv3 failed when inet6.0 shows a static route active and the OSPFv3 candidate inactive. It does not explain the condition tested here.
D:“OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication” belongs to a separate Interior Gateway Protocols (IGPs) issue: a new IPv6 peering uses OSPFv3 on a retired VLAN unit rather than the active routed transit interface. It does not explain the condition tested here.
Question 503
Which suggested shortcut would be especially unsafe for this exact situation? A campus onboarding policy puts cameras on the normal data VLAN even though a targeted filter-based VLAN should steer them.
- Scope and monitor tunneled L2 control protocols to prevent control-plane abuse.
- Assume naming a quarantine VLAN automatically steers matching traffic without an applied filter.
- Version-control MSTP name, revision and VLAN mapping as one change unit.
- Audit edge classifications and apply appropriate BPDU protection on true client-facing ports.
Explanation
Correct Answer
B:The tempting alternative fails because filter-based VLAN assignment depends on correctly matching the selected traffic and applying the filter at the right ingress point. The supported action is to inspect match conditions and attachment point, then change the approved filter-based VLAN steering rule.
Incorrect Answers
A:That prevention measure relates to an 802.1Q trunk carries customer data through a provider Ethernet segment but fails to forward the required spanning-tree control frames transparently.; it is not the unsafe shortcut described here.
C:That prevention measure relates to two adjacent MSTP switches show different region digests after one has a different VLAN-to-instance map.; it is not the unsafe shortcut described here.
D:That prevention measure relates to a campus mistakenly enables edge behavior on a switch-to-switch trunk and a loop appears when a backup link activates.; it is not the unsafe shortcut described here.
Question 504
A network change is required for the following specific situation: A phone supports LLDP-MED but the switch sends no med TLVs after a policy template disables the feature. Which corrective action is most appropriate?
- Verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media.
- Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access.
- Check switch PoE budget, negotiated device requirements and per-port allocation, then rebalance or provision supported power.
- Configure an approved voice VLAN on the port while keeping the PC data VLAN constrained.
Explanation
Correct Answer
B:Base LLDP discovery and LLDP-MED telephony advertisement are distinct capabilities and may require separate enablement. Verify this by checking that packet and operational views show the required LLDP-MED telephony TLVs at the correct interface.
Incorrect Answers
A:“Verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media” belongs to a separate IP Telephony Features issue: a handset follows LLDP-MED voice VLAN advertisement but sends SIP media with the wrong priority marking for the campus QoS design. It does not explain the condition tested here.
C:“Check switch PoE budget, negotiated device requirements and per-port allocation, then rebalance or provision supported power” belongs to a separate IP Telephony Features issue: a voice handset fails to boot on an EX switch port after new cameras consume the remaining PoE budget. It does not explain the condition tested here.
D:“Configure an approved voice VLAN on the port while keeping the PC data VLAN constrained” belongs to a separate IP Telephony Features issue: a desk phone sends tagged voice traffic, but the switchport permits only the untagged data VLAN. It does not explain the condition tested here.
Question 505
To prevent recurrence of this precise networking failure, which practice should be adopted? A shared Ethernet segment loses its fast convergence properties after an ESI-LAG peer receives an inconsistent configuration.
- Maintain a central VNI registry and test cross-tenant isolation on each leaf rollout.
- Keep route-type purpose and acceptance checks in EVPN troubleshooting runbooks.
- Audit ESI consistency and platform-supported multihoming mode across paired leafs.
- Validate EVPN Type 2 and Type 3 propagation separately in new VNI bring-up tests.
Explanation
Correct Answer
C:Audit ESI consistency and platform-supported multihoming mode across paired leafs. This guards against EVPN Ethernet segment identifiers associate redundant attachments with one multihoming segment and support coordinated convergence.
Incorrect Answers
A:“Maintain a central VNI registry and test cross-tenant isolation on each leaf rollout” 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.
B:“Keep route-type purpose and acceptance checks in EVPN troubleshooting runbooks” belongs to a separate EVPN issue: a fabric advertises Type 3 routes and claims this proves specific remote host MACs are reachable. It does not explain the condition tested here.
D:“Validate EVPN Type 2 and Type 3 propagation separately in new VNI bring-up tests” belongs to a separate EVPN issue: a VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side. It does not explain the condition tested here.
Question 506
A network change is required for the following specific situation: A router prefers a longer AS path when a higher LOCAL_PREF makes that route win, surprising the transit team. Which corrective action is most appropriate?
- Inspect reflector/client relationships and cluster behavior, then correct the intended route-reflector configuration.
- Examine both attributes in the received route detail and update the explicit routing policy rather than guessing.
- Use precise route-filter match conditions and explicit rejection of unauthorized more-specific routes.
- Compare BGP best-path and multipath eligibility conditions, then enable approved multipath behavior and validate forwarding.
Explanation
Correct Answer
B:For eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner. Verify this by checking that after policy correction, chosen path and attribute ordering match documented routing intent.
Incorrect Answers
A:“Inspect reflector/client relationships and cluster behavior, then correct the intended route-reflector configuration” belongs to a separate Border Gateway Protocol (BGP) issue: a route-reflector topology loses an iBGP-advertised prefix because clients are not configured under the intended reflector cluster. It does not explain the condition tested here.
C:“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:“Compare BGP best-path and multipath eligibility conditions, then enable approved multipath behavior and validate forwarding” belongs to a separate Border Gateway Protocol (BGP) issue: equal candidate BGP routes are visible but no multipath forwarding entry is installed because eligibility or policy differs. It does not explain the condition tested here.
Question 507
To prevent recurrence of this precise networking failure, which practice should be adopted? A non-802.1X network printer is consistently rejected because its access port permits only EAP supplicants.
- Review MAC-device inventory, spoofing exposure and expiry before using MAC-based authorization.
- Include downstream device count and authentication method in desk-port templates.
- Test captive-portal redirects, session expiry and post-login VLAN access in guest-network acceptance.
- Verify RADIUS attribute handling and model/release feature support before rolling out dynamic assignment.
Explanation
Correct Answer
A:Review MAC-device inventory, spoofing exposure and expiry before using MAC-based authorization. This guards against MAC RADIUS provides a fallback identity mechanism for suitable non-802.1X devices, with weaker assurance than certificate-based 802.1X.
Incorrect Answers
B:“Include downstream device count and authentication method in desk-port templates” belongs to a separate Layer 2 Authentication and Access Control issue: an access port is placed in single-supplicant mode but a desk phone and PC must authenticate separately behind the same port. It does not explain the condition tested here.
C:“Test captive-portal redirects, session expiry and post-login VLAN access in guest-network acceptance” belongs to a separate Layer 2 Authentication and Access Control issue: a visitor portal redirects browser traffic but never releases the user to the approved network after authentication. It does not explain the condition tested here.
D:“Verify RADIUS attribute handling and model/release feature support before rolling out dynamic assignment” belongs to a separate Layer 2 Authentication and Access Control issue: a switch receives successful RADIUS Access-Accept but the user still lands in an unexpected VLAN because the dynamic assignment is not supported on that platform. It does not explain the condition tested here.
Question 508
Select THREE complementary corrective, verification, or preventive controls for this scenario: A provider-facing policy stops honoring a route-tag community after a new import policy changes the attached communities.
- Use MED changes alone as guaranteed overrides of a conflicting higher local preference.
- Increase the route's MED while leaving BGP transport reachability and hop settings incorrect.
- A controlled route is withheld from prohibited peers while approved routes retain their expected advertisements.
- Assume attaching a BGP community automatically prevents all external redistribution without policy.
- Inspect received communities and export policy terms, then attach a tested community match and reject rule.
- Maintain community inventories and test outbound policy outcomes for allowed and denied prefixes.
Explanation
Correct Answers
C:Confirmation: Inspect received communities and export policy terms, then attach a tested community match and reject rule.
E:Correction: Communities are policy metadata; tagging does not enforce advertisement restrictions unless a matching policy acts on it.
F:Prevention of recurrence: Communities are policy metadata; tagging does not enforce advertisement restrictions unless a matching policy acts on it.
Incorrect Answers
A:“Use MED changes alone as guaranteed overrides of a conflicting higher local preference” is an unsafe response to a different problem: an enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path. It is not a valid fix here.
B:“Increase the route's MED while leaving BGP transport reachability and hop settings incorrect” is an unsafe response to a different problem: a transit peering is moved off directly connected interface IPs to loopbacks yet the TTL and reachability design are not updated. It is not a valid fix here.
D:“Assume attaching a BGP community automatically prevents all external redistribution without policy” does not address communities are policy metadata; tagging does not enforce advertisement restrictions unless a matching policy acts on it.
Question 509
A Junos enterprise team investigates this incident: An aggregation network sees customer VLAN IDs collide because several tenants share the same single-tagged provider infrastructure. Which technical explanation most directly identifies the cause or design principle?
- MSTP maps VLANs into a smaller set of spanning-tree instances, providing scalable per-group path control.
- MSTP region membership depends on compatible region parameters such as name, revision and VLAN-to-instance map.
- Q-in-Q encapsulation can place a provider outer tag around customer VLAN tags to isolate transport context.
- Spanning-tree edge-port assumptions are intended for non-switching endpoints, not redundant bridging connections.
Explanation
Correct Answer
C:Q-in-Q encapsulation can place a provider outer tag around customer VLAN tags to isolate transport context. The appropriate response is to design supported stacked VLAN tagging and verify S-tag/C-tag placement at the correct ingress and egress.
Incorrect Answers
A:“MSTP maps VLANs into a smaller set of spanning-tree instances, providing scalable per-group path control” belongs to a separate Ethernet Switching and Spanning Tree issue: a large campus places hundreds of VLANs in separate spanning-tree instances and reaches scale or CPU limits. It does not explain the condition tested here.
B:“MSTP region membership depends on compatible region parameters such as name, revision and VLAN-to-instance map” belongs to a separate Ethernet Switching and Spanning Tree issue: two adjacent MSTP switches show different region digests after one has a different VLAN-to-instance map. It does not explain the condition tested here.
D:“Spanning-tree edge-port assumptions are intended for non-switching endpoints, not redundant bridging connections” belongs to a separate Ethernet Switching and Spanning Tree issue: a redundant L2 topology creates a broadcast storm after an edge port connected to another switch is treated as an endpoint. It does not explain the condition tested here.
Question 510
To prevent recurrence of this precise networking failure, which practice should be adopted? An ingress classification filter for one terminal type inadvertently redirects other hosts using the same uplink.
- Version-control MSTP name, revision and VLAN mapping as one change unit.
- Check policy coverage and unintended-match cases before activating filter-based steering.
- Scope and monitor tunneled L2 control protocols to prevent control-plane abuse.
- Audit edge classifications and apply appropriate BPDU protection on true client-facing ports.
Explanation
Correct Answer
B:Check policy coverage and unintended-match cases before activating filter-based steering. This guards against overbroad match conditions can cause unauthorized VLAN steering and affect both security and reachability.
Incorrect Answers
A:“Version-control MSTP name, revision and VLAN mapping as one change unit” belongs to a separate Ethernet Switching and Spanning Tree issue: two adjacent MSTP switches show different region digests after one has a different VLAN-to-instance map. It does not explain the condition tested here.
C:“Scope and monitor tunneled L2 control protocols to prevent control-plane abuse” belongs to a separate Ethernet Switching and Spanning Tree issue: an 802.1Q trunk carries customer data through a provider Ethernet segment but fails to forward the required spanning-tree control frames transparently. It does not explain the condition tested here.
D:“Audit edge classifications and apply appropriate BPDU protection on true client-facing ports” belongs to a separate Ethernet Switching and Spanning Tree issue: a redundant L2 topology creates a broadcast storm after an edge port connected to another switch is treated as an endpoint. It does not explain the condition tested here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests