100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 1040
The team believes it has resolved this Junos issue: A BGP export policy advertises a prefix that exists only as an inactive local candidate, despite an expectation of default active-only behavior. Which observation best verifies the specific intended result?
- The advertised set matches the documented inactive-BGP exception without changing local forwarding selection.
- After policy correction, chosen path and attribute ordering match documented routing intent.
- The route is accepted only after the AS-path loop is removed, with stable forwarding.
- A loopback-to-loopback BGP session becomes Established and exchanges only permitted NLRI.
Explanation
Correct Answer
A:The advertised set matches the documented inactive-BGP exception without changing local forwarding selection. This checks the relevant result after inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
Incorrect Answers
B:“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.
C:“The route is accepted only after the AS-path loop is removed, with stable forwarding” belongs to a separate Border Gateway Protocol (BGP) issue: a carrier changes an upstream routing arrangement and a downstream Junos router detects its own AS in the advertised AS path. It does not explain the condition tested here.
D:“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.
Question 1041
Select THREE complementary corrective, verification, or preventive controls for this scenario: A branch egress rewriter incorrectly gives bulk backups the same DSCP as real-time voice.
- Configure egress rewriting alone and assume it classifies all incoming traffic into voice queues.
- Audit DSCP preservation and remarking at untrusted edge boundaries.
- Assume any policing rule provides the same paced, buffered behavior as egress shaping.
- Let all untrusted clients self-select expedited forwarding marks without verification.
- Only approved media streams leave with high-priority code points; backup traffic uses its designated mark.
- Define a controlled rewrite map for each class and verify high-priority markings remain restricted.
Explanation
Correct Answers
B:Prevention of recurrence: CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings.
E:Confirmation: Define a controlled rewrite map for each class and verify high-priority markings remain restricted.
F:Correction: CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings.
Incorrect Answers
A:“Configure egress rewriting alone and assume it classifies all incoming traffic into voice queues” is an unsafe response to a different problem: voice packets arrive with DSCP EF but are placed into the best-effort queue after a new access interface template is applied. It is not a valid fix here.
C:“Assume any policing rule provides the same paced, buffered behavior as egress shaping” is an unsafe response to a different problem: a branch link should pace scheduled traffic to a slower uplink yet the team only drops excess packets abruptly. It is not a valid fix here.
D:“Let all untrusted clients self-select expedited forwarding marks without verification” does not address CoS rewrite must reflect trusted classifications and intended forwarding policy, not arbitrary source markings.
Question 1042
A network change is required for the following specific situation: A host moves between leafs and the destination leaf still forwards toward the previous MAC location. Which corrective action is most appropriate?
- Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration.
- 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.
- Check relevant BGP EVPN Type 2 advertisements, MAC mobility updates and import policy for the affected bridge domain.
Explanation
Correct Answer
D: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
A:“Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration” 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.
B:“Repair authorized underlay routing to remote VTEPs and check tunnel reachability before changing EVPN policies” 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.
C:“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 campus extension carries the right VXLAN outer header but directs frames to the wrong tenant bridge domain due to bad VNI mapping. It does not explain the condition tested here.
Question 1043
The team believes it has resolved this Junos issue: An IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement. Which observation best verifies the specific intended result?
- The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop.
- After policy correction, chosen path and attribute ordering match documented routing intent.
- The downstream client learns approved prefixes and cluster-loop checks remain operational.
- The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged.
Explanation
Correct Answer
A: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
B:“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.
C:“The downstream client learns approved prefixes and cluster-loop checks remain operational” 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:“The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged” belongs to a separate Border Gateway Protocol (BGP) issue: a campus router's BGP IPv6 session is Established yet peers advertise only inet unicast family routes. It does not explain the condition tested here.
Question 1044
The team believes it has resolved this Junos issue: An engineer adds advertise-inactive and downstream peers begin receiving a BGP route that loses to an OSPF route locally. Which observation best verifies the specific intended result?
- The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged.
- The selected BGP route reflects the intended higher LOCAL_PREF, and traceroute follows the approved exit.
- The unauthorized route is rejected while intended export cases still match the proper terms.
- The advertised set matches the documented inactive-BGP exception without changing local forwarding selection.
Explanation
Correct Answer
D:The advertised set matches the documented inactive-BGP exception without changing local forwarding selection. This checks the relevant result after inspect active-route selection and the advertise-inactive configuration; keep it only if the external requirement justifies it.
Incorrect Answers
A:“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.
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: 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.
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 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 1045
To prevent recurrence of this precise networking failure, which practice should be adopted? A printer's MAC address is duplicated by an unauthorized endpoint that obtains the same weak MAC-based policy.
- Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions.
- Test captive-portal redirects, session expiry and post-login VLAN access in guest-network acceptance.
- Classify interactive and headless endpoint requirements before choosing the access method.
- Separate EAP silence, reject and timeout counters in authentication operational monitoring.
Explanation
Correct Answer
A:Require inventory ownership and anomaly monitoring for MAC RADIUS exceptions. This guards against MAC-based identity is tied to the observed hardware address and can be spoofed; it is not strong user authentication.
Incorrect Answers
B:“Test captive-portal redirects, session expiry and post-login VLAN access in guest-network acceptance” 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:“Classify interactive and headless endpoint requirements before choosing the access method” belongs to a separate Layer 2 Authentication and Access Control issue: a noninteractive sensor is trapped in captive-portal onboarding because operators selected browser authentication for all endpoints. It does not explain the condition tested here.
D:“Separate EAP silence, reject and timeout counters in authentication operational monitoring” 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.
Question 1046
The team believes it has resolved this Junos issue: An application needs priority regardless of incoming DSCP, but an interface uses only a header-based classifier. Which observation best verifies the specific intended result?
- Voice traffic receives the required scheduled service at the congested egress without starving other classes.
- Queue depth, latency and drop statistics meet documented objectives during realistic traffic load.
- Only traffic meeting the defined match receives the intended queue and packet loss priority.
- Measured guest ingress usage remains within policy and permitted business traffic is unaffected.
Explanation
Correct Answer
C:Only traffic meeting the defined match receives the intended queue and packet loss priority. This checks the relevant result after use a permitted firewall or multifield classifier matching the approved traffic fields and assign its forwarding class.
Incorrect Answers
A:“Voice traffic receives the required scheduled service at the congested egress without starving other classes” 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:“Queue depth, latency and drop statistics meet documented objectives during realistic traffic load” 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.
D:“Measured guest ingress usage remains within policy and permitted business traffic is unaffected” belongs to a separate Class of Service (CoS) issue: a branch wants to enforce a traffic contract on an incoming service flow yet applies policing to an unrelated egress path. It does not explain the condition tested here.
Question 1047
The team believes it has resolved this Junos issue: An edge router uses a broad multicast filter that blocks valid collaboration groups alongside restricted lab streams. Which observation best verifies the specific intended result?
- A failure of one RP does not strand subscribers and remaining RPs maintain correct multicast source awareness.
- Restricted groups are stopped at the boundary while approved collaboration streams still reach subscribers.
- RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
- PIM joins build the intended shared tree and the requested group begins forwarding to subscribers.
Explanation
Correct Answer
B:Restricted groups are stopped at the boundary while approved collaboration streams still reach subscribers. This checks the relevant result after refine the relevant multicast policy ranges and inspect forwarding for both permitted and denied groups.
Incorrect Answers
A:“A failure of one RP does not strand subscribers and remaining RPs maintain correct multicast source awareness” 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.
C:“RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces” 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:“PIM joins build the intended shared tree and the requested group begins forwarding to subscribers” belongs to a separate IP Multicast issue: a PIM sparse-mode receiver has an IGMP join but no multicast traffic because its upstream router cannot resolve the rendezvous point. It does not explain the condition tested here.
Question 1048
The team believes it has resolved this Junos issue: A shared multiaccess segment elects an undesired OSPF DR after new routers are connected, and control-plane load rises. Which observation best verifies the specific intended result?
- The expected prefix becomes active locally while unwanted external prefixes remain filtered.
- Neighbor states and DR/BDR assignments match the approved design following a managed election.
- Only authorized static prefixes appear as OSPF externals; management prefixes remain local.
- The remote inet6.0 table learns the intended loopback and reachability testing succeeds.
Explanation
Correct Answer
B:Neighbor states and DR/BDR assignments match the approved design following a managed election. This checks the relevant result after inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change.
Incorrect Answers
A:“The expected prefix becomes active locally while unwanted external prefixes remain filtered” 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:“Only authorized static prefixes appear as OSPF externals; management prefixes remain local” 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.
D:“The remote inet6.0 table learns the intended loopback and reachability testing succeeds” belongs to a separate Interior Gateway Protocols (IGPs) issue: a replacement router has IPv6 OSPFv3 adjacency yet does not advertise the loopback subnet required for monitoring. It does not explain the condition tested here.
Question 1049
Select THREE complementary corrective, verification, or preventive controls for this scenario: A campus router's BGP IPv6 session is Established yet peers advertise only inet unicast family routes.
- Validate all required BGP address families during dual-stack peer commissioning.
- Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated.
- Assume TCP session Established proves every learned prefix has a usable forwarding next hop.
- Enable the intended inet6 family consistently on eligible BGP peers and verify route policy and inet6.0.
- The expected IPv6 prefix is received in inet6.0 while IPv4 route exchange remains unchanged.
- Assume the shortest AS path must win regardless of any LOCAL_PREF difference.
Explanation
Correct Answers
A:Prevention of recurrence: BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state.
D:Correction: BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state.
E:Confirmation: Enable the intended inet6 family consistently on eligible BGP peers and verify route policy and inet6.0.
Incorrect Answers
B:“Assume successful inet IPv4 routes imply that IPv6 NLRI is already negotiated” does not address BGP address-family negotiation controls which IPv4 or IPv6 NLRI can be exchanged independently of session state.
C:“Assume TCP session Established proves every learned prefix has a usable forwarding next hop” is an unsafe response to a different problem: an iBGP egress advertisement forwards a transit next hop that branch routers cannot resolve, creating traffic blackholes. It is not a valid fix here.
F:“Assume the shortest AS path must win regardless of any LOCAL_PREF difference” is an unsafe response to a different problem: a branch dual-transit design sees the higher-preference provider route win even though its AS path has more hops. It is not a valid fix here.
Question 1050
To prevent recurrence of this precise networking failure, which practice should be adopted? Two equal LOCAL_PREF and AS-path candidates remain tied until MED influences the choice under the applicable comparison rules.
- Distinguish internal exit selection from inbound inter-AS path influence in routing design reviews.
- Track every BGP advertise-inactive exception and test cross-protocol route selection.
- Use multivariable path-selection lab tests before changing MED-based policy.
- Monitor AS-path anomalies and validate inter-AS topology changes before enabling export.
Explanation
Correct Answer
C:Use multivariable path-selection lab tests before changing MED-based policy. This guards against MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
Incorrect Answers
A:“Distinguish internal exit selection from inbound inter-AS path influence in routing design reviews” 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.
B:“Track every BGP advertise-inactive exception and test cross-protocol route selection” 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.
D:“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.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests