100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 630
A network change is required for the following specific situation: An enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path. Which corrective action is most appropriate?
- Compare BGP best-path and multipath eligibility conditions, then enable approved multipath behavior and validate forwarding.
- Check the advertised AS sequence and correct the peering or routing design instead of bypassing loop checks.
- Inspect per-route local preferences and import policy; set the intended exit's LOCAL_PREF consistently.
- Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
Explanation
Correct Answer
C:BGP typically prefers a larger LOCAL_PREF among otherwise eligible candidates before later path-selection tie breakers. Verify this by checking that the selected BGP route reflects the intended higher LOCAL_PREF, and traceroute follows the approved exit.
Incorrect Answers
A:“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: two eBGP sessions over different transports are expected to provide ECMP but only one forwarding next hop appears. It does not explain the condition tested here.
B:“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: the local AS appears in a received external BGP AS_PATH and the route is rejected despite valid prefix reachability. It does not explain the condition tested here.
D:“Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it” belongs to a separate Border Gateway Protocol (BGP) issue: an engineer adds advertise-inactive and downstream peers begin receiving a BGP route that loses to an OSPF route locally. It does not explain the condition tested here.
Question 631
A network change is required for the following specific situation: A switch rollout splits a team that should communicate within one PVLAN community, while protecting it from another community. Which corrective action is most appropriate?
- Inspect VSTP VLAN membership, root priority and port roles, then repair the intended per-VLAN root arrangement.
- Compare complete region configuration on the peers and restore the approved shared MSTP region values.
- Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately.
- Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated.
Explanation
Correct Answer
D:A private VLAN community allows permitted communication within its community; isolated behavior is stricter. Verify this by checking that community members can communicate as intended while cross-community access remains blocked.
Incorrect Answers
A:“Inspect VSTP VLAN membership, root priority and port roles, then repair the intended per-VLAN root arrangement” belongs to a separate Ethernet Switching and Spanning Tree issue: a VSTP network intended to send voice and data VLANs over different active paths instead blocks both on the same uplink. It does not explain the condition tested here.
B:“Compare complete region configuration on the peers and restore the approved shared MSTP region values” 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:“Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately” belongs to a separate Ethernet Switching and Spanning Tree issue: a switch with an unexpectedly low bridge priority becomes MSTP root and redirects aggregation traffic through an access closet. It does not explain the condition tested here.
Question 632
Select THREE complementary corrective, verification, or preventive controls for this scenario: A route-reflector client receives an external destination but lacks the underlay path to the advertised next hop.
- Inspect next-hop attributes and IGP reachability; deliberately choose appropriate next-hop-self policy or add valid underlay routes.
- Review next-hop propagation and IGP coverage whenever an eBGP route enters iBGP.
- Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated.
- Disable all iBGP loop protection and expect the route-reflector hierarchy to be unnecessary.
- Assume TCP session Established proves every learned prefix has a usable forwarding next hop.
- Route detail shows a reachable next hop and end-to-end forwarding through the intended border router.
Explanation
Correct Answers
A:Correction: A reachable BGP peering session does not itself make a third-party route next hop recursively resolvable.
B:Prevention of recurrence: A reachable BGP peering session does not itself make a third-party route next hop recursively resolvable.
F:Confirmation: Inspect next-hop attributes and IGP reachability; deliberately choose appropriate next-hop-self policy or add valid underlay routes.
Incorrect Answers
C:“Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated” is an unsafe response to a different problem: a campus router's BGP IPv6 session is Established yet peers advertise only inet unicast family routes. It is not a valid fix here.
D:“Disable all iBGP loop protection and expect the route-reflector hierarchy to be unnecessary” is an unsafe response to a different problem: a route-reflector topology loses an iBGP-advertised prefix because clients are not configured under the intended reflector cluster. It is not a valid fix here.
E:“Assume TCP session Established proves every learned prefix has a usable forwarding next hop” does not address a reachable BGP peering session does not itself make a third-party route next hop recursively resolvable.
Question 633
To prevent recurrence of this precise networking failure, which practice should be adopted? An enterprise fallback design accidentally places unauthenticated users into the production network when all RADIUS servers fail.
- Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions.
- Verify RADIUS attribute handling and model/release feature support before rolling out dynamic assignment.
- Test fail-open/fail-closed decisions and platform-specific fallback capabilities in disaster recovery exercises.
- Test captive-portal redirects, session expiry and post-login VLAN access in guest-network acceptance.
Explanation
Correct Answer
C:Test fail-open/fail-closed decisions and platform-specific fallback capabilities in disaster recovery exercises. This guards against server-fail fallback must be an explicitly scoped authorization policy; availability cannot justify unbounded access.
Incorrect Answers
A:“Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions” belongs to a separate Layer 2 Authentication and Access Control issue: a MAC RADIUS device changes its network adapter and can no longer authenticate because its registered identifier is stale. It does not explain the condition tested here.
B:“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.
D:“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: guest users on an EX switch see no captive login page because browser HTTP redirects are not being applied on the intended VLAN. It does not explain the condition tested here.
Question 634
A network change is required for the following specific situation: A switch assigns equal PoE power priority to every port and disconnects an emergency phone before low-priority signage during a power shortage. 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.
- Set supported higher PoE priority for critical voice endpoints and validate the failure budget.
- Enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings.
Explanation
Correct Answer
C:PoE priority is a tool for allocating scarce power among endpoints when the chassis budget is constrained. Verify this by checking that the critical phone remains powered during a simulated shortage while lower-priority devices are shed as designed.
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.
B:“Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access” belongs to a separate IP Telephony Features issue: a powered endpoint detects a Junos switch but fails to negotiate voice prioritization because only ordinary LLDP is enabled. It does not explain the condition tested here.
D:“Enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings” belongs to a separate IP Telephony Features issue: a vendor handset discovers its neighbor using basic LLDP but does not learn the configured network policy for voice tagging. It does not explain the condition tested here.
Question 635
A network change is required for the following specific situation: A bridge domain has valid unicast Type 2 entries yet remote VTEPs do not discover a new participating segment for BUM forwarding. Which corrective action is most appropriate?
- Align the intended ESI and supported LAG mode, then inspect relevant EVPN Type 1 and Type 4 routes.
- Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
- Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement.
- Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies.
Explanation
Correct Answer
C: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:“Align the intended ESI and supported LAG mode, then inspect relevant EVPN Type 1 and Type 4 routes” belongs to a separate EVPN issue: a multihomed CE is attached to two leafs but one leaf advertises a different ESI, preventing expected redundancy behavior. It does not explain the condition tested here.
B:“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 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.
D:“Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies” belongs to a separate EVPN issue: a VXLAN overlay's BGP EVPN routes are present, but the underlay cannot route to a remote VTEP loopback. It does not explain the condition tested here.
Question 636
A network change is required for the following specific situation: A multicast source is active in a different PIM domain but the local ASM RP never learns the source mapping. Which corrective action is most appropriate?
- Compare source-route preference with actual multicast ingress and restore a consistent authorized upstream path.
- Identify the configured RPF table and verify the source route and next hop in that table before updating the multicast policy.
- Select an appropriate SSM group range and verify source-specific IGMPv3/PIM signaling on the supported platform.
- Inspect MSDP peer state and source-active information, then configure the permitted peer relationships.
Explanation
Correct Answer
D:MSDP is used in applicable ASM inter-RP designs to exchange active-source information between rendezvous points. Verify this by checking that remote ASM receivers can discover the intended source and request multicast delivery through the proper tree.
Incorrect Answers
A:“Compare source-route preference with actual multicast ingress and restore a consistent authorized upstream path” belongs to a separate IP Multicast issue: a stream uses asymmetric unicast routing; multicast forwarding fails intermittently although individual host routes work. It does not explain the condition tested here.
B:“Identify the configured RPF table and verify the source route and next hop in that table before updating the multicast policy” belongs to a separate IP Multicast issue: a campus uses a separate inet.2 multicast RPF table and investigators inspect only inet.0, overlooking a stale source route. It does not explain the condition tested here.
C:“Select an appropriate SSM group range and verify source-specific IGMPv3/PIM signaling on the supported platform” instead concerns another network scenario: A video source is known and receivers support IGMPv3, but engineers configure ASM and an RP unnecessarily for the source-specific application. It does not address the requirement here.
Question 637
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A BGP export policy advertises a prefix that exists only as an inactive local candidate, despite an expectation of default active-only behavior.
- The advertised set matches the documented inactive-BGP exception without changing local forwarding selection.
- Treat advertise-inactive as a universal method to export all hidden and rejected routes.
- Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
- Expect a locally set LOCAL_PREF value to propagate unchanged over standard eBGP to another AS.
- Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated.
Explanation
Correct Answers
A:The advertised set matches the documented inactive-BGP exception without changing local forwarding selection. The specific steps required are to inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
C:Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it. This addresses the dependency that Junos normally exports active routes; advertise-inactive can expose a best BGP candidate that lost to another protocol.
Incorrect Answers
B:“Treat advertise-inactive as a universal method to export all hidden and rejected routes” does not address Junos normally exports active routes; advertise-inactive can expose a best BGP candidate that lost to another protocol.
D:“Expect a locally set LOCAL_PREF value to propagate unchanged over standard eBGP to another AS” is an unsafe response to a different problem: an operator tries to make a remote AS prefer one inbound path using LOCAL_PREF that the remote eBGP peer never receives. It is not a valid fix here.
E:“Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated” is an unsafe response to a different problem: BGP peers exchange IPv4 NLRI correctly but a planned IPv6 customer route never appears in inet6.0. It is not a valid fix here.
Question 638
To prevent recurrence of this precise networking failure, which practice should be adopted? A router prefers a longer AS path when a higher LOCAL_PREF makes that route win, surprising the transit team.
- Test path equivalence, forwarding and failure convergence before enabling transit ECMP.
- Maintain expected BGP attribute decisions for every primary/secondary transit policy.
- Distinguish internal exit selection from inbound inter-AS path influence in routing design reviews.
- Track every BGP advertise-inactive exception and test cross-protocol route selection.
Explanation
Correct Answer
B:Maintain expected BGP attribute decisions for every primary/secondary transit policy. This guards against for eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner.
Incorrect Answers
A:“Test path equivalence, forwarding and failure convergence before enabling transit ECMP” 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.
C:“Distinguish internal exit selection from inbound inter-AS path influence in routing design reviews” belongs to a separate Border Gateway Protocol (BGP) issue: a dual-homed site changes internal LOCAL_PREF but sees no change in the other autonomous system's inbound traffic choice. It does not explain the condition tested here.
D:“Track every BGP advertise-inactive exception and test cross-protocol route selection” belongs to a separate Border Gateway Protocol (BGP) issue: a BGP export policy advertises a prefix that exists only as an inactive local candidate, despite an expectation of default active-only behavior. It does not explain the condition tested here.
Question 639
The team believes it has resolved this Junos issue: An OSPF neighbor remains Down because the routed transit interface was left passive after a site template rollout. Which observation best verifies the specific intended result?
- Hellos are observed in the routing adjacency and a Full neighbor appears on the intended port.
- Only authorized static prefixes appear as OSPF externals; management prefixes remain local.
- The team explains the selected active route and verifies intended failover without disturbing OSPFv3 adjacency.
- The affected link passes OSPFv3 neighbor and IPv6 reachability checks rather than IPv4-only tests.
Explanation
Correct Answer
A:Hellos are observed in the routing adjacency and a Full neighbor appears on the intended port. This checks the relevant result after remove passive behavior only from the approved router-to-router transit link and check Hello and neighbor states.
Incorrect Answers
B:“Only authorized static prefixes appear as OSPF externals; management prefixes remain local” belongs to a separate Interior Gateway Protocols (IGPs) issue: an ABR starts leaking a management static route into the enterprise IGP after a permissive export term was introduced. It does not explain the condition tested here.
C:“The team explains the selected active route and verifies intended failover without disturbing OSPFv3 adjacency” belongs to a separate Interior Gateway Protocols (IGPs) issue: an IPv6 route learned through OSPFv3 is absent from the forwarding table because a more preferred static route covers the same prefix. It does not explain the condition tested here.
D:“The affected link passes OSPFv3 neighbor and IPv6 reachability checks rather than IPv4-only tests” 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.
Question 640
Which suggested shortcut would be especially unsafe for this exact situation? A branch dual-transit design sees the higher-preference provider route win even though its AS path has more hops.
- Include next-hop reachability tests in iBGP and route-reflector deployment acceptance.
- Assume the shortest AS path must win regardless of any LOCAL_PREF difference.
- Review policy ordering with negative tests and explicit default actions on every change.
- Include show route hidden and policy term hit checks in BGP troubleshooting playbooks.
Explanation
Correct Answer
B:The tempting alternative fails because for eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner. The supported action is to examine both attributes in the received route detail and update the explicit routing policy rather than guessing.
Incorrect Answers
A:That prevention measure relates to an iBGP route is received from a reflector but hidden because its third-party next hop is unreachable in inet.0.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a BGP export configuration has a broad first match so a specific downstream deny never evaluates the target prefix.; it is not the unsafe shortcut described here.
D:That prevention measure relates to a Junos route is hidden by import policy, but the team troubleshoots only local physical interfaces.; it is not the unsafe shortcut described here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests