100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 570
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A campus extension carries the right VXLAN outer header but directs frames to the wrong tenant bridge domain due to bad VNI mapping.
- Assume a data-plane VXLAN tunnel automatically updates every remote leaf's EVPN MAC reachability without Type 2 control-plane exchange.
- Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address.
- Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
- Tenant traffic reaches only its intended remote bridge domain and overlapping VLAN IDs remain isolated.
- Reuse one VNI for unrelated tenants and assume local VLAN names alone prevent overlay mixing.
Explanation
Correct Answers
C:Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map. This addresses the dependency that VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
D:Tenant traffic reaches only its intended remote bridge domain and overlapping VLAN IDs remain isolated. The specific steps required are to compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
Incorrect Answers
A:“Assume a data-plane VXLAN tunnel automatically updates every remote leaf's EVPN MAC reachability without Type 2 control-plane exchange” is an unsafe response to a different problem: a new endpoint MAC is learned at a remote VTEP but never reaches the receiving leaf's EVPN control-plane table. It is not a valid fix here.
B:“Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address” is an unsafe response to a different problem: a troubleshooting team expects EVPN Ethernet auto-discovery route Type 1 to carry all host MAC/IP bindings. It is not a valid fix here.
E:“Reuse one VNI for unrelated tenants and assume local VLAN names alone prevent overlay mixing” does not address VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
Question 571
The team believes it has resolved this Junos issue: An IPv6 transit prefix is hidden because its next-hop address is absent from the correct IPv6 routing table. Which observation best verifies the specific intended result?
- The unauthorized route is rejected while intended export cases still match the proper terms.
- The selected BGP route reflects the intended higher LOCAL_PREF, and traceroute follows the approved exit.
- The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop.
- The chosen best path follows the documented attribute ordering rather than a single observed MED value.
Explanation
Correct Answer
C:The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop. This checks the relevant result after check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Incorrect Answers
A:“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.
B:“The selected BGP route reflects the intended higher LOCAL_PREF, and traceroute follows the approved exit” 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.
D:“The chosen best path follows the documented attribute ordering rather than a single observed MED value” 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.
Question 572
To prevent recurrence of this precise networking failure, which practice should be adopted? Packets with two different drop precedence values are treated as equally discardable during congestion.
- Validate classifier, scheduler map and interface association as a complete CoS chain.
- Review queue buffer tradeoffs and regression-test peak loads before tuning schedulers.
- Plan buffer and shaping rates against provider handoff capacity and expected burst size.
- Test marking, PLP assignment and drop policy together rather than checking only DSCP fields.
Explanation
Correct Answer
D:Test marking, PLP assignment and drop policy together rather than checking only DSCP fields. This guards against packet loss priority differentiates drop susceptibility within a forwarding class and works with the configured queue/drop behavior.
Incorrect Answers
A:“Validate classifier, scheduler map and interface association as a complete CoS chain” belongs to a separate Class of Service (CoS) issue: a low-latency queue is correctly classified but voice delays because its egress scheduler map is absent from the trunk. It does not explain the condition tested here.
B:“Review queue buffer tradeoffs and regression-test peak loads before tuning schedulers” belongs to a separate Class of Service (CoS) issue: video gets dropped under congestion despite spare capacity because its queue has a too-small delay buffer. It does not explain the condition tested here.
C:“Plan buffer and shaping rates against provider handoff capacity and expected burst size” 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.
Question 573
The team believes it has resolved this Junos issue: A campus summarization change hides a needed subnet because the configured address range omits it. Which observation best verifies the specific intended result?
- Only authorized static prefixes appear as OSPF externals; management prefixes remain local.
- An OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0.
- The backbone receives the intended aggregate and routers can reach all included component subnets.
- The preferred primary route wins when healthy and the backup becomes active on a controlled failure.
Explanation
Correct Answer
C:The backbone receives the intended aggregate and routers can reach all included component subnets. This checks the relevant result after verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan.
Incorrect Answers
A:“Only authorized static prefixes appear as OSPF externals; management prefixes remain local” 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.
B:“An OSPFv3 neighbor forms and approved IPv6 prefixes appear in inet6.0” 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.
D:“The preferred primary route wins when healthy and the backup becomes active on a controlled failure” belongs to a separate Interior Gateway Protocols (IGPs) issue: a branch receives two external paths with different metric-type assumptions after a policy change and prefers the wrong exit. It does not explain the condition tested here.
Question 574
Which suggested shortcut would be especially unsafe for this exact situation? An OSPF policy update redistributes a route without an appropriate external metric, shifting traffic to a slow backup.
- Validate active logical-interface mappings and IPv6 adjacency as part of change acceptance.
- Make physical and logical MTU parity part of transit-link commissioning and review.
- Increase every external metric blindly without checking which path should win.
- Specify preferred OSPF DR candidates on shared transit segments and account for non-preemptive elections.
Explanation
Correct Answer
C:The tempting alternative fails because OSPF external route costs and metric types affect path choice and must reflect intended topology and failover behavior. The supported action is to review external metric type and value at the originator, then apply the documented traffic-engineering policy.
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 two EX distribution routers in OSPF area 0 remain in ExStart after a new transit VLAN uses inconsistent interface MTUs.; it is not the unsafe shortcut described here.
D:That prevention measure relates to an aggregation broadcast VLAN has a DR/BDR placement that conflicts with the approved design after a maintenance reboot.; it is not the unsafe shortcut described here.
Question 575
Select THREE complementary corrective, verification, or preventive controls for this scenario: A branch wants to enforce a traffic contract on an incoming service flow yet applies policing to an unrelated egress path.
- Differentiate ingress policing from egress shaping when designing bandwidth controls.
- Assume a correct internal forwarding class guarantees outgoing DSCP is preserved without rewrite policy.
- Assume more queues automatically improve latency even if control traffic remains mapped to a congested queue.
- Measured guest ingress usage remains within policy and permitted business traffic is unaffected.
- Apply a correctly scoped ingress policer with tested rate and burst values on the relevant flow.
- Use an egress shaper at the wrong interface as a substitute for every ingress traffic-contract check.
Explanation
Correct Answers
A:Prevention of recurrence: A policer enforces traffic rate or burst limits and can discard or mark out-of-profile input; shaping buffers traffic for paced egress.
D:Confirmation: Apply a correctly scoped ingress policer with tested rate and burst values on the relevant flow.
E:Correction: A policer enforces traffic rate or burst limits and can discard or mark out-of-profile input; shaping buffers traffic for paced egress.
Incorrect Answers
B:“Assume a correct internal forwarding class guarantees outgoing DSCP is preserved without rewrite policy” is an unsafe response to a different problem: a provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior. It is not a valid fix here.
C:“Assume more queues automatically improve latency even if control traffic remains mapped to a congested queue” is an unsafe response to a different problem: a forwarding-class configuration sends critical routing packets to a queue used for bulk backups and adjacency stability degrades under load. It is not a valid fix here.
F:“Use an egress shaper at the wrong interface as a substitute for every ingress traffic-contract check” does not address a policer enforces traffic rate or burst limits and can discard or mark out-of-profile input; shaping buffers traffic for paced egress.
Question 576
To prevent recurrence of this precise networking failure, which practice should be adopted? Two EX distribution routers in OSPF area 0 remain in ExStart after a new transit VLAN uses inconsistent interface MTUs.
- Verify both protocol RIB candidates and active next-hop selection in dual-stack change tests.
- Make physical and logical MTU parity part of transit-link commissioning and review.
- Test one allowed and one forbidden route against each export policy term before deployment.
- Use named prefix lists and regression tests for approved and denied redistribution cases.
Explanation
Correct Answer
B:Make physical and logical MTU parity part of transit-link commissioning and review. This guards against OSPF database-description exchange can stall when adjacent interfaces disagree on MTU even though basic Hello connectivity exists.
Incorrect Answers
A:“Verify both protocol RIB candidates and active next-hop selection in dual-stack change tests” belongs to a separate Interior Gateway Protocols (IGPs) issue: a team wrongly concludes OSPFv3 failed when inet6.0 shows a static route active and the OSPFv3 candidate inactive. It does not explain the condition tested here.
C:“Test one allowed and one forbidden route against each export policy term before deployment” 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.
D:“Use named prefix lists and regression tests for approved and denied redistribution cases” belongs to a separate Interior Gateway Protocols (IGPs) issue: an ABR starts leaking a management static route into the enterprise IGP after a permissive export term was introduced. It does not explain the condition tested here.
Question 577
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: A shared multiaccess segment elects an undesired OSPF DR after new routers are connected, and control-plane load rises.
- Inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change.
- Add a catch-all accept at the end of the policy to bypass the source-type error.
- Assume increasing OSPF priority immediately preempts an existing healthy DR on every device.
- Neighbor states and DR/BDR assignments match the approved design following a managed election.
- Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically.
Explanation
Correct Answers
A:Inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change. This addresses the dependency that DR/BDR elections on OSPF broadcast networks affect LSA exchange and can be influenced by priority.
D:Neighbor states and DR/BDR assignments match the approved design following a managed election. The specific steps required are to inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change.
Incorrect Answers
B:“Add a catch-all accept at the end of the policy to bypass the source-type error” is an unsafe response to a different problem: an OSPF export term filters routes based on the wrong protocol, so an intended static default is not originated. It is not a valid fix here.
C:“Assume increasing OSPF priority immediately preempts an existing healthy DR on every device” does not address DR/BDR elections on OSPF broadcast networks affect LSA exchange and can be influenced by priority.
E:“Configure IPv4 OSPFv2 alone and expect it to populate IPv6 unicast routes automatically” is an unsafe response to a different problem: a new IPv6 peering uses OSPFv3 on a retired VLAN unit rather than the active routed transit interface. It is not a valid fix here.
Question 578
A Junos enterprise team investigates this incident: OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout. Which technical explanation most directly identifies the cause or design principle?
- Local import policy can affect installed route visibility independently of the remote origination of LSAs.
- An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology.
- OSPF external route costs and metric types affect path choice and must reflect intended topology and failover behavior.
- OSPF neighbors require compatible Hello and dead interval settings on the shared interface.
Explanation
Correct Answer
B:An established OSPFv3 neighbor does not prove every desired IPv6 interface prefix is included in the protocol topology. The appropriate response is to inspect IPv6 interface addresses and OSPFv3 interface participation, then add the intended loopback advertisement within policy.
Incorrect Answers
A:“Local import policy can affect installed route visibility independently of the remote origination of LSAs” belongs to a separate Interior Gateway Protocols (IGPs) issue: a core node shows a missing route while remote LSDBs include the corresponding external LSA after a local policy change. It does not explain the condition tested here.
C:“OSPF external route costs and metric types affect path choice and must reflect intended topology and failover behavior” belongs to a separate Interior Gateway Protocols (IGPs) issue: a branch receives two external paths with different metric-type assumptions after a policy change and prefers the wrong exit. It does not explain the condition tested here.
D:“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.
Question 579
A network change is required for the following specific situation: A new endpoint MAC is learned at a remote VTEP but never reaches the receiving leaf's EVPN control-plane table. Which corrective action is most appropriate?
- Check relevant BGP EVPN Type 2 advertisements, MAC mobility updates and import policy for the affected bridge domain.
- Align the intended ESI and supported LAG mode, then inspect relevant EVPN Type 1 and Type 4 routes.
- Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies.
- Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
Explanation
Correct Answer
A:EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane. Verify this by checking that the current MAC location is learned and traffic reaches the moved endpoint without persistent old-VTEP forwarding.
Incorrect Answers
B:“Align the intended ESI and supported LAG mode, then inspect relevant EVPN Type 1 and Type 4 routes” belongs to a separate EVPN issue: a shared Ethernet segment loses its fast convergence properties after an ESI-LAG peer receives an inconsistent configuration. It does not explain the condition tested here.
C:“Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies” belongs to a separate EVPN issue: a new leaf imports VNI reachability but packets disappear because its VXLAN tunnel endpoint IP is unresolved. It does not explain the condition tested here.
D:“Compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map” belongs to a separate EVPN issue: a fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. It does not explain the condition tested here.
Question 580
A Junos enterprise team investigates this incident: An edge router uses a broad multicast filter that blocks valid collaboration groups alongside restricted lab streams. Which technical explanation most directly identifies the cause or design principle?
- Anycast RP aims for a stable RP address with multiple nodes; consistent source discovery and RP coordination are essential to the chosen architecture.
- Junos multicast RPF may use a dedicated routing table, so the effective RPF path must be inspected, not guessed from unicast traffic.
- Policy selectors must match the intended multicast group and source ranges so unrelated services are not blocked or leaked.
- ASM and SSM use different membership and source-selection semantics; an SSM receiver must identify its desired sender.
Explanation
Correct Answer
C:Policy selectors must match the intended multicast group and source ranges so unrelated services are not blocked or leaked. The appropriate response is to refine the relevant multicast policy ranges and inspect forwarding for both permitted and denied groups.
Incorrect Answers
A:“Anycast RP aims for a stable RP address with multiple nodes; consistent source discovery and RP coordination are essential to the chosen architecture” belongs to a separate IP Multicast issue: a second campus RP is deployed for availability but source-awareness synchronization is omitted where the design requires it. It does not explain the condition tested here.
B:“Junos multicast RPF may use a dedicated routing table, so the effective RPF path must be inspected, not guessed from unicast traffic” belongs to a separate IP Multicast issue: a multicast team changes unicast routing yet an engineered multicast RPF table still points to an obsolete next hop. 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 campus multicast application migrates ASM clients to SSM but does not update the source-qualified membership requests. It does not explain the condition tested here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests