100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 810
A network change is required for the following specific situation: An IPv6 route learned through OSPFv3 is absent from the forwarding table because a more preferred static route covers the same prefix. Which corrective action is most appropriate?
- Compare LSDB advertisements with local route policy and inet.0 state; correct the intended import filter.
- Inspect inet6.0 route detail and route preferences before changing OSPFv3 neighbor configuration.
- Assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence.
- Inspect the active local default and export term conditions; match only the authorized static default source.
Explanation
Correct Answer
B:Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate. Verify this by checking that the team explains the selected active route and verifies intended failover without disturbing OSPFv3 adjacency.
Incorrect Answers
A:“Compare LSDB advertisements with local route policy and inet.0 state; correct the intended import filter” 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.
C:“Assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence” belongs to a separate Interior Gateway Protocols (IGPs) issue: two newly deployed distribution switches report identical OSPF router IDs, causing inconsistent LSAs in the area. It does not explain the condition tested here.
D:“Inspect the active local default and export term conditions; match only the authorized static default source” 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.
Question 811
Select THREE complementary corrective, verification, or preventive controls for this scenario: A provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior.
- Apply the appropriate interface rewrite rule and verify the contract-specific egress code points.
- Use an egress shaper at the wrong interface as a substitute for every ingress traffic-contract check.
- Map every packet to the lowest loss priority regardless of its out-of-profile status.
- Test ingress classification separately from egress rewrite at every trust boundary.
- Assume a correct internal forwarding class guarantees outgoing DSCP is preserved without rewrite policy.
- Packet captures show the intended DSCP or 802.1p fields on outbound voice, video and data traffic.
Explanation
Correct Answers
A:Correction: Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings.
D:Prevention of recurrence: Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings.
F:Confirmation: Apply the appropriate interface rewrite rule and verify the contract-specific egress code points.
Incorrect Answers
B:“Use an egress shaper at the wrong interface as a substitute for every ingress traffic-contract check” is an unsafe response to a different problem: a guest network should be rate-limited at ingress, but engineers configure only an egress shaper on the uplink. It is not a valid fix here.
C:“Map every packet to the lowest loss priority regardless of its out-of-profile status” is an unsafe response to a different problem: packets with two different drop precedence values are treated as equally discardable during congestion. It is not a valid fix here.
E:“Assume a correct internal forwarding class guarantees outgoing DSCP is preserved without rewrite policy” does not address Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings.
Question 812
A network change is required for the following specific situation: A provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior. Which corrective action is most appropriate?
- Assign the intended service class and scheduler priorities with measured bandwidth needs, then validate.
- Apply the appropriate interface rewrite rule and verify the contract-specific egress code points.
- Review the forwarding class and queue map for control and data traffic and apply the intended assignments.
- Configure supported egress shaping at the bottleneck and verify throughput and queue behavior.
Explanation
Correct Answer
B:Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings. Verify this by checking that packet captures show the intended DSCP or 802.1p fields on outbound voice, video and data traffic.
Incorrect Answers
A:“Assign the intended service class and scheduler priorities with measured bandwidth needs, then validate” belongs to a separate Class of Service (CoS) issue: a finance video queue configured as low priority cannot meet latency targets because competing transfers share the same service policy. It does not explain the condition tested here.
C:“Review the forwarding class and queue map for control and data traffic and apply the intended assignments” belongs to a separate Class of Service (CoS) issue: a forwarding-class configuration sends critical routing packets to a queue used for bulk backups and adjacency stability degrades under load. It does not explain the condition tested here.
D:“Configure supported egress shaping at the bottleneck and verify throughput and queue behavior” belongs to a separate Class of Service (CoS) issue: a branch link should pace scheduled traffic to a slower uplink yet the team only drops excess packets abruptly. It does not explain the condition tested here.
Question 813
Select THREE complementary corrective, verification, or preventive controls for this scenario: A troubleshooting team expects EVPN Ethernet auto-discovery route Type 1 to carry all host MAC/IP bindings.
- Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address.
- Use two unrelated ESIs for one logical Ethernet segment and assume EVPN coordinates them as one.
- The expected MAC/IP binding is visible in Type 2 while multihoming and BUM state use their own route types.
- Reuse one VNI for unrelated tenants and assume local VLAN names alone prevent overlay mixing.
- Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally.
- Keep route-type purpose and acceptance checks in EVPN troubleshooting runbooks.
Explanation
Correct Answers
C:Confirmation: Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally.
E:Correction: EVPN route types carry different information: Type 1 Ethernet auto-discovery, Type 2 MAC/IP, Type 3 inclusive multicast.
F:Prevention of recurrence: EVPN route types carry different information: Type 1 Ethernet auto-discovery, Type 2 MAC/IP, Type 3 inclusive multicast.
Incorrect Answers
A:“Read a Type 1 Ethernet auto-discovery update as the definitive source of every individual host MAC address” does not address EVPN route types carry different information: Type 1 Ethernet auto-discovery, Type 2 MAC/IP, Type 3 inclusive multicast.
B:“Use two unrelated ESIs for one logical Ethernet segment and assume EVPN coordinates them as one” is an unsafe response to a different problem: a multihomed CE is attached to two leafs but one leaf advertises a different ESI, preventing expected redundancy behavior. It is not a valid fix here.
D:“Reuse one VNI for unrelated tenants and assume local VLAN names alone prevent overlay mixing” is an unsafe response to a different problem: a campus extension carries the right VXLAN outer header but directs frames to the wrong tenant bridge domain due to bad VNI mapping. It is not a valid fix here.
Question 814
To prevent recurrence of this precise networking failure, which practice should be adopted? A Junos route is hidden by import policy, but the team troubleshoots only local physical interfaces.
- Maintain expected BGP attribute decisions for every primary/secondary transit policy.
- Include show route hidden and policy term hit checks in BGP troubleshooting playbooks.
- Validate every route-reflector client and failover path in topology inventory before conversion.
- Use multivariable path-selection lab tests before changing MED-based policy.
Explanation
Correct Answer
B:Include show route hidden and policy term hit checks in BGP troubleshooting playbooks. This guards against a BGP route rejected or hidden by import policy can be absent from active forwarding despite a healthy peer session.
Incorrect Answers
A:“Maintain expected BGP attribute decisions for every primary/secondary transit policy” 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.
C:“Validate every route-reflector client and failover path in topology inventory before conversion” belongs to a separate Border Gateway Protocol (BGP) issue: a full-mesh iBGP design is converted to route reflection but one peer is treated as an ordinary nonclient and route propagation fails. 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 815
The team believes it has resolved this Junos issue: A network marks a customer route with a community but an export policy ignores the community, leaking the route to another peer. Which observation best verifies the specific intended result?
- After policy correction, chosen path and attribute ordering match documented routing intent.
- A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI.
- The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged.
- A controlled route is withheld from prohibited peers while approved routes retain their expected advertisements.
Explanation
Correct Answer
D:A controlled route is withheld from prohibited peers while approved routes retain their expected advertisements. This checks the relevant result after inspect received communities and export policy terms, then attach a tested community match and reject rule.
Incorrect Answers
A:“After policy correction, chosen path and attribute ordering match documented routing intent” belongs to a separate Border Gateway Protocol (BGP) issue: a router prefers a longer AS path when a higher LOCAL_PREF makes that route win, surprising the transit team. It does not explain the condition tested here.
B:“A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI” belongs to a separate Border Gateway Protocol (BGP) issue: a transit peering is moved off directly connected interface IPs to loopbacks yet the TTL and reachability design are not updated. It does not explain the condition tested here.
C:“The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged” 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.
Question 816
A Junos enterprise team investigates this incident: A fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. Which technical explanation most directly identifies the cause or design principle?
- EVPN Ethernet segment identifiers associate redundant attachments with one multihoming segment and support coordinated convergence.
- EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops.
- EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane.
- VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
Explanation
Correct Answer
D:VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic. The appropriate response is to compare VLAN-to-VNI and bridge-domain assignments on all leafs and correct them against the approved tenant map.
Incorrect Answers
A:“EVPN Ethernet segment identifiers associate redundant attachments with one multihoming segment and support coordinated convergence” belongs to a separate EVPN issue: a multihomed CE is attached to two leafs but one leaf advertises a different ESI, preventing expected redundancy behavior. It does not explain the condition tested here.
B:“EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops” belongs to a separate EVPN issue: a dual-attached Ethernet segment experiences persistent duplicates during link recovery because multihoming election or ESI state differs. It does not explain the condition tested here.
C:“EVPN Type 2 MAC/IP advertisement carries endpoint reachability and mobility information in the control plane” instead concerns another network scenario: A new endpoint MAC is learned at a remote VTEP but never reaches the receiving leaf's EVPN control-plane table. It does not address the requirement here.
Question 817
A Junos enterprise team investigates this incident: An IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement. Which technical explanation most directly identifies the cause or design principle?
- iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology.
- BGP equal-cost multipath requires appropriate configured support and matching eligible path attributes, not merely two established sessions.
- BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops.
- Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints.
Explanation
Correct Answer
C:BGP next-hop resolution must use the appropriate address family; IPv4 routes do not automatically resolve IPv6 next hops. The appropriate response is to check IPv6 next-hop reachability and inet6.0, then install a permitted IPv6 underlay route or correct next-hop policy.
Incorrect Answers
A:“iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology” belongs to a separate Border Gateway Protocol (BGP) issue: a route-reflector topology loses an iBGP-advertised prefix because clients are not configured under the intended reflector cluster. It does not explain the condition tested here.
B:“BGP equal-cost multipath requires appropriate configured support and matching eligible path attributes, not merely two established sessions” belongs to a separate Border Gateway Protocol (BGP) issue: equal candidate BGP routes are visible but no multipath forwarding entry is installed because eligibility or policy differs. It does not explain the condition tested here.
D:“Multihop BGP peerings require suitable routing to endpoint addresses and peer-session settings for nonadjacent endpoints” 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.
Question 818
Which suggested shortcut would be especially unsafe for this exact situation? A campus OSPF interface is accidentally placed in area 0 while its neighbor advertises a nonbackbone area, preventing a Full adjacency.
- Use named prefix lists and regression tests for approved and denied redistribution cases.
- Document expected external metrics and run primary/backup failover tests during policy changes.
- Include a checklist of advertised IPv6 service and loopback addresses in OSPFv3 acceptance.
- Change only router IDs while leaving the mismatched interface areas intact.
Explanation
Correct Answer
D:The tempting alternative fails because OSPF neighbors must agree on the area context to form adjacency on the common link. The supported action is to compare configured interface areas with the approved topology and put both interfaces in the intended matching area.
Incorrect Answers
A: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.
B:That prevention measure relates to an OSPF policy update redistributes a route without an appropriate external metric, shifting traffic to a slow backup.; it is not the unsafe shortcut described here.
C:That prevention measure relates to a replacement router has IPv6 OSPFv3 adjacency yet does not advertise the loopback subnet required for monitoring.; it is not the unsafe shortcut described here.
Question 819
To prevent recurrence of this precise networking failure, which practice should be adopted? A branch link should pace scheduled traffic to a slower uplink yet the team only drops excess packets abruptly.
- Plan buffer and shaping rates against provider handoff capacity and expected burst size.
- Review queue buffer tradeoffs and regression-test peak loads before tuning schedulers.
- Test classifier attachment and DSCP mappings on every access and aggregation ingress template.
- Keep a documented forwarding-class inventory and test default mappings after service changes.
Explanation
Correct Answer
A:Plan buffer and shaping rates against provider handoff capacity and expected burst size. This guards against shaping buffers and schedules outgoing traffic to a rate, unlike policing which marks or discards traffic exceeding a contract.
Incorrect Answers
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:“Test classifier attachment and DSCP mappings on every access and aggregation ingress template” belongs to a separate Class of Service (CoS) issue: a campus uplink transmits marked video as ordinary data because no behavior-aggregate classifier is attached at ingress. It does not explain the condition tested here.
D:“Keep a documented forwarding-class inventory and test default mappings after service changes” belongs to a separate Class of Service (CoS) issue: a forwarding-class configuration sends critical routing packets to a queue used for bulk backups and adjacency stability degrades under load. It does not explain the condition tested here.
Question 820
Select THREE complementary corrective, verification, or preventive controls for this scenario: A new IPv4 BGP prefix has a valid AS path but cannot become active after the IGP stops carrying its next-hop address.
- Restore permitted next-hop reachability via IGP or adjust next-hop policy where appropriate; recheck route detail.
- Append an extra deny at the end and assume it overrides a prior terminal accept.
- Use MED changes alone as guaranteed overrides of a conflicting higher local preference.
- Lower AS-path length without fixing the unreachable BGP next-hop address.
- Include next-hop reachability tests in iBGP and route-reflector deployment acceptance.
- The previously hidden BGP prefix resolves its next hop and becomes an eligible route.
Explanation
Correct Answers
A:Correction: BGP route selection first requires the BGP next hop to resolve through the appropriate routing table.
E:Prevention of recurrence: BGP route selection first requires the BGP next hop to resolve through the appropriate routing table.
F:Confirmation: Restore permitted next-hop reachability via IGP or adjust next-hop policy where appropriate; recheck route detail.
Incorrect Answers
B:“Append an extra deny at the end and assume it overrides a prior terminal accept” is an unsafe response to a different problem: a route with a permissive policy term is accepted before a later deny term can block it. It is not a valid fix here.
C:“Use MED changes alone as guaranteed overrides of a conflicting higher local preference” is an unsafe response to a different problem: an enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path. It is not a valid fix here.
D:“Lower AS-path length without fixing the unreachable BGP next-hop address” does not address BGP route selection first requires the BGP next hop to resolve through the appropriate routing table.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests