100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 321
The team believes it has resolved this Junos issue: A handset follows LLDP-MED voice VLAN advertisement but sends SIP media with the wrong priority marking for the campus QoS design. Which observation best verifies the specific intended result?
- The phone receives stable negotiated power and the chassis stays within its supported budget under peak load.
- Tagged voice packets retain the intended service class through the access and aggregation paths.
- The phone or location service reports the correct emergency location for the new access port.
- The handset learns the authorized voice VLAN and traffic is tagged and prioritized according to design.
Explanation
Correct Answer
B:Tagged voice packets retain the intended service class through the access and aggregation paths. This checks the relevant result after verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media.
Incorrect Answers
A:“The phone receives stable negotiated power and the chassis stays within its supported budget under peak load” belongs to a separate IP Telephony Features issue: a high-power phone intermittently reboots whenever all powered endpoints on a switch chassis start simultaneously. It does not explain the condition tested here.
C:“The phone or location service reports the correct emergency location for the new access port” belongs to a separate IP Telephony Features issue: an IP phone uses the wrong location information for emergency response after a switch move. It does not explain the condition tested here.
D:“The handset learns the authorized voice VLAN and traffic is tagged and prioritized according to design” belongs to a separate IP Telephony Features issue: a newly deployed IP phone joins the data network because the switch does not advertise the intended voice VLAN through LLDP-MED. It does not explain the condition tested here.
Question 322
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: An IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement.
- Use only the MED field as guaranteed proof of the selected route regardless of preceding BGP attributes.
- Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
- Point to a successful IPv4 traceroute as sufficient proof an IPv6 BGP next hop resolves.
- Increase the route's MED while leaving BGP transport reachability and hop settings incorrect.
- The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop.
Explanation
Correct Answers
B:Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy. This addresses the dependency that BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops.
E:The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop. The specific steps required are to check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Incorrect Answers
A:“Use only the MED field as guaranteed proof of the selected route regardless of preceding BGP attributes” is an unsafe response to a different problem: two equal LOCAL_PREF and AS-path candidates remain tied until MED influences the choice under the applicable comparison rules. It is not a valid fix here.
C:“Point to a successful IPv4 traceroute as sufficient proof an IPv6 BGP next hop resolves” does not address BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops.
D:“Increase the route's MED while leaving BGP transport reachability and hop settings incorrect” is an unsafe response to a different problem: a multihop eBGP peer uses loopback addresses but its session times out when directly connected assumptions remain. It is not a valid fix here.
Question 323
The team believes it has resolved this Junos issue: A private L2 service must extend customer control protocols, yet the provider fabric consumes or drops the customer's BPDUs. Which observation best verifies the specific intended result?
- Only the intended endpoint class is moved while nonmatching hosts retain correct access.
- Community members can communicate as intended while cross-community access remains blocked.
- Isolated clients reach the shared service but cannot communicate laterally with other isolated clients.
- The customer control protocol reaches the far endpoint without altering the provider's own spanning-tree topology.
Explanation
Correct Answer
D:The customer control protocol reaches the far endpoint without altering the provider's own spanning-tree topology. This checks the relevant result after configure supported L2PT for the required control protocols and verify provider-edge handling.
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: 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:“Community members can communicate as intended while cross-community access remains blocked” belongs to a separate Ethernet Switching and Spanning Tree issue: a switch rollout splits a team that should communicate within one PVLAN community, while protecting it from another community. It does not explain the condition tested here.
C:“Isolated clients reach the shared service but cannot communicate laterally with other isolated clients” 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 324
A network change is required for the following specific situation: A multicast team changes unicast routing yet an engineered multicast RPF table still points to an obsolete next hop. Which corrective action is most appropriate?
- Check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping.
- Inspect MSDP peer state and source-active information, then configure the permitted peer relationships.
- Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
- Identify the configured RPF table and verify the source route and next hop in that table before updating the multicast policy.
Explanation
Correct Answer
D:Junos multicast RPF may use a dedicated routing table, so the effective RPF path must be inspected, not guessed from unicast traffic. Verify this by checking that the selected upstream RPF neighbor and packet arrival interface agree, restoring intended multicast flow.
Incorrect Answers
A:“Check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping” belongs to a separate IP Multicast issue: a PIM sparse-mode receiver has an IGMP join but no multicast traffic because its upstream router cannot resolve the rendezvous point. It does not explain the condition tested here.
B:“Inspect MSDP peer state and source-active information, then configure the permitted peer relationships” belongs to a separate IP Multicast issue: a receiver domain requires discovery of sources known behind another RP, yet inter-RP source information exchange is absent. It does not explain the condition tested here.
C:“Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports” 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.
Question 325
Which suggested shortcut would be especially unsafe for this exact situation? A VSTP network intended to send voice and data VLANs over different active paths instead blocks both on the same uplink.
- Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews.
- Assume setting one global RSTP root automatically produces independently chosen roots for every VSTP VLAN.
- Maintain representative match and nonmatch tests for filter-based VLAN policies.
- Document primary/secondary VLAN mappings and test permitted peer groups and isolation boundaries.
Explanation
Correct Answer
B:The tempting alternative fails because VSTP provides per-VLAN spanning-tree behavior for compatibility and path control when the design and platform support it. The supported action is to inspect VSTP VLAN membership, root priority and port roles, then repair the intended per-VLAN root arrangement.
Incorrect Answers
A:That prevention measure relates to 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 is not the unsafe shortcut described here.
C:That prevention measure relates to 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 is not the unsafe shortcut described here.
D:That prevention measure relates to members of the same trusted workgroup are accidentally placed in isolated rather than community PVLAN ports and lose peer communication.; it is not the unsafe shortcut described here.
Question 326
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A switch with an unexpectedly low bridge priority becomes MSTP root and redirects aggregation traffic through an access closet.
- Treat ordinary VLAN membership as equivalent to isolation between every port inside that VLAN.
- Assume the physically fastest switch is always elected as spanning-tree root irrespective of priority.
- Root and forwarding roles match the approved topology under normal and failover conditions.
- Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately.
- Remove customer inner VLAN tags at entry and assume overlapping customer IDs remain isolated.
Explanation
Correct Answers
C:Root and forwarding roles match the approved topology under normal and failover conditions. The specific steps required are to compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately.
D:Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately. This addresses the dependency that spanning-tree root choice and path costs govern forwarding paths; unplanned priority changes can alter traffic patterns.
Incorrect Answers
A:“Treat ordinary VLAN membership as equivalent to isolation between every port inside that VLAN” is an unsafe response to a different problem: a lab uses one primary VLAN for many tenants but isolated access ports can still exchange Layer 2 frames after a misconfiguration. It is not a valid fix here.
B:“Assume the physically fastest switch is always elected as spanning-tree root irrespective of priority” does not address spanning-tree root choice and path costs govern forwarding paths; unplanned priority changes can alter traffic patterns.
E:“Remove customer inner VLAN tags at entry and assume overlapping customer IDs remain isolated” is an unsafe response to a different problem: an aggregation network sees customer VLAN IDs collide because several tenants share the same single-tagged provider infrastructure. It is not a valid fix here.
Question 327
Which suggested shortcut would be especially unsafe for this exact situation? A campus has configured forwarding classes and schedulers but one uplink carries all traffic through default service because association is missing.
- Test marking, PLP assignment and drop policy together rather than checking only DSCP fields.
- Test ingress classification separately from egress rewrite at every trust boundary.
- Create a scheduler definition in configuration but never bind the scheduler map to egress interfaces.
- Audit DSCP preservation and remarking at untrusted edge boundaries.
Explanation
Correct Answer
C:The tempting alternative fails because egress scheduling requires the intended schedulers and their mapping to be applied on the outgoing interface. The supported action is to associate the approved scheduler map with the correct egress interface and confirm class queue counters.
Incorrect Answers
A:That prevention measure relates to a business wants out-of-profile marked traffic to drop earlier than in-profile traffic within one forwarding class.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a boundary router classifies EF voice traffic correctly but sends outbound DSCP zero, so downstream devices undo priority handling.; it is not the unsafe shortcut described here.
D:That prevention measure relates to a customer access switch trusts external CoS bits and redistributes high-priority markings to all guest traffic.; it is not the unsafe shortcut described here.
Question 328
A network change is required for the following specific situation: Multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core. Which corrective action is most appropriate?
- Update receiver memberships to use the approved source and group, and validate end-to-end (S,G) trees.
- Check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping.
- Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
- Inspect multicast RPF state and the routing table used for source resolution, then correct the underlay or allowed RPF selection.
Explanation
Correct Answer
D:Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root. Verify this by checking that RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
Incorrect Answers
A:“Update receiver memberships to use the approved source and group, and validate end-to-end (S,G) trees” belongs to a separate IP Multicast issue: a streaming application expects a source-specific group to accept traffic from any origin, contrary to its (S,G) subscription. It does not explain the condition tested here.
B:“Check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping” belongs to a separate IP Multicast issue: an ASM video distribution has valid listener memberships yet PIM joins never converge toward the configured RP. It does not explain the condition tested here.
C:“Inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports” 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.
Question 329
Select THREE complementary corrective, verification, or preventive controls for this scenario: A printer's MAC address is duplicated by an unauthorized endpoint that obtains the same weak MAC-based policy.
- Only the inventoried device has the expected limited connectivity; rogue or unknown hardware is denied.
- Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls.
- Allow the weakest matching authentication method to grant full access regardless of prior EAP outcomes.
- Add a static DNS record and assume it substitutes for captive-portal authentication and authorization.
- Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions.
- Treat a MAC address alone as cryptographic proof of device ownership and elevate access privileges.
Explanation
Correct Answers
A:Confirmation: Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls.
B:Correction: MAC-based identity is tied to the observed hardware address and can be spoofed; it is not strong user authentication.
E:Prevention of recurrence: MAC-based identity is tied to the observed hardware address and can be spoofed; it is not strong user authentication.
Incorrect Answers
C:“Allow the weakest matching authentication method to grant full access regardless of prior EAP outcomes” is an unsafe response to a different problem: two authentication methods are enabled on a shared switch port but fallback ordering bypasses a successful 802.1X result. It is not a valid fix here.
D:“Add a static DNS record and assume it substitutes for captive-portal authentication and authorization” is an unsafe response to a different problem: guest users on an EX switch see no captive login page because browser HTTP redirects are not being applied on the intended VLAN. It is not a valid fix here.
F:“Treat a MAC address alone as cryptographic proof of device ownership and elevate access privileges” does not address MAC-based identity is tied to the observed hardware address and can be spoofed; it is not strong user authentication.
Question 330
The team believes it has resolved this Junos issue: A backup traffic queue consumes too much buffer and latency-sensitive applications starve during peak bursts. Which observation best verifies the specific intended result?
- Outgoing traffic conforms to the contracted rate with acceptable delay and fewer burst losses.
- 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.
- During controlled congestion, out-of-profile traffic experiences earlier drops than in-profile traffic.
Explanation
Correct Answer
B:Queue depth, latency and drop statistics meet documented objectives during realistic traffic load. This checks the relevant result after review queue buffer and scheduler allocations against traffic measurements and apply a bounded adjustment.
Incorrect Answers
A:“Outgoing traffic conforms to the contracted rate with acceptable delay and fewer burst losses” belongs to a separate Class of Service (CoS) issue: a WAN customer requires smooth outbound transmission but an ingress drop policer creates unnecessary burst loss. It does not explain the condition tested here.
C:“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.
D:“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.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests