100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 770
A network change is required for the following specific situation: A core node shows a missing route while remote LSDBs include the corresponding external LSA after a local policy change. Which corrective action is most appropriate?
- Move OSPFv3 participation to the correct active interface and verify neighbor and IPv6 RIB state.
- Compare LSDB advertisements with local route policy and inet.0 state; correct the intended import filter.
- Inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change.
- Verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan.
Explanation
Correct Answer
B:Local import policy can affect installed route visibility independently of the remote origination of LSAs. Verify this by checking that the expected prefix becomes active locally while unwanted external prefixes remain filtered.
Incorrect Answers
A:“Move OSPFv3 participation to the correct active interface and verify neighbor and IPv6 RIB state” 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:“Inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change” belongs to a separate Interior Gateway Protocols (IGPs) issue: an aggregation broadcast VLAN has a DR/BDR placement that conflicts with the approved design after a maintenance reboot. It does not explain the condition tested here.
D:“Verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan” belongs to a separate Interior Gateway Protocols (IGPs) issue: an ABR stops advertising a branch prefix into the backbone after an OSPF area-range summary is configured incorrectly. It does not explain the condition tested here.
Question 771
To prevent recurrence of this precise networking failure, which practice should be adopted? A route with a permissive policy term is accepted before a later deny term can block it.
- Review policy ordering with negative tests and explicit default actions on every change.
- Audit prefix and mask-length boundaries with positive and negative routing-policy tests.
- Test expected best-path behavior before modifying LOCAL_PREF across internal peers.
- Use multivariable path-selection lab tests before changing MED-based policy.
Explanation
Correct Answer
A:Review policy ordering with negative tests and explicit default actions on every change. This guards against routing-policy term order and terminal actions determine whether later conditions are evaluated.
Incorrect Answers
B:“Audit prefix and mask-length boundaries with positive and negative routing-policy tests” belongs to a separate Border Gateway Protocol (BGP) issue: an eBGP import policy unexpectedly accepts more-specific prefixes outside the approved customer allocation. It does not explain the condition tested here.
C:“Test expected best-path behavior before modifying LOCAL_PREF across internal peers” belongs to a separate Border Gateway Protocol (BGP) issue: two iBGP exits offer equal reachable routes but the one with higher LOCAL_PREF is not the egress an operator expected. It does not explain the condition tested here.
D:“Use multivariable path-selection lab tests before changing MED-based policy” 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.
Question 772
The team believes it has resolved this Junos issue: A phone supports LLDP-MED but the switch sends no med TLVs after a policy template disables the feature. Which observation best verifies the specific intended result?
- Packet and operational views show the required LLDP-MED telephony TLVs at the correct interface.
- The device stays powered during peak consumption and Junos reports no power-denial events.
- The phone receives voice service on its tagged VLAN and the PC remains on its separate data VLAN.
- The handset learns the authorized voice VLAN and traffic is tagged and prioritized according to design.
Explanation
Correct Answer
A:Packet and operational views show the required LLDP-MED telephony TLVs at the correct interface. This checks the relevant result after review LLDP and LLDP-MED operational status and enable supported MED policy for phone access.
Incorrect Answers
B:“The device stays powered during peak consumption and Junos reports no power-denial events” belongs to a separate IP Telephony Features issue: an emergency intercom can establish Ethernet link but loses power during activity because its PD class is not supported by that port. It does not explain the condition tested here.
C:“The phone receives voice service on its tagged VLAN and the PC remains on its separate data VLAN” belongs to a separate IP Telephony Features issue: a phone-with-PC desk deployment lets the PC reach data services while the tagged voice stream is dropped by VLAN membership. 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” instead concerns another network scenario: 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 address the requirement here.
Question 773
To prevent recurrence of this precise networking failure, which practice should be adopted? An enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path.
- Include show route hidden and policy term hit checks in BGP troubleshooting playbooks.
- Audit prefix and mask-length boundaries with positive and negative routing-policy tests.
- Monitor AS-path anomalies and validate inter-AS topology changes before enabling export.
- Test expected best-path behavior before modifying LOCAL_PREF across internal peers.
Explanation
Correct Answer
D:Test expected best-path behavior before modifying LOCAL_PREF across internal peers. This guards against BGP typically prefers a larger LOCAL_PREF among otherwise eligible candidates before later path-selection tie breakers.
Incorrect Answers
A:“Include show route hidden and policy term hit checks in BGP troubleshooting playbooks” 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.
B:“Audit prefix and mask-length boundaries with positive and negative routing-policy tests” belongs to a separate Border Gateway Protocol (BGP) issue: a prefix-list matches a broad aggregate but accepts unwanted subprefixes from a new external neighbor. It does not explain the condition tested here.
C:“Monitor AS-path anomalies and validate inter-AS topology changes before enabling export” belongs to a separate Border Gateway Protocol (BGP) issue: the local AS appears in a received external BGP AS_PATH and the route is rejected despite valid prefix reachability. It does not explain the condition tested here.
Question 774
To prevent recurrence of this precise networking failure, which practice should be adopted? Members of the same trusted workgroup are accidentally placed in isolated rather than community PVLAN ports and lose peer communication.
- Document primary/secondary VLAN mappings and test permitted peer groups and isolation boundaries.
- Include MVRP adjacency and registration checks in trunk-change reviews.
- Include packet-capture verification of S-tag and C-tag transformation in provider handoffs.
- Track VLAN lifecycle and MVRP registration ownership as ports are decommissioned.
Explanation
Correct Answer
A:Document primary/secondary VLAN mappings and test permitted peer groups and isolation boundaries. This guards against a private VLAN community allows permitted communication within its community; isolated behavior is stricter.
Incorrect Answers
B:“Include MVRP adjacency and registration checks in trunk-change reviews” 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.
C:“Include packet-capture verification of S-tag and C-tag transformation in provider handoffs” belongs to a separate Ethernet Switching and Spanning Tree issue: customer traffic emerges with the provider service tag still attached and is rejected by an endpoint expecting ordinary Ethernet. It does not explain the condition tested here.
D:“Track VLAN lifecycle and MVRP registration ownership as ports are decommissioned” 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 775
Select THREE complementary corrective, verification, or preventive controls for this scenario: A building's private VLAN design inadvertently limits tenant access to a shared printer uplink while direct tenant communication is supposed to stay blocked.
- Assume that one switch's locally created VLAN is automatically registered on all links with MVRP disabled.
- Assume every endpoint supports stacked 802.1Q tags even when the customer ordered a single-tagged handoff.
- Inspect the primary/secondary association to shared-service promiscuous ports, then correct only authorized connectivity.
- Isolated clients reach the shared service but cannot communicate laterally with other isolated clients.
- Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews.
- Disable private VLAN restrictions entirely as a shortcut to reach a single shared uplink service.
Explanation
Correct Answers
C:Correction: Private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles.
D:Confirmation: Inspect the primary/secondary association to shared-service promiscuous ports, then correct only authorized connectivity.
E:Prevention of recurrence: Private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles.
Incorrect Answers
A:“Assume that one switch's locally created VLAN is automatically registered on all links with MVRP disabled” is an unsafe response to a different problem: a new switch automatically discovers VLAN registrations on one trunk, but an intermediate trunk lacks MVRP participation and blocks the VLAN. It is not a valid fix here.
B:“Assume every endpoint supports stacked 802.1Q tags even when the customer ordered a single-tagged handoff” is an unsafe response to a different problem: customer traffic emerges with the provider service tag still attached and is rejected by an endpoint expecting ordinary Ethernet. It is not a valid fix here.
F:“Disable private VLAN restrictions entirely as a shortcut to reach a single shared uplink service” does not address private VLAN communication depends on permitted mappings to promiscuous ports and permitted community or isolated roles.
Question 776
To prevent recurrence of this precise networking failure, which practice should be adopted? An 802.1Q trunk carries customer data through a provider Ethernet segment but fails to forward the required spanning-tree control frames transparently.
- Document primary/secondary VLAN mappings and test permitted peer groups and isolation boundaries.
- Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews.
- Test each critical VLAN's root bridge and forwarding path after VSTP updates.
- Scope and monitor tunneled L2 control protocols to prevent control-plane abuse.
Explanation
Correct Answer
D:Scope and monitor tunneled L2 control protocols to prevent control-plane abuse. This guards against layer 2 protocol tunneling preserves selected customer control traffic across a service where ordinary data tagging is not enough.
Incorrect Answers
A:“Document primary/secondary VLAN mappings and test permitted peer groups and isolation boundaries” 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:“Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews” belongs to a separate Ethernet Switching and Spanning Tree issue: a private VLAN isolated endpoint reaches the local gateway but cannot access a peer service that should be shared via a permitted promiscuous port. It does not explain the condition tested here.
C:“Test each critical VLAN's root bridge and forwarding path after VSTP updates” belongs to a separate Ethernet Switching and Spanning Tree issue: a legacy interop design needs separate per-VLAN spanning-tree compatibility but all VLANs inherit one unsuitable tree. It does not explain the condition tested here.
Question 777
A Junos enterprise team investigates this incident: A vendor handset discovers its neighbor using basic LLDP but does not learn the configured network policy for voice tagging. Which technical explanation most directly identifies the cause or design principle?
- LLDP-MED extends device discovery with telephony-related network-policy TLVs that need compatible endpoint behavior.
- PoE availability depends on the supported per-port power class and total switch power budget, not just Ethernet link status.
- PoE priority is a tool for allocating scarce power among endpoints when the chassis budget is constrained.
- Voice/data split depends on compatible VLAN membership, accepted 802.1Q tagging and endpoint network policy.
Explanation
Correct Answer
A:LLDP-MED extends device discovery with telephony-related network-policy TLVs that need compatible endpoint behavior. The appropriate response is to enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings.
Incorrect Answers
B:“PoE availability depends on the supported per-port power class and total switch power budget, not just Ethernet link status” belongs to a separate IP Telephony Features issue: a voice handset fails to boot on an EX switch port after new cameras consume the remaining PoE budget. It does not explain the condition tested here.
C:“PoE priority is a tool for allocating scarce power among endpoints when the chassis budget is constrained” belongs to a separate IP Telephony Features issue: a switch assigns equal PoE power priority to every port and disconnects an emergency phone before low-priority signage during a power shortage. It does not explain the condition tested here.
D:“Voice/data split depends on compatible VLAN membership, accepted 802.1Q tagging and endpoint network policy” belongs to a separate IP Telephony Features issue: a phone-with-PC desk deployment lets the PC reach data services while the tagged voice stream is dropped by VLAN membership. It does not explain the condition tested here.
Question 778
To prevent recurrence of this precise networking failure, which practice should be adopted? Two eBGP sessions over different transports are expected to provide ECMP but only one forwarding next hop appears.
- Maintain community inventories and test outbound policy outcomes for allowed and denied prefixes.
- Use multivariable path-selection lab tests before changing MED-based policy.
- Test path equivalence, forwarding and failure convergence before enabling transit ECMP.
- Test expected best-path behavior before modifying LOCAL_PREF across internal peers.
Explanation
Correct Answer
C:Test path equivalence, forwarding and failure convergence before enabling transit ECMP. This guards against BGP equal-cost multipath requires appropriate configured support and matching eligible path attributes, not merely two established sessions.
Incorrect Answers
A:“Maintain community inventories and test outbound policy outcomes for allowed and denied prefixes” 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.
B:“Use multivariable path-selection lab tests before changing MED-based policy” 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.
D:“Test expected best-path behavior before modifying LOCAL_PREF across internal peers” belongs to a separate Border Gateway Protocol (BGP) issue: an enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path. It does not explain the condition tested here.
Question 779
The team believes it has resolved this Junos issue: An iBGP egress advertisement forwards a transit next hop that branch routers cannot resolve, creating traffic blackholes. Which observation best verifies the specific intended result?
- A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI.
- External peer advertisements show the intended supported attributes and inbound traffic is measured.
- The unauthorized route is rejected while intended export cases still match the proper terms.
- Route detail shows a reachable next hop and end-to-end forwarding through the intended border router.
Explanation
Correct Answer
D:Route detail shows a reachable next hop and end-to-end forwarding through the intended border router. This checks the relevant result after inspect next-hop attributes and IGP reachability; deliberately choose appropriate next-hop-self policy or add valid underlay routes.
Incorrect Answers
A:“A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI” belongs to a separate Border Gateway Protocol (BGP) issue: a multihop eBGP peer uses loopback addresses but its session times out when directly connected assumptions remain. It does not explain the condition tested here.
B:“External peer advertisements show the intended supported attributes and inbound traffic is measured” 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 unauthorized route is rejected while intended export cases still match the proper terms” belongs to a separate Border Gateway Protocol (BGP) issue: a BGP export configuration has a broad first match so a specific downstream deny never evaluates the target prefix. It does not explain the condition tested here.
Question 780
Which suggested shortcut would be especially unsafe for this exact situation? Members of the same trusted workgroup are accidentally placed in isolated rather than community PVLAN ports and lose peer communication.
- Make every tenant port promiscuous simply to restore one workgroup's access.
- Version-control MSTP name, revision and VLAN mapping as one change unit.
- Document outer/inner VLAN roles and test tag stripping and preservation at service boundaries.
- Track MSTP instance scale and maintain identical region parameters across participating switches.
Explanation
Correct Answer
A:The tempting alternative fails because a private VLAN community allows permitted communication within its community; isolated behavior is stricter. The supported action is to map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated.
Incorrect Answers
B:That prevention measure relates to two adjacent MSTP switches show different region digests after one has a different VLAN-to-instance map.; it is not the unsafe shortcut described here.
C: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.
D:That prevention measure relates to a network uses one VLAN-wide topology but wants two forwarding trees for different groups without an instance for every VLAN.; it is not the unsafe shortcut described here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests