100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 960
A network change is required for the following specific situation: A legacy interop design needs separate per-VLAN spanning-tree compatibility but all VLANs inherit one unsuitable tree. Which corrective action is most appropriate?
- Inspect match conditions and attachment point, then change the approved filter-based VLAN steering rule.
- Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated.
- Inspect registration state and remove stale VLAN membership while preserving necessary registrations.
- Inspect VSTP VLAN membership, root priority and port roles, then repair the intended per-VLAN root arrangement.
Explanation
Correct Answer
D:VSTP provides per-VLAN spanning-tree behavior for compatibility and path control when the design and platform support it. Verify this by checking that selected voice and data VLANs use the approved active links without loops.
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.
B:“Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated” 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.
C:“Inspect registration state and remove stale VLAN membership while preserving necessary registrations” belongs to a separate Ethernet Switching and Spanning Tree issue: a campus migration removes a VLAN at the source while a trunk continues advertising it unexpectedly. It does not explain the condition tested here.
Question 961
Select THREE complementary corrective, verification, or preventive controls for this scenario: Multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core.
- Check multicast and unicast topology alignment whenever routing paths or metrics change.
- Inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
- Turn off all RPF checking to accept duplicate or looping multicast packets from arbitrary links.
- Assume an ASM (*,G) join identifies and restricts a unique approved source by itself.
- Configure two unrelated RP mappings and assume their failover and source state stay identical automatically.
- RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
Explanation
Correct Answers
A:Prevention of recurrence: Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
B:Correction: Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
F:Confirmation: Inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
Incorrect Answers
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.
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.
E:“Configure two unrelated RP mappings and assume their failover and source state stay identical automatically” is an unsafe response to a different problem: an Anycast RP design uses two RP addresses that do not share the intended anycast identity, producing inconsistent joins. It is not a valid fix here.
Question 962
Which suggested shortcut would be especially unsafe for this exact situation? A one-to-many lecture stream is configured as separate unicast connections and saturates a WAN link to a remote campus.
- Enable the same full-bandwidth unicast copy to every receiver and call it multicast optimization.
- Monitor IGMP membership churn and snooping state when moving clients between VLANs.
- Document whether multicast RPF uses inet.0 or inet.2 and verify after topology changes.
- Test RP failover and synchronization behavior before expanding Anycast RP.
Explanation
Correct Answer
A:The tempting alternative fails because IP multicast replicates streams at forwarding branches instead of requiring a separate source-to-receiver unicast stream. The supported action is to design a multicast distribution tree with explicit receiver memberships and test only the subscribed delivery paths.
Incorrect Answers
B:That prevention measure relates to an access VLAN floods every multicast packet because IGMP snooping state was lost during migration.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a multicast team changes unicast routing yet an engineered multicast RPF table still points to an obsolete next hop.; it is not the unsafe shortcut described here.
D:That prevention measure relates to a second campus RP is deployed for availability but source-awareness synchronization is omitted where the design requires it.; it is not the unsafe shortcut described here.
Question 963
The team believes it has resolved this Junos issue: A redundant L2 topology creates a broadcast storm after an edge port connected to another switch is treated as an endpoint. Which observation best verifies the specific intended result?
- Only the intended endpoint class is moved while nonmatching hosts retain correct access.
- The VLAN registration propagates to the intended downstream trunk and reaches its member ports.
- The redundant topology converges without sustained broadcast loops during link-failure testing.
- Two customers can use overlapping inner VLAN numbers without traffic mixing on the transport.
Explanation
Correct Answer
C:The redundant topology converges without sustained broadcast loops during link-failure testing. This checks the relevant result after remove incorrect edge treatment, validate BPDU reception and restore loop-free port roles.
Incorrect Answers
A:“Only the intended endpoint class is moved while nonmatching hosts retain correct access” belongs to a separate Ethernet Switching and Spanning Tree issue: an ingress classification filter for one terminal type inadvertently redirects other hosts using the same uplink. It does not explain the condition tested here.
B:“The VLAN registration propagates to the intended downstream trunk and reaches its member ports” belongs to a separate Ethernet Switching and Spanning Tree issue: a shared uplink carries dynamically registered VLANs until one device has MVRP disabled during an upgrade. It does not explain the condition tested here.
D:“Two customers can use overlapping inner VLAN numbers without traffic mixing on the transport” belongs to a separate Ethernet Switching and Spanning Tree issue: an aggregation network sees customer VLAN IDs collide because several tenants share the same single-tagged provider infrastructure. It does not explain the condition tested here.
Question 964
A Junos enterprise team investigates this incident: A transit peering is moved off directly connected interface IPs to loopbacks yet the TTL and reachability design are not updated. Which technical explanation most directly identifies the cause or design principle?
- Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints.
- For eligible BGP candidates, LOCAL_PREF comparison precedes AS-path length, so AS-path length alone does not determine the winner.
- Communities are policy metadata; tagging does not enforce advertisement restrictions unless a matching policy acts on it.
- LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors.
Explanation
Correct Answer
A:Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints. The appropriate response is to verify endpoint reachability and configure appropriate multihop session parameters and security controls.
Incorrect Answers
B:“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 branch dual-transit design sees the higher-preference provider route win even though its AS path has more hops. It does not explain the condition tested here.
C:“Communities are policy metadata; tagging does not enforce advertisement restrictions unless a matching policy acts on it” belongs to a separate Border Gateway Protocol (BGP) issue: a provider-facing policy stops honoring a route-tag community after a new import policy changes the attached communities. It does not explain the condition tested here.
D:“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: 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.
Question 965
Select THREE complementary corrective, verification, or preventive controls for this scenario: A RADIUS server reports no Access-Request for a silent legacy terminal, while switch timers show no EAP response.
- Inspect packet exchange and classify the endpoint before selecting a supported fallback method.
- Rotate every user's password without checking whether the endpoint sent an EAP response at all.
- Require the scanner to open a login web page even though the device has no web client.
- Separate EAP silence, reject and timeout counters in authentication operational monitoring.
- Configure unrestricted access as the universal RADIUS-outage fallback for sensitive access ports.
- The observed authentication state identifies missing supplicant response, and the approved method onboards the endpoint.
Explanation
Correct Answers
A:Correction: Supplicant absence is a distinct failure from an invalid credential or unreachable authentication server.
D:Prevention of recurrence: Supplicant absence is a distinct failure from an invalid credential or unreachable authentication server.
F:Confirmation: Inspect packet exchange and classify the endpoint before selecting a supported fallback method.
Incorrect Answers
B:“Rotate every user's password without checking whether the endpoint sent an EAP response at all” does not address supplicant absence is a distinct failure from an invalid credential or unreachable authentication server.
C:“Require the scanner to open a login web page even though the device has no web client” is an unsafe response to a different problem: a captive portal requirement is applied to a headless barcode scanner that has no web browser to follow its redirect. It is not a valid fix here.
E:“Configure unrestricted access as the universal RADIUS-outage fallback for sensitive access ports” is an unsafe response to a different problem: after a RADIUS outage, the access switch opens ports broadly instead of applying the approved restricted server-fail VLAN. It is not a valid fix here.
Question 966
A Junos enterprise team investigates this incident: A Q-in-Q service works across transport but the far-end access handoff presents unexpected double tags. Which technical explanation most directly identifies the cause or design principle?
- Overbroad match conditions can cause unauthorized VLAN steering and affect both security and reachability.
- Filter-based VLAN assignment depends on correctly matching the selected traffic and applying the filter at the right ingress point.
- Private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles.
- Q-in-Q requires deliberate tagging and untagging at service boundaries, with customer tags retained according to the handoff contract.
Explanation
Correct Answer
D:Q-in-Q requires deliberate tagging and untagging at service boundaries, with customer tags retained according to the handoff contract. The appropriate response is to inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation.
Incorrect Answers
A:“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.
B:“Filter-based VLAN assignment depends on correctly matching the selected traffic and applying the filter at the right ingress point” belongs to a separate Ethernet Switching and Spanning Tree issue: a campus onboarding policy puts cameras on the normal data VLAN even though a targeted filter-based VLAN should steer them. It does not explain the condition tested here.
C:“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.
Question 967
To prevent recurrence of this precise networking failure, which practice should be adopted? An alternate upstream sends multicast on a path different from the router's route back to the source, causing RPF failures.
- Monitor IGMP membership churn and snooping state when moving clients between VLANs.
- Test RP failover and synchronization behavior before expanding Anycast RP.
- Run both allow and deny group tests against multicast policy whenever prefixes are revised.
- Check multicast and unicast topology alignment whenever routing paths or metrics change.
Explanation
Correct Answer
D:Check multicast and unicast topology alignment whenever routing paths or metrics change. This guards against reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
Incorrect Answers
A:“Monitor IGMP membership churn and snooping state when moving clients between VLANs” 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.
B:“Test RP failover and synchronization behavior before expanding Anycast RP” belongs to a separate IP Multicast issue: an Anycast RP design uses two RP addresses that do not share the intended anycast identity, producing inconsistent joins. It does not explain the condition tested here.
C:“Run both allow and deny group tests against multicast policy whenever prefixes are revised” belongs to a separate IP Multicast issue: an edge router uses a broad multicast filter that blocks valid collaboration groups alongside restricted lab streams. It does not explain the condition tested here.
Question 968
A network change is required for the following specific situation: A switch assigns a misconfigured laptop with incorrect EAP credentials to a VLAN intended only for devices that never attempt 802.1X. Which corrective action is most appropriate?
- Check authentication result classification and map the rejected user to an appropriate deny or reject response.
- Assign the authenticated device to the authorized restricted network profile and verify effective VLAN/filter.
- Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls.
- Choose a documented compatible nonbrowser method such as supported MAC RADIUS under narrow access controls.
Explanation
Correct Answer
A:Guest, server-reject and server-fail outcomes represent different causes and require distinct supported policies. Verify this by checking that a nonresponding guest gets its intended limited VLAN while invalid credentials never receive guest privilege.
Incorrect Answers
B:“Assign the authenticated device to the authorized restricted network profile and verify effective VLAN/filter” belongs to a separate Layer 2 Authentication and Access Control issue: a legacy printer can join after MAC authentication yet is allowed to reach sensitive management segments. It does not explain the condition tested here.
C:“Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls” belongs to a separate Layer 2 Authentication and Access Control issue: a printer's MAC address is duplicated by an unauthorized endpoint that obtains the same weak MAC-based policy. It does not explain the condition tested here.
D:“Choose a documented compatible nonbrowser method such as supported MAC RADIUS under narrow access controls” belongs to a separate Layer 2 Authentication and Access Control issue: a noninteractive sensor is trapped in captive-portal onboarding because operators selected browser authentication for all endpoints. It does not explain the condition tested here.
Question 969
To prevent recurrence of this precise networking failure, which practice should be adopted? A PIM sparse-mode receiver has an IGMP join but no multicast traffic because its upstream router cannot resolve the rendezvous point.
- Document ASM/SSM selection and receiver-version prerequisites before multicast deployment.
- Run both allow and deny group tests against multicast policy whenever prefixes are revised.
- Maintain consistent RP mappings and failover tests across multicast routers.
- Test multicast source-path behavior under each failover case, not only unicast ping.
Explanation
Correct Answer
C:Maintain consistent RP mappings and failover tests across multicast routers. This guards against PIM sparse-mode ASM builds shared-tree state toward a reachable RP, and an incorrect RP mapping can prevent service.
Incorrect Answers
A:“Document ASM/SSM selection and receiver-version prerequisites before multicast deployment” belongs to a separate IP Multicast issue: a controlled one-source data feed requires group membership constrained by both source and group, not arbitrary senders. It does not explain the condition tested here.
B:“Run both allow and deny group tests against multicast policy whenever prefixes are revised” belongs to a separate IP Multicast issue: an edge router uses a broad multicast filter that blocks valid collaboration groups alongside restricted lab streams. It does not explain the condition tested here.
D:“Test multicast source-path behavior under each failover case, not only unicast ping” 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.
Question 970
Which suggested shortcut would be especially unsafe for this exact situation? A VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side.
- Include encapsulation headroom and path MTU tests in EVPN-VXLAN design validation.
- Test multihoming election and per-VLAN failover after attaching new dual-homed devices.
- Maintain a central VNI registry and test cross-tenant isolation on each leaf rollout.
- Treat a single learned MAC/IP Type 2 route as guaranteed proof of correct BUM participation for every VTEP.
Explanation
Correct Answer
D:The tempting alternative fails because EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set. The supported action is to inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement.
Incorrect Answers
A:That prevention measure relates to an EVPN-VXLAN frame is dropped over a path where the IP underlay MTU was sized only for unencapsulated Ethernet payloads.; it is not the unsafe shortcut described here.
B:That prevention measure relates to an EVPN multihomed endpoint creates duplicate forwarding when two leafs both forward the same BUM traffic without appropriate split-horizon behavior.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a campus extension carries the right VXLAN outer header but directs frames to the wrong tenant bridge domain due to bad VNI mapping.; it is not the unsafe shortcut described here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests