100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 160
A Junos enterprise team investigates this incident: Two newly deployed distribution switches report identical OSPF router IDs, causing inconsistent LSAs in the area. Which technical explanation most directly identifies the cause or design principle?
- Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability.
- OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
- OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
- Local import policy can affect installed route visibility independently of the remote origination of LSAs.
Explanation
Correct Answer
B:OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior. The appropriate response is to assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence.
Incorrect Answers
A:“Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability” belongs to a separate Interior Gateway Protocols (IGPs) issue: a redistribution policy injects every static route into OSPF, including a maintenance-only prefix that should stay local. It does not explain the condition tested here.
C:“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.
D:“Local import policy can affect installed route visibility independently of the remote origination of LSAs” 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.
Question 161
Select THREE complementary corrective, verification, or preventive controls for this scenario: Two newly deployed distribution switches report identical OSPF router IDs, causing inconsistent LSAs in the area.
- Reset OSPFv3 adjacency repeatedly although the route exists as a nonactive candidate.
- Assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence.
- Record a successful IPv4 echo response as conclusive proof that OSPFv3 is healthy.
- Reserve router IDs from a centrally managed inventory before zero-touch provisioning.
- Raise interface OSPF costs without resolving the duplicated router IDs.
- No router-ID collision appears and OSPF paths stabilize with expected next hops.
Explanation
Correct Answers
B:Correction: OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
D:Prevention of recurrence: OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
F:Confirmation: Assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence.
Incorrect Answers
A:“Reset OSPFv3 adjacency repeatedly although the route exists as a nonactive candidate” is an unsafe response to a different problem: a team wrongly concludes OSPFv3 failed when inet6.0 shows a static route active and the OSPFv3 candidate inactive. It is not a valid fix here.
C:“Record a successful IPv4 echo response as conclusive proof that OSPFv3 is healthy” is an unsafe response to a different problem: an OSPFv3 adjacency on a dual-stack campus changes state because engineers treat IPv4 interface reachability as proof of IPv6 control-plane health. It is not a valid fix here.
E:“Raise interface OSPF costs without resolving the duplicated router IDs” does not address OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
Question 162
Which suggested shortcut would be especially unsafe for this exact situation? A switch logs EAP timeout while the endpoint has no 802.1X supplicant, yet the operator rotates valid RADIUS passwords repeatedly.
- Classify interactive and headless endpoint requirements before choosing the access method.
- Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions.
- Rotate every user's password without checking whether the endpoint sent an EAP response at all.
- Test multi-method paths including success, reject and timeout cases before deployment.
Explanation
Correct Answer
C:The tempting alternative fails because supplicant absence is a distinct failure from an invalid credential or unreachable authentication server. The supported action is to inspect packet exchange and classify the endpoint before selecting a supported fallback method.
Incorrect Answers
A:That prevention measure relates to a noninteractive sensor is trapped in captive-portal onboarding because operators selected browser authentication for all endpoints.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a printer's MAC address is duplicated by an unauthorized endpoint that obtains the same weak MAC-based policy.; it is not the unsafe shortcut described here.
D:That prevention measure relates to two authentication methods are enabled on a shared switch port but fallback ordering bypasses a successful 802.1X result.; it is not the unsafe shortcut described here.
Question 163
The team believes it has resolved this Junos issue: Multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core. Which observation best verifies the specific intended result?
- The required PIM neighbors appear and downstream join state tracks active interested receivers.
- 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.
- Backbone utilization reflects one upstream multicast copy per tree branch while interested receivers obtain the stream.
Explanation
Correct Answer
C:RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces. This checks the relevant result after inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
Incorrect Answers
A:“The required PIM neighbors appear and downstream join state tracks active interested receivers” belongs to a separate IP Multicast issue: a PIM sparse-mode segment cannot maintain neighbor state because PIM is configured on the wrong routed interface. It does not explain the condition tested here.
B:“Subscribed receivers get the stream without unnecessary flood to ports that did not join” belongs to a separate IP Multicast issue: a receiver port stops getting multicast because IGMP membership was not processed by the access switch after an interface move. It does not explain the condition tested here.
D:“Backbone utilization reflects one upstream multicast copy per tree branch while interested receivers obtain the stream” belongs to a separate IP Multicast issue: a one-to-many lecture stream is configured as separate unicast connections and saturates a WAN link to a remote campus. It does not explain the condition tested here.
Question 164
A Junos enterprise team investigates this incident: An IPv6 transit prefix is hidden because its next-hop address is absent from the correct IPv6 routing table. Which technical explanation most directly identifies the cause or design principle?
- BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops.
- MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
- BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state.
- Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints.
Explanation
Correct Answer
A:BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops. The appropriate response is to check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Incorrect Answers
B:“MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions” belongs to a separate Border Gateway Protocol (BGP) issue: two equal LOCAL_PREF and AS-path candidates remain tied until MED influences the choice under the applicable comparison rules. It does not explain the condition tested here.
C:“BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state” belongs to a separate Border Gateway Protocol (BGP) issue: a campus router's BGP IPv6 session is Established yet peers advertise only inet unicast family routes. It does not explain the condition tested here.
D:“Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints” belongs to a separate Border Gateway Protocol (BGP) issue: a multihop eBGP peer uses loopback addresses but its session times out when directly connected assumptions remain. It does not explain the condition tested here.
Question 165
The team believes it has resolved this Junos issue: A business wants out-of-profile marked traffic to drop earlier than in-profile traffic within one forwarding class. Which observation best verifies the specific intended result?
- Voice traffic receives the required scheduled service at the congested egress without starving other classes.
- During controlled congestion, out-of-profile traffic experiences earlier drops than in-profile traffic.
- Queue depth, latency and drop statistics meet documented objectives during realistic traffic load.
- Packet captures show the intended DSCP or 802.1p fields on outbound voice, video and data traffic.
Explanation
Correct Answer
B:During controlled congestion, out-of-profile traffic experiences earlier drops than in-profile traffic. This checks the relevant result after map the two packet categories to the intended PLP levels and verify drop-profile response.
Incorrect Answers
A:“Voice traffic receives the required scheduled service at the congested egress without starving other classes” belongs to a separate Class of Service (CoS) issue: a low-latency queue is correctly classified but voice delays because its egress scheduler map is absent from the trunk. It does not explain the condition tested here.
C:“Queue depth, latency and drop statistics meet documented objectives during realistic traffic load” belongs to a separate Class of Service (CoS) issue: video gets dropped under congestion despite spare capacity because its queue has a too-small delay buffer. It does not explain the condition tested here.
D:“Packet captures show the intended DSCP or 802.1p fields on outbound voice, video and data traffic” belongs to a separate Class of Service (CoS) issue: a provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior. It does not explain the condition tested here.
Question 166
Which suggested shortcut would be especially unsafe for this exact situation? An IP phone uses the wrong location information for emergency response after a switch move.
- Capacity-plan PoE power classes and reserved headroom before connecting new powered devices.
- Test both tagged phone frames and untagged PC frames during phone-port commissioning.
- Validate PD power profiles and test peak draw rather than idle boot alone.
- Treat the old physical room value as correct because IP addressing did not change.
Explanation
Correct Answer
D:The tempting alternative fails because LLDP-MED location metadata can support telephony location services and must match actual switch-port placement. The supported action is to update the approved location mapping and confirm transmitted LLDP-MED location information on the affected port.
Incorrect Answers
A:That prevention measure relates to a voice handset fails to boot on an EX switch port after new cameras consume the remaining PoE budget.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a phone-with-PC desk deployment lets the PC reach data services while the tagged voice stream is dropped by VLAN membership.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a phone's LLDP-negotiated power demand exceeds its access port's allocated PoE limit and it repeatedly restarts.; it is not the unsafe shortcut described here.
Question 167
A network change is required for the following specific situation: Two adjacent MSTP switches show different region digests after one has a different VLAN-to-instance map. Which corrective action is most appropriate?
- Inspect match conditions and attachment point, then change the approved filter-based VLAN steering rule.
- Compare complete region configuration on the peers and restore the approved shared MSTP region values.
- Inspect the primary/secondary association to shared-service promiscuous ports, then correct only authorized connectivity.
- Inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation.
Explanation
Correct Answer
B:MSTP region membership depends on compatible region parameters such as name, revision and VLAN-to-instance map. Verify this by checking that both switches show compatible region membership and intended instance root/port roles.
Incorrect Answers
A:“Inspect match conditions and attachment point, then change the approved filter-based VLAN steering rule” belongs to a separate Ethernet Switching and Spanning Tree issue: a policy-based VLAN filter moves matching device traffic to a quarantine VLAN but a rule fails to match the intended MAC or packet fields. It does not explain the condition tested here.
C:“Inspect the primary/secondary association to shared-service promiscuous ports, then correct only authorized connectivity” belongs to a separate Ethernet Switching and Spanning Tree issue: a building's private VLAN design inadvertently limits tenant access to a shared printer uplink while direct tenant communication is supposed to stay blocked. It does not explain the condition tested here.
D:“Inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation” belongs to a separate Ethernet Switching and Spanning Tree issue: customer traffic emerges with the provider service tag still attached and is rejected by an endpoint expecting ordinary Ethernet. It does not explain the condition tested here.
Question 168
A Junos enterprise team investigates this incident: A dual-homed site changes internal LOCAL_PREF but sees no change in the other autonomous system's inbound traffic choice. Which technical explanation most directly identifies the cause or design principle?
- Routing-policy evaluation depends on term matches, flow-control actions and the policy chain, including what happens on no match.
- LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors.
- iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology.
- For eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner.
Explanation
Correct Answer
B:LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors. The appropriate response is to select a permitted inbound traffic-engineering mechanism with the provider, such as suitable AS-path prepending or agreed communities.
Incorrect Answers
A:“Routing-policy evaluation depends on term matches, flow-control actions and the policy chain, including what happens on no match” 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.
C:“iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology” belongs to a separate Border Gateway Protocol (BGP) issue: a full-mesh iBGP design is converted to route reflection but one peer is treated as an ordinary nonclient and route propagation fails. It does not explain the condition tested here.
D:“For eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner” belongs to a separate Border Gateway Protocol (BGP) issue: a router prefers a longer AS path when a higher LOCAL_PREF makes that route win, surprising the transit team. It does not explain the condition tested here.
Question 169
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A new switch automatically discovers VLAN registrations on one trunk, but an intermediate trunk lacks MVRP participation and blocks the VLAN.
- Inspect MVRP state and permitted VLANs on each trunk; enable supported participation on the missing hop.
- Assume setting one global RSTP root automatically produces independently chosen roots for every VSTP VLAN.
- Assume that one switch's locally created VLAN is automatically registered on all links with MVRP disabled.
- The VLAN registration propagates to the intended downstream trunk and reaches its member ports.
- Make every tenant port promiscuous simply to restore one workgroup's access.
Explanation
Correct Answers
A:Inspect MVRP state and permitted VLANs on each trunk; enable supported participation on the missing hop. This addresses the dependency that MVRP distributes VLAN registration information across participating links; a gap can stop propagation.
D:The VLAN registration propagates to the intended downstream trunk and reaches its member ports. The specific steps required are to inspect MVRP state and permitted VLANs on each trunk; enable supported participation on the missing hop.
Incorrect Answers
B:“Assume setting one global RSTP root automatically produces independently chosen roots for every VSTP VLAN” is an unsafe response to a different problem: a legacy interop design needs separate per-VLAN spanning-tree compatibility but all VLANs inherit one unsuitable tree. It is not a valid fix here.
C:“Assume that one switch's locally created VLAN is automatically registered on all links with MVRP disabled” does not address MVRP distributes VLAN registration information across participating links; a gap can stop propagation.
E:“Make every tenant port promiscuous simply to restore one workgroup's access” is an unsafe response to a different problem: a switch rollout splits a team that should communicate within one PVLAN community, while protecting it from another community. It is not a valid fix here.
Question 170
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: An access VLAN floods every multicast packet because IGMP snooping state was lost during migration.
- Disable IGMP snooping everywhere and assume uncontrolled flooding is equivalent to correct membership delivery.
- Assume inet.0 always controls PIM RPF even when an alternate multicast RPF table is configured.
- Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
- Assume an ASM (*,G) join identifies and restricts a unique approved source by itself.
- Subscribed receivers get the stream without unnecessary flood to ports that did not join.
Explanation
Correct Answers
C:Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports. This addresses the dependency that IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication.
E:Subscribed receivers get the stream without unnecessary flood to ports that did not join. The specific steps required are to inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
Incorrect Answers
A:“Disable IGMP snooping everywhere and assume uncontrolled flooding is equivalent to correct membership delivery” does not address IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication.
B:“Assume inet.0 always controls PIM RPF even when an alternate multicast RPF table is configured” is an unsafe response to a different problem: a multicast team changes unicast routing yet an engineered multicast RPF table still points to an obsolete next hop. It is not a valid fix here.
D:“Assume an ASM (*,G) join identifies and restricts a unique approved source by itself” is an unsafe response to a different problem: a video source is known and receivers support IGMPv3, but engineers configure ASM and an RP unnecessarily for the source-specific application. It is not a valid fix here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests