100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 310
A Junos enterprise team investigates this incident: A campus migration removes a VLAN at the source while a trunk continues advertising it unexpectedly. Which technical explanation most directly identifies the cause or design principle?
- Private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles.
- Spanning-tree root choice and path costs govern forwarding paths; unplanned priority changes can alter traffic patterns.
- MVRP registrations can persist where membership state or participation has not been updated consistently.
- MSTP maps VLANs into a smaller set of spanning-tree instances, providing scalable per-group path control.
Explanation
Correct Answer
C:MVRP registrations can persist where membership state or participation has not been updated consistently. The appropriate response is to inspect registration state and remove stale VLAN membership while preserving necessary registrations.
Incorrect Answers
A:“Private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles” 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.
B:“Spanning-tree root choice and path costs govern forwarding paths; unplanned priority changes can alter traffic patterns” belongs to a separate Ethernet Switching and Spanning Tree issue: a network replacement changes VSTP root elections, causing backup links to forward for a critical VLAN. It does not explain the condition tested here.
D:“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 network uses one VLAN-wide topology but wants two forwarding trees for different groups without an instance for every VLAN. It does not explain the condition tested here.
Question 311
Select THREE complementary corrective, verification, or preventive controls for this scenario: A one-to-many lecture stream is configured as separate unicast connections and saturates a WAN link to a remote campus.
- Backbone utilization reflects one upstream multicast copy per tree branch while interested receivers obtain the stream.
- Configure two unrelated RP mappings and assume their failover and source state stay identical automatically.
- Assume IGMP membership on the access switch alone builds an end-to-end PIM ASM tree.
- Enable the same full-bandwidth unicast copy to every receiver and call it multicast optimization.
- Measure receiver interest and multicast forwarding state before scaling new one-to-many services.
- Design a multicast distribution tree with explicit receiver memberships and test only the subscribed delivery paths.
Explanation
Correct Answers
A:Confirmation: Design a multicast distribution tree with explicit receiver memberships and test only the subscribed delivery paths.
E:Prevention of recurrence: IP multicast replicates streams at forwarding branches instead of requiring a separate source-to-receiver unicast stream.
F:Correction: IP multicast replicates streams at forwarding branches instead of requiring a separate source-to-receiver unicast stream.
Incorrect Answers
B:“Configure two unrelated RP mappings and assume their failover and source state stay identical automatically” is an unsafe response to a different problem: a second campus RP is deployed for availability but source-awareness synchronization is omitted where the design requires it. It is not a valid fix here.
C:“Assume IGMP membership on the access switch alone builds an end-to-end PIM ASM tree” is an unsafe response to a different problem: a PIM sparse-mode receiver has an IGMP join but no multicast traffic because its upstream router cannot resolve the rendezvous point. It is not a valid fix here.
D:“Enable the same full-bandwidth unicast copy to every receiver and call it multicast optimization” does not address IP multicast replicates streams at forwarding branches instead of requiring a separate source-to-receiver unicast stream.
Question 312
A network change is required for the following specific situation: A VXLAN overlay's BGP EVPN routes are present, but the underlay cannot route to a remote VTEP loopback. Which corrective action is most appropriate?
- Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally.
- 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.
- Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration.
Explanation
Correct Answer
C:VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state. Verify this by checking that the remote VTEP becomes reachable and encapsulated packets cross the fabric as intended.
Incorrect Answers
A:“Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally” belongs to a separate EVPN issue: a troubleshooting team expects EVPN Ethernet auto-discovery route Type 1 to carry all host MAC/IP bindings. It does not explain the condition tested here.
B:“Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement” belongs to a separate EVPN issue: a bridge domain has valid unicast Type 2 entries yet remote VTEPs do not discover a new participating segment for BUM forwarding. It does not explain the condition tested here.
D:“Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration” 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.
Question 313
To prevent recurrence of this precise networking failure, which practice should be adopted? A filter-based VLAN security design uses a rule that catches too many packets and steers legitimate devices into quarantine.
- Audit edge classifications and apply appropriate BPDU protection on true client-facing ports.
- Scope and monitor tunneled L2 control protocols to prevent control-plane abuse.
- Check policy coverage and unintended-match cases before activating filter-based steering.
- Keep explicit root priority policy and validate elections after device replacement.
Explanation
Correct Answer
C: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:“Audit edge classifications and apply appropriate BPDU protection on true client-facing ports” belongs to a separate Ethernet Switching and Spanning Tree issue: a campus mistakenly enables edge behavior on a switch-to-switch trunk and a loop appears when a backup link activates. It does not explain the condition tested here.
B:“Scope and monitor tunneled L2 control protocols to prevent control-plane abuse” belongs to a separate Ethernet Switching and Spanning Tree issue: a private L2 service must extend customer control protocols, yet the provider fabric consumes or drops the customer's BPDUs. It does not explain the condition tested here.
D:“Keep explicit root priority policy and validate elections after device replacement” 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 314
The team believes it has resolved this Junos issue: A campus has configured forwarding classes and schedulers but one uplink carries all traffic through default service because association is missing. Which observation best verifies the specific intended result?
- During controlled congestion, out-of-profile traffic experiences earlier drops than in-profile traffic.
- Measured guest ingress usage remains within policy and permitted business traffic is unaffected.
- Voice traffic receives the required scheduled service at the congested egress without starving other classes.
- Outgoing traffic conforms to the contracted rate with acceptable delay and fewer burst losses.
Explanation
Correct Answer
C:Voice traffic receives the required scheduled service at the congested egress without starving other classes. This checks the relevant result after associate the approved scheduler map with the correct egress interface and confirm class queue counters.
Incorrect Answers
A:“During controlled congestion, out-of-profile traffic experiences earlier drops than in-profile traffic” 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:“Measured guest ingress usage remains within policy and permitted business traffic is unaffected” belongs to a separate Class of Service (CoS) issue: a guest network should be rate-limited at ingress, but engineers configure only an egress shaper on the uplink. It does not explain the condition tested here.
D:“Outgoing traffic conforms to the contracted rate with acceptable delay and fewer burst losses” belongs to a separate Class of Service (CoS) issue: a branch link should pace scheduled traffic to a slower uplink yet the team only drops excess packets abruptly. It does not explain the condition tested here.
Question 315
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A multihop eBGP peer uses loopback addresses but its session times out when directly connected assumptions remain.
- Verify endpoint reachability and configure appropriate multihop session parameters and security controls.
- Increase the route's MED while leaving BGP transport reachability and hop settings incorrect.
- Assume the shortest AS path must win regardless of any LOCAL_PREF difference.
- Expect a locally set LOCAL_PREF value to propagate unchanged over standard eBGP to another AS.
- A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI.
Explanation
Correct Answers
A:Verify endpoint reachability and configure appropriate multihop session parameters and security controls. This addresses the dependency that multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints.
E:A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI. The specific steps required are to verify endpoint reachability and configure appropriate multihop session parameters and security controls.
Incorrect Answers
B:“Increase the route's MED while leaving BGP transport reachability and hop settings incorrect” does not address multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints.
C:“Assume the shortest AS path must win regardless of any LOCAL_PREF difference” is an unsafe response to a different problem: a branch dual-transit design sees the higher-preference provider route win even though its AS path has more hops. It is not a valid fix here.
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: a dual-homed site changes internal LOCAL_PREF but sees no change in the other autonomous system's inbound traffic choice. It is not a valid fix here.
Question 316
Which suggested shortcut would be especially unsafe for this exact situation? A PIM sparse-mode receiver has an IGMP join but no multicast traffic because its upstream router cannot resolve the rendezvous point.
- 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.
- Test multicast source-path behavior under each failover case, not only unicast ping.
- Assume IGMP membership on the access switch alone builds an end-to-end PIM ASM tree.
Explanation
Correct Answer
D:The tempting alternative fails because PIM sparse-mode ASM builds shared-tree state toward a reachable RP, and an incorrect RP mapping can prevent service. The supported action is to check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping.
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 an alternate upstream sends multicast on a path different from the router's route back to the source, causing RPF failures.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a redundant network changes the preferred route to the source while packets keep arriving on the other physical link.; it is not the unsafe shortcut described here.
Question 317
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: An alternate upstream sends multicast on a path different from the router's route back to the source, causing RPF failures.
- Enable the same full-bandwidth unicast copy to every receiver and call it multicast optimization.
- RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
- Turn off all RPF checking to accept duplicate or looping multicast packets from arbitrary links.
- Inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
- Assume an ASM (*,G) join identifies and restricts a unique approved source by itself.
Explanation
Correct Answers
B:RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces. The specific steps required are to inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
D:Inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection. This addresses the dependency that reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
Incorrect Answers
A:“Enable the same full-bandwidth unicast copy to every receiver and call it multicast optimization” is an unsafe response to a different problem: a trading-data sender needs to serve many local subscribers, but each listener receives its own redundant copy over the backbone. It is not a valid fix here.
C:“Turn off all RPF checking to accept duplicate or looping multicast packets from arbitrary links” does not address reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
E:“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.
Question 318
The team believes it has resolved this Junos issue: An ABR stops advertising a branch prefix into the backbone after an OSPF area-range summary is configured incorrectly. Which observation best verifies the specific intended result?
- A designated external default appears at downstream routers without leaking unrelated static prefixes.
- An OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0.
- The preferred primary route wins when healthy and the backup becomes active on a controlled failure.
- The backbone receives the intended aggregate and routers can reach all included component subnets.
Explanation
Correct Answer
D:The backbone receives the intended aggregate and routers can reach all included component subnets. This checks the relevant result after verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan.
Incorrect Answers
A:“A designated external default appears at downstream routers without leaking unrelated static prefixes” 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:“An OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0” 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.
C:“The preferred primary route wins when healthy and the backup becomes active on a controlled failure” belongs to a separate Interior Gateway Protocols (IGPs) issue: an OSPF policy update redistributes a route without an appropriate external metric, shifting traffic to a slow backup. It does not explain the condition tested here.
Question 319
A Junos enterprise team investigates this incident: A route-reflector topology loses an iBGP-advertised prefix because clients are not configured under the intended reflector cluster. Which technical explanation most directly identifies the cause or design principle?
- iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology.
- LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors.
- The default BGP AS-path loop check rejects routes containing the local autonomous system to prevent loops.
- MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
Explanation
Correct Answer
A:IBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology. The appropriate response is to inspect reflector/client relationships and cluster behavior, then correct the intended route-reflector configuration.
Incorrect Answers
B:“LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors” belongs to a separate Border Gateway Protocol (BGP) issue: an operator tries to make a remote AS prefer one inbound path using LOCAL_PREF that the remote eBGP peer never receives. It does not explain the condition tested here.
C:“The default BGP AS-path loop check rejects routes containing the local autonomous system to prevent loops” 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:“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.
Question 320
Select THREE complementary corrective, verification, or preventive controls for this scenario: A new IPv6 peering uses OSPFv3 on a retired VLAN unit rather than the active routed transit interface.
- Move OSPFv3 participation to the correct active interface and verify neighbor and IPv6 RIB state.
- Increase every external metric blindly without checking which path should win.
- Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically.
- Change only BGP keepalive values and assume OSPF timers automatically follow.
- An OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0.
- Validate active logical-interface mappings and IPv6 adjacency as part of change acceptance.
Explanation
Correct Answers
A:Correction: OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
E:Confirmation: Move OSPFv3 participation to the correct active interface and verify neighbor and IPv6 RIB state.
F:Prevention of recurrence: OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
Incorrect Answers
B:“Increase every external metric blindly without checking which path should win” is an unsafe response to a different problem: a branch receives two external paths with different metric-type assumptions after a policy change and prefers the wrong exit. It is not a valid fix here.
C:“Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically” does not address OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
D:“Change only BGP keepalive values and assume OSPF timers automatically follow” is an unsafe response to a different problem: an access-area adjacency drops after one device is changed to shorter OSPF Hello timers but its peer keeps prior settings. It is not a valid fix here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests