100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 660
Which suggested shortcut would be especially unsafe for this exact situation? A network uses one VLAN-wide topology but wants two forwarding trees for different groups without an instance for every VLAN.
- Create an independent VSTP instance for every VLAN without checking platform scaling limits.
- Track VLAN lifecycle and MVRP registration ownership as ports are decommissioned.
- Maintain representative match and nonmatch tests for filter-based VLAN policies.
- Document outer/inner VLAN roles and test tag stripping and preservation at service boundaries.
Explanation
Correct Answer
A:The tempting alternative fails because MSTP maps VLANs into a smaller set of spanning-tree instances, providing scalable per-group path control. The supported action is to create an approved MSTP region and VLAN-to-instance mapping, then verify root and port role behavior.
Incorrect Answers
B:That prevention measure relates to a dynamic VLAN is removed from one edge but stale MVRP registration keeps an unused VLAN active downstream.; 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 a service provider must carry multiple customer VLAN IDs transparently over one metro Ethernet handoff.; it is not the unsafe shortcut described here.
Question 661
A Junos enterprise team investigates this incident: A video source is known and receivers support IGMPv3, but engineers configure ASM and an RP unnecessarily for the source-specific application. Which technical explanation most directly identifies the cause or design principle?
- An RPF check is tied to the selected source path, so asymmetric arrival can invalidate otherwise reachable multicast traffic.
- Source-specific multicast uses (S,G) membership semantics and generally avoids ASM rendezvous-point discovery for that flow.
- Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
- IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication.
Explanation
Correct Answer
B:Source-specific multicast uses (S,G) membership semantics and generally avoids ASM rendezvous-point discovery for that flow. The appropriate response is to select an appropriate SSM group range and verify source-specific IGMPv3/PIM signaling on the supported platform.
Incorrect Answers
A:“An RPF check is tied to the selected source path, so asymmetric arrival can invalidate otherwise reachable multicast traffic” 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.
C:“Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root” belongs to a separate IP Multicast issue: multicast packets arrive on the wrong uplink after unicast routing changes and are dropped by the campus core. It does not explain the condition tested here.
D:“IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication” 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 662
A Junos enterprise team investigates this incident: A branch default-route injection stops after a policy matches OSPF-learned routes instead of the intended local static. Which technical explanation most directly identifies the cause or design principle?
- An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology.
- Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate.
- Routing-policy match criteria must align with the source route type and the intended OSPF export behavior.
- OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
Explanation
Correct Answer
C:Routing-policy match criteria must align with the source route type and the intended OSPF export behavior. The appropriate response is to inspect the active local default and export term conditions; match only the authorized static default source.
Incorrect Answers
A:“An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology” belongs to a separate Interior Gateway Protocols (IGPs) issue: OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout. It does not explain the condition tested here.
B:“Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate” 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:“OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication” belongs to a separate Interior Gateway Protocols (IGPs) issue: an IPv6-only branch has OSPFv3 Hellos on the wrong logical unit after interface renumbering, so no IPv6 routes appear. It does not explain the condition tested here.
Question 663
A Junos enterprise team investigates this incident: A team wrongly concludes OSPFv3 failed when inet6.0 shows a static route active and the OSPFv3 candidate inactive. Which technical explanation most directly identifies the cause or design principle?
- Making a link passive suppresses OSPF adjacency formation even when its prefix remains eligible for advertisement.
- Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate.
- OSPF database-description exchange can stall when adjacent interfaces disagree on MTU even though basic Hello connectivity exists.
- OSPF neighbors must agree on the area context to form adjacency on the common link.
Explanation
Correct Answer
B:Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate. The appropriate response is to inspect inet6.0 route detail and route preferences before changing OSPFv3 neighbor configuration.
Incorrect Answers
A:“Making a link passive suppresses OSPF adjacency formation even when its prefix remains eligible for advertisement” belongs to a separate Interior Gateway Protocols (IGPs) issue: an OSPF neighbor remains Down because the routed transit interface was left passive after a site template rollout. It does not explain the condition tested here.
C:“OSPF database-description exchange can stall when adjacent interfaces disagree on MTU even though basic Hello connectivity exists” belongs to a separate Interior Gateway Protocols (IGPs) issue: a core-router replacement leaves an OSPF adjacency stuck exchanging database descriptions, while the two ends have different Layer 3 MTUs. It does not explain the condition tested here.
D:“OSPF neighbors must agree on the area context to form adjacency on the common link” belongs to a separate Interior Gateway Protocols (IGPs) issue: a campus OSPF interface is accidentally placed in area 0 while its neighbor advertises a nonbackbone area, preventing a Full adjacency. It does not explain the condition tested here.
Question 664
Which suggested shortcut would be especially unsafe for this exact situation? A new endpoint MAC is learned at a remote VTEP but never reaches the receiving leaf's EVPN control-plane table.
- Test multihoming election and per-VLAN failover after attaching new dual-homed devices.
- Audit ESI consistency and platform-supported multihoming mode across paired leafs.
- Include underlay loopback reachability and MTU checks in VXLAN overlay deployment QA.
- Assume a data-plane VXLAN tunnel automatically updates every remote leaf's EVPN MAC reachability without Type 2 control-plane exchange.
Explanation
Correct Answer
D:The tempting alternative fails because EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane. The supported action is to check relevant BGP EVPN Type 2 advertisements, MAC mobility updates and import policy for the affected bridge domain.
Incorrect Answers
A: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.
B:That prevention measure relates to a shared Ethernet segment loses its fast convergence properties after an ESI-LAG peer receives an inconsistent configuration.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a new leaf imports VNI reachability but packets disappear because its VXLAN tunnel endpoint IP is unresolved.; it is not the unsafe shortcut described here.
Question 665
A network change is required for the following specific situation: Equal candidate BGP routes are visible but no multipath forwarding entry is installed because eligibility or policy differs. Which corrective action is most appropriate?
- Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
- Read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence.
- Put specific deny conditions before broad acceptance, and test the policy with representative routes.
- Compare BGP best-path and multipath eligibility conditions, then enable approved multipath behavior and validate forwarding.
Explanation
Correct Answer
D:BGP equal-cost multipath requires appropriate configured support and matching eligible path attributes, not merely two established sessions. Verify this by checking that the routing and forwarding tables show the intended multiple next hops only for qualifying routes.
Incorrect Answers
A:“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: 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.
B:“Read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence” belongs to a separate Border Gateway Protocol (BGP) issue: an engineer incorrectly assumes a lower MED overrides a larger LOCAL_PREF, when both transit candidates are eligible. It does not explain the condition tested here.
C:“Put specific deny conditions before broad acceptance, and test the policy with representative routes” belongs to a separate Border Gateway Protocol (BGP) issue: a route with a permissive policy term is accepted before a later deny term can block it. It does not explain the condition tested here.
Question 666
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A powered endpoint detects a Junos switch but fails to negotiate voice prioritization because only ordinary LLDP is enabled.
- Packet and operational views show the required LLDP-MED telephony TLVs at the correct interface.
- Allocate identical priority to all PoE consumers and assume emergency devices receive preferential power.
- Put the phone and PC on one unrestricted VLAN to avoid checking voice VLAN tagging.
- Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access.
- Assume enabling ordinary LLDP globally is guaranteed to activate every LLDP-MED policy automatically.
Explanation
Correct Answers
A:Packet and operational views show the required LLDP-MED telephony TLVs at the correct interface. The specific steps required are to review LLDP and LLDP-MED operational status and enable supported MED policy for phone access.
D:Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access. This addresses the dependency that base LLDP discovery and LLDP-MED telephony advertisement are distinct capabilities and may require separate enablement.
Incorrect Answers
B:“Allocate identical priority to all PoE consumers and assume emergency devices receive preferential power” is an unsafe response to a different problem: a switch assigns equal PoE power priority to every port and disconnects an emergency phone before low-priority signage during a power shortage. It is not a valid fix here.
C:“Put the phone and PC on one unrestricted VLAN to avoid checking voice VLAN tagging” is an unsafe response to a different problem: 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 a valid fix here.
E:“Assume enabling ordinary LLDP globally is guaranteed to activate every LLDP-MED policy automatically” does not address base LLDP discovery and LLDP-MED telephony advertisement are distinct capabilities and may require separate enablement.
Question 667
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: An OSPF neighbor remains Down because the routed transit interface was left passive after a site template rollout.
- Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically.
- Hellos are observed in the routing adjacency and a Full neighbor appears on the intended port.
- Record a successful IPv4 echo response as conclusive proof that OSPFv3 is healthy.
- Remove passive behavior only from the approved router-to-router transit link and check Hello and neighbor states.
- Make every edge interface active to OSPF regardless of whether a routing peer exists.
Explanation
Correct Answers
B:Hellos are observed in the routing adjacency and a Full neighbor appears on the intended port. The specific steps required are to remove passive behavior only from the approved router-to-router transit link and check Hello and neighbor states.
D:Remove passive behavior only from the approved router-to-router transit link and check Hello and neighbor states. This addresses the dependency that making a link passive suppresses OSPF adjacency formation even when its prefix remains eligible for advertisement.
Incorrect Answers
A:“Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically” is an unsafe response to a different problem: an IPv6-only branch has OSPFv3 Hellos on the wrong logical unit after interface renumbering, so no IPv6 routes appear. 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 IPv6 branch outage is misdiagnosed using only IPv4 pings, despite OSPFv3 neighbors using IPv6 link-local messaging. It is not a valid fix here.
E:“Make every edge interface active to OSPF regardless of whether a routing peer exists” does not address making a link passive suppresses OSPF adjacency formation even when its prefix remains eligible for advertisement.
Question 668
A network change is required for the following specific situation: A dual-homed site changes internal LOCAL_PREF but sees no change in the other autonomous system's inbound traffic choice. Which corrective action is most appropriate?
- Inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
- Select a permitted inbound traffic-engineering mechanism with the provider, such as suitable AS-path prepending or agreed communities.
- Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
- Inspect hidden-route reason, incoming attributes and import-policy decisions, then correct the authorized match.
Explanation
Correct Answer
B:LOCAL_PREF is an intra-AS BGP attribute, not a value routinely advertised to external BGP neighbors. Verify this by checking that external peer advertisements show the intended supported attributes and inbound traffic is measured.
Incorrect Answers
A:“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: 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.
C:“Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy” belongs to a separate Border Gateway Protocol (BGP) issue: an IPv6 transit prefix is hidden because its next-hop address is absent from the correct IPv6 routing table. It does not explain the condition tested here.
D:“Inspect hidden-route reason, incoming attributes and import-policy decisions, then correct the authorized match” belongs to a separate Border Gateway Protocol (BGP) issue: a Junos route is hidden by import policy, but the team troubleshoots only local physical interfaces. It does not explain the condition tested here.
Question 669
A Junos enterprise team investigates this incident: A business wants out-of-profile marked traffic to drop earlier than in-profile traffic within one forwarding class. Which technical explanation most directly identifies the cause or design principle?
- Packet loss priority differentiates drop susceptibility within a forwarding class and works with the configured queue/drop behavior.
- Shaping buffers and schedules outgoing traffic to a rate, unlike policing which marks or discards traffic exceeding a contract.
- Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings.
- CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings.
Explanation
Correct Answer
A:Packet loss priority differentiates drop susceptibility within a forwarding class and works with the configured queue/drop behavior. The appropriate response is to map the two packet categories to the intended PLP levels and verify drop-profile response.
Incorrect Answers
B:“Shaping buffers and schedules outgoing traffic to a rate, unlike policing which marks or discards traffic exceeding a contract” 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:“Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings” 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:“CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings” belongs to a separate Class of Service (CoS) issue: a branch egress rewriter incorrectly gives bulk backups the same DSCP as real-time voice. It does not explain the condition tested here.
Question 670
Which suggested shortcut would be especially unsafe for this exact situation? A campus summarization change hides a needed subnet because the configured address range omits it.
- Validate active logical-interface mappings and IPv6 adjacency as part of change acceptance.
- Record both LSDB presence and local RIB installation in OSPF troubleshooting runbooks.
- Include a checklist of advertised IPv6 service and loopback addresses in OSPFv3 acceptance.
- Advertise an arbitrary wide aggregate that includes unrelated networks to make the missing route disappear.
Explanation
Correct Answer
D:The tempting alternative fails because area summarization scope must correctly cover the intended component networks; the wrong range can suppress or misrepresent reachability. The supported action is to verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan.
Incorrect Answers
A:That prevention measure relates to a new IPv6 peering uses OSPFv3 on a retired VLAN unit rather than the active routed transit interface.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a core node shows a missing route while remote LSDBs include the corresponding external LSA after a local policy change.; it is not the unsafe shortcut described here.
C:That prevention measure relates to OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout.; it is not the unsafe shortcut described here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests