100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 880
A Junos enterprise team investigates this incident: An EVPN multihomed endpoint creates duplicate forwarding when two leafs both forward the same BUM traffic without appropriate split-horizon behavior. Which technical explanation most directly identifies the cause or design principle?
- EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane.
- EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set.
- VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state.
- EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops.
Explanation
Correct Answer
D:EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops. The appropriate response is to inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration.
Incorrect Answers
A:“EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane” belongs to a separate EVPN issue: a host moves between leafs and the destination leaf still forwards toward the previous MAC location. It does not explain the condition tested here.
B:“EVPN Type 3 inclusive multicast routes announce interested VTEPs for a broadcast domain's BUM replication set” belongs to a separate EVPN issue: a VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side. It does not explain the condition tested here.
C:“VXLAN encapsulates overlay traffic across an IP underlay; VTEP reachability is necessary even with valid BGP EVPN control-plane state” belongs to a separate EVPN issue: a VXLAN overlay's BGP EVPN routes are present, but the underlay cannot route to a remote VTEP loopback. It does not explain the condition tested here.
Question 881
A network change is required for the following specific situation: An 802.1Q trunk carries customer data through a provider Ethernet segment but fails to forward the required spanning-tree control frames transparently. Which corrective action is most appropriate?
- Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated.
- Inspect primary and secondary private VLAN roles and port membership; restore approved isolated/community mappings.
- Inspect the primary/secondary association to shared-service promiscuous ports, then correct only authorized connectivity.
- Configure supported L2PT for the required control protocols and verify provider-edge handling.
Explanation
Correct Answer
D:Layer 2 protocol tunneling preserves selected customer control traffic across a service where ordinary data tagging is not enough. Verify this by checking that the customer control protocol reaches the far endpoint without altering the provider's own spanning-tree topology.
Incorrect Answers
A:“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: 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.
B:“Inspect primary and secondary private VLAN roles and port membership; restore approved isolated/community mappings” belongs to a separate Ethernet Switching and Spanning Tree issue: a shared guest access VLAN allows two untrusted hotel-room ports to communicate directly, violating the isolation design. 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.
Question 882
A Junos enterprise team investigates this incident: An ABR starts leaking a management static route into the enterprise IGP after a permissive export term was introduced. Which technical explanation most directly identifies the cause or design principle?
- OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
- OSPF neighbors require compatible Hello and dead interval settings on the shared interface.
- Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability.
- IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges.
Explanation
Correct Answer
C:Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability. The appropriate response is to restrict the export policy to explicit approved route prefixes and protocols, then check external LSAs.
Incorrect Answers
A:“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.
B:“OSPF neighbors require compatible Hello and dead interval settings on the shared interface” belongs to a separate Interior Gateway Protocols (IGPs) issue: an access-area adjacency drops after one device is changed to shorter OSPF Hello timers but its peer keeps prior settings. It does not explain the condition tested here.
D:“IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges” belongs to a separate Interior Gateway Protocols (IGPs) issue: an IPv6 branch outage is misdiagnosed using only IPv4 pings, despite OSPFv3 neighbors using IPv6 link-local messaging. It does not explain the condition tested here.
Question 883
To prevent recurrence of this precise networking failure, which practice should be adopted? A voice handset fails to boot on an EX switch port after new cameras consume the remaining PoE budget.
- Capacity-plan PoE power classes and reserved headroom before connecting new powered devices.
- Review LLDP-MED state and phone compliance during access-switch template audits.
- Synchronize switchport moves with maintained emergency location records.
- Validate PD power profiles and test peak draw rather than idle boot alone.
Explanation
Correct Answer
A:Capacity-plan PoE power classes and reserved headroom before connecting new powered devices. This guards against PoE availability depends on the supported per-port power class and total switch power budget, not just Ethernet link status.
Incorrect Answers
B:“Review LLDP-MED state and phone compliance during access-switch template audits” belongs to a separate IP Telephony Features issue: a phone supports LLDP-MED but the switch sends no med TLVs after a policy template disables the feature. It does not explain the condition tested here.
C:“Synchronize switchport moves with maintained emergency location records” 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:“Validate PD power profiles and test peak draw rather than idle boot alone” instead concerns another network scenario: A phone's LLDP-negotiated power demand exceeds its access port's allocated PoE limit and it repeatedly restarts. It does not address the requirement here.
Question 884
A Junos enterprise team investigates this incident: An IPv6 branch outage is misdiagnosed using only IPv4 pings, despite OSPFv3 neighbors using IPv6 link-local messaging. Which technical explanation most directly identifies the cause or design principle?
- DR/BDR elections on OSPF broadcast networks affect LSA exchange and can be influenced by priority.
- IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges.
- OSPF neighbors require compatible Hello and dead interval settings on the shared interface.
- Local import policy can affect installed route visibility independently of the remote origination of LSAs.
Explanation
Correct Answer
B:IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges. The appropriate response is to check IPv6 link-local addressing, OSPFv3 neighbor state and relevant ICMPv6 connectivity on the actual interface.
Incorrect Answers
A:“DR/BDR elections on OSPF broadcast networks affect LSA exchange and can be influenced by priority” belongs to a separate Interior Gateway Protocols (IGPs) issue: a shared multiaccess segment elects an undesired OSPF DR after new routers are connected, and control-plane load rises. It does not explain the condition tested here.
C:“OSPF neighbors require compatible Hello and dead interval settings on the shared interface” belongs to a separate Interior Gateway Protocols (IGPs) issue: an access-area adjacency drops after one device is changed to shorter OSPF Hello timers but its peer keeps prior settings. 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: an OSPF import policy hides external routes on one device while neighbors retain them, confusing the team reviewing reachability. It does not explain the condition tested here.
Question 885
The team believes it has resolved this Junos issue: An industrial sensor lacks a supplicant but needs restricted network authorization through a centralized identity service. Which observation best verifies the specific intended result?
- The observed authentication state identifies missing supplicant response, and the approved method onboards the endpoint.
- The user sees a valid login prompt and receives only the approved post-login policy.
- During a simulated RADIUS outage, endpoints receive only the approved degraded-connectivity policy.
- The registered device is authorized with limited access; an unknown MAC remains blocked.
Explanation
Correct Answer
D:The registered device is authorized with limited access; an unknown MAC remains blocked. This checks the relevant result after configure supported MAC RADIUS under least-privilege policy and register the device MAC with the approved service.
Incorrect Answers
A:“The observed authentication state identifies missing supplicant response, and the approved method onboards the endpoint” belongs to a separate Layer 2 Authentication and Access Control issue: a RADIUS server reports no Access-Request for a silent legacy terminal, while switch timers show no EAP response. It does not explain the condition tested here.
B:“The user sees a valid login prompt and receives only the approved post-login policy” belongs to a separate Layer 2 Authentication and Access Control issue: guest users on an EX switch see no captive login page because browser HTTP redirects are not being applied on the intended VLAN. It does not explain the condition tested here.
C:“During a simulated RADIUS outage, endpoints receive only the approved degraded-connectivity policy” belongs to a separate Layer 2 Authentication and Access Control issue: an enterprise fallback design accidentally places unauthenticated users into the production network when all RADIUS servers fail. It does not explain the condition tested here.
Question 886
A Junos enterprise team investigates this incident: A new IPv4 BGP prefix has a valid AS path but cannot become active after the IGP stops carrying its next-hop address. Which technical explanation most directly identifies the cause or design principle?
- BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state.
- 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.
- BGP route selection first requires the BGP next hop to resolve through the appropriate routing table.
Explanation
Correct Answer
D:BGP route selection first requires the BGP next hop to resolve through the appropriate routing table. The appropriate response is to restore permitted next-hop reachability via IGP or adjust next-hop policy where appropriate; recheck route detail.
Incorrect Answers
A:“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: BGP peers exchange IPv4 NLRI correctly but a planned IPv6 customer route never appears in inet6.0. It does not explain the condition tested here.
B:“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.
C:“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 887
A network change is required for the following specific situation: An IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement. Which corrective action is most appropriate?
- Examine both attributes in the received route detail and update the explicit routing policy rather than guessing.
- Put specific deny conditions before broad acceptance, and test the policy with representative routes.
- Document and test terminal accept or reject behavior along with next-term and next-policy handling.
- Check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Explanation
Correct Answer
D:BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops. Verify this by checking that the IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop.
Incorrect Answers
A:“Examine both attributes in the received route detail and update the explicit routing policy rather than guessing” 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.
B:“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.
C:“Document and test terminal accept or reject behavior along with next-term and next-policy handling” 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.
Question 888
A Junos enterprise team investigates this incident: A router's OSPF neighbor restarts repeatedly because duplicate router IDs were assigned to different routing nodes. Which technical explanation most directly identifies the cause or design principle?
- Routing-policy match criteria must align with the source route type and the intended OSPF export behavior.
- OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
- IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges.
- Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability.
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:“Routing-policy match criteria must align with the source route type and the intended OSPF export behavior” 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.
C:“IPv4 packet reachability does not independently validate OSPFv3's IPv6 link-local neighbor exchanges” belongs to a separate Interior Gateway Protocols (IGPs) issue: an OSPFv3 adjacency on a dual-stack campus changes state because engineers treat IPv4 interface reachability as proof of IPv6 control-plane health. It does not explain the condition tested here.
D:“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.
Question 889
Which suggested shortcut would be especially unsafe for this exact situation? An access-area adjacency drops after one device is changed to shorter OSPF Hello timers but its peer keeps prior settings.
- Change only BGP keepalive values and assume OSPF timers automatically follow.
- Test one allowed and one forbidden route against each export policy term before deployment.
- Record both LSDB presence and local RIB installation in OSPF troubleshooting runbooks.
- Use named prefix lists and regression tests for approved and denied redistribution cases.
Explanation
Correct Answer
A:The tempting alternative fails because OSPF neighbors require compatible Hello and dead interval settings on the shared interface. The supported action is to compare OSPF interface timers and align the two peers to approved Hello and dead values.
Incorrect Answers
B:That prevention measure relates to a branch default-route injection stops after a policy matches OSPF-learned routes instead of the intended local static.; it is not the unsafe shortcut described here.
C: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.
D:That prevention measure relates to an ABR starts leaking a management static route into the enterprise IGP after a permissive export term was introduced.; it is not the unsafe shortcut described here.
Question 890
A Junos enterprise team investigates this incident: An ASM video distribution has valid listener memberships yet PIM joins never converge toward the configured RP. Which technical explanation most directly identifies the cause or design principle?
- Multicast administrative scoping must restrict eligible groups and outgoing boundaries; group addresses alone do not impose all policy.
- PIM sparse-mode ASM builds shared-tree state toward a reachable RP, and an incorrect RP mapping can prevent service.
- An RPF check is tied to the selected source path, so asymmetric arrival can invalidate otherwise reachable multicast traffic.
- ASM and SSM use different membership and source-selection semantics; an SSM receiver must identify its desired sender.
Explanation
Correct Answer
B:PIM sparse-mode ASM builds shared-tree state toward a reachable RP, and an incorrect RP mapping can prevent service. The appropriate response is to check group-to-RP mapping and RP reachability, then repair the RP discovery or explicit mapping.
Incorrect Answers
A:“Multicast administrative scoping must restrict eligible groups and outgoing boundaries; group addresses alone do not impose all policy” belongs to a separate IP Multicast issue: a laboratory's multicast test group leaks to the corporate backbone despite a requirement to keep it within the lab. It does not explain the condition tested here.
C:“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.
D:“ASM and SSM use different membership and source-selection semantics; an SSM receiver must identify its desired sender” 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.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests