100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 350
The team believes it has resolved this Junos issue: An engineer incorrectly assumes a lower MED overrides a larger LOCAL_PREF, when both transit candidates are eligible. Which observation best verifies the specific intended result?
- The advertised set matches the documented inactive-BGP exception without changing local forwarding selection.
- The unauthorized route is rejected while intended export cases still match the proper terms.
- The chosen best path follows the documented attribute ordering rather than a single observed MED value.
- The previously hidden BGP prefix resolves its next hop and becomes an eligible route.
Explanation
Correct Answer
C:The chosen best path follows the documented attribute ordering rather than a single observed MED value. This checks the relevant result after read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence.
Incorrect Answers
A:“The advertised set matches the documented inactive-BGP exception without changing local forwarding selection” belongs to a separate Border Gateway Protocol (BGP) issue: an engineer adds advertise-inactive and downstream peers begin receiving a BGP route that loses to an OSPF route locally. It does not explain the condition tested here.
B:“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.
D:“The previously hidden BGP prefix resolves its next hop and becomes an eligible route” belongs to a separate Border Gateway Protocol (BGP) issue: a new IPv4 BGP prefix has a valid AS path but cannot become active after the IGP stops carrying its next-hop address. It does not explain the condition tested here.
Question 351
A network change is required for the following specific situation: A campus OSPF interface is accidentally placed in area 0 while its neighbor advertises a nonbackbone area, preventing a Full adjacency. Which corrective action is most appropriate?
- Compare configured interface areas with the approved topology and put both interfaces in the intended matching area.
- Inspect inet6.0 route detail and route preferences before changing OSPFv3 neighbor configuration.
- Inspect IPv6 interface addresses and OSPFv3 interface participation, then add the intended loopback advertisement within policy.
- Compare LSDB advertisements with local route policy and inet.0 state; correct the intended import filter.
Explanation
Correct Answer
A:OSPF neighbors must agree on the area context to form adjacency on the common link. Verify this by checking that OSPF neighbor state reaches Full and the expected area LSDB receives the neighbor advertisements.
Incorrect Answers
B:“Inspect inet6.0 route detail and route preferences before changing OSPFv3 neighbor configuration” 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:“Inspect IPv6 interface addresses and OSPFv3 interface participation, then add the intended loopback advertisement within policy” belongs to a separate Interior Gateway Protocols (IGPs) issue: OSPFv3 peering comes up but the desired IPv6 loopback is not in the routing database after a rollout. It does not explain the condition tested here.
D:“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: 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.
Question 352
A Junos enterprise team investigates this incident: A handset follows LLDP-MED voice VLAN advertisement but sends SIP media with the wrong priority marking for the campus QoS design. 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.
- Voice VLAN placement and CoS marking are related but separate; correct VLAN tagging does not guarantee priority handling.
- LLDP-MED location metadata can support telephony location services and must match actual switch-port placement.
- Physical PoE delivery and negotiated device power requirements must match switch and endpoint capabilities.
Explanation
Correct Answer
B:Voice VLAN placement and CoS marking are related but separate; correct VLAN tagging does not guarantee priority handling. The appropriate response is to verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media.
Incorrect Answers
A:“LLDP-MED extends device discovery with telephony-related network-policy TLVs that need compatible endpoint behavior” belongs to a separate IP Telephony Features issue: a vendor handset discovers its neighbor using basic LLDP but does not learn the configured network policy for voice tagging. It does not explain the condition tested here.
C:“LLDP-MED location metadata can support telephony location services and must match actual switch-port placement” 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:“Physical PoE delivery and negotiated device power requirements must match switch and endpoint capabilities” 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.
Question 353
A network change is required for the following specific situation: A phone's LLDP-negotiated power demand exceeds its access port's allocated PoE limit and it repeatedly restarts. Which corrective action is most appropriate?
- Enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings.
- Configure an approved voice VLAN on the port while keeping the PC data VLAN constrained.
- Inspect PoE class, per-port priority and available chassis budget, and move to a supported powered port if needed.
- Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access.
Explanation
Correct Answer
C:Physical PoE delivery and negotiated device power requirements must match switch and endpoint capabilities. Verify this by checking that the device stays powered during peak consumption and Junos reports no power-denial events.
Incorrect Answers
A:“Enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings” belongs to a separate IP Telephony Features issue: a vendor handset discovers its neighbor using basic LLDP but does not learn the configured network policy for voice tagging. It does not explain the condition tested here.
B:“Configure an approved voice VLAN on the port while keeping the PC data VLAN constrained” 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:“Review LLDP and LLDP-MED operational status and enable supported MED policy for phone access” belongs to a separate IP Telephony Features issue: a powered endpoint detects a Junos switch but fails to negotiate voice prioritization because only ordinary LLDP is enabled. It does not explain the condition tested here.
Question 354
Which suggested shortcut would be especially unsafe for this exact situation? An uplink becomes a region boundary unexpectedly after an administrator changes an MSTP configuration name on only one switch.
- Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews.
- Check policy coverage and unintended-match cases before activating filter-based steering.
- Adjust Ethernet cable speed and expect different MSTP region digests to converge automatically.
- Include MVRP adjacency and registration checks in trunk-change reviews.
Explanation
Correct Answer
C:The tempting alternative fails because MSTP region membership depends on compatible region parameters such as name, revision and VLAN-to-instance map. The supported action is to compare complete region configuration on the peers and restore the approved shared MSTP region values.
Incorrect Answers
A:That prevention measure relates to 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 is not the unsafe shortcut described here.
B:That prevention measure relates to an ingress classification filter for one terminal type inadvertently redirects other hosts using the same uplink.; it is not the unsafe shortcut described here.
D:That prevention measure relates to a new switch automatically discovers VLAN registrations on one trunk, but an intermediate trunk lacks MVRP participation and blocks the VLAN.; it is not the unsafe shortcut described here.
Question 355
The team believes it has resolved this Junos issue: An operator tries to make a remote AS prefer one inbound path using LOCAL_PREF that the remote eBGP peer never receives. Which observation best verifies the specific intended result?
- The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop.
- External peer advertisements show the intended supported attributes and inbound traffic is measured.
- The chosen best path follows the documented attribute ordering rather than a single observed MED value.
- Allowed customer prefixes are received while unauthorized longer prefixes are absent from accepted routes.
Explanation
Correct Answer
B:External peer advertisements show the intended supported attributes and inbound traffic is measured. This checks the relevant result after select a permitted inbound traffic-engineering mechanism with the provider, such as suitable AS-path prepending or agreed communities.
Incorrect Answers
A:“The IPv6 BGP route becomes eligible and forwards over an IPv6-resolvable next hop” belongs to a separate Border Gateway Protocol (BGP) issue: an IPv6 BGP peer receives a route with an unreachable IPv6 next hop despite an otherwise valid inet6 unicast advertisement. It does not explain the condition tested here.
C:“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.
D:“Allowed customer prefixes are received while unauthorized longer prefixes are absent from accepted routes” 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.
Question 356
A Junos enterprise team investigates this incident: A core node shows a missing route while remote LSDBs include the corresponding external LSA after a local policy change. Which technical explanation most directly identifies the cause or design principle?
- Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate.
- OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
- Local import policy can affect installed route visibility independently of the remote origination of LSAs.
- OSPF database-description exchange can stall when adjacent interfaces disagree on MTU even though basic Hello connectivity exists.
Explanation
Correct Answer
C:Local import policy can affect installed route visibility independently of the remote origination of LSAs. The appropriate response is to compare LSDB advertisements with local route policy and inet.0 state; correct the intended import filter.
Incorrect Answers
A:“Protocol route advertisement and active-route selection are separate; lower route preference can select a non-OSPF candidate” 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.
B:“OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior” belongs to a separate Interior Gateway Protocols (IGPs) issue: a router's OSPF neighbor restarts repeatedly because duplicate router IDs were assigned to different routing nodes. It does not explain the condition tested here.
D:“OSPF database-description exchange can stall when adjacent interfaces disagree on MTU even though basic Hello connectivity exists” belongs to a separate Interior Gateway Protocols (IGPs) issue: a core-router replacement leaves an OSPF adjacency stuck exchanging database descriptions, while the two ends have different Layer 3 MTUs. It does not explain the condition tested here.
Question 357
To prevent recurrence of this precise networking failure, which practice should be adopted? A route-reflector topology loses an iBGP-advertised prefix because clients are not configured under the intended reflector cluster.
- Include inet6-specific next-hop verification in dual-stack BGP peer checklists.
- Monitor AS-path anomalies and validate inter-AS topology changes before enabling export.
- Validate every route-reflector client and failover path in topology inventory before conversion.
- Review policy ordering with negative tests and explicit default actions on every change.
Explanation
Correct Answer
C:Validate every route-reflector client and failover path in topology inventory before conversion. This guards against iBGP-learned routes are not freely re-advertised to all iBGP neighbors without appropriate reflection or topology.
Incorrect Answers
A:“Include inet6-specific next-hop verification in dual-stack BGP peer checklists” belongs to a separate Border Gateway Protocol (BGP) issue: an IPv6 transit prefix is hidden because its next-hop address is absent from the correct IPv6 routing table. It does not explain the condition tested here.
B:“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.
D:“Review policy ordering with negative tests and explicit default actions on every change” 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 358
Select THREE complementary corrective, verification, or preventive controls for this scenario: An engineer incorrectly assumes a lower MED overrides a larger LOCAL_PREF, when both transit candidates are eligible.
- Read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence.
- Use multivariable path-selection lab tests before changing MED-based policy.
- Use only the MED field as guaranteed proof of the selected route regardless of preceding BGP attributes.
- The chosen best path follows the documented attribute ordering rather than a single observed MED value.
- Increase the route's MED while leaving BGP transport reachability and hop settings incorrect.
- Add a second BGP neighbor and assume the forwarding table automatically load-balances every route.
Explanation
Correct Answers
A:Correction: MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
B:Prevention of recurrence: MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
D:Confirmation: Read all relevant candidate attributes and apply policy consistent with intended tie-breaker precedence.
Incorrect Answers
C:“Use only the MED field as guaranteed proof of the selected route regardless of preceding BGP attributes” does not address MED has lower precedence than LOCAL_PREF and AS-path in common BGP best-path selection and must be compared under supported conditions.
E:“Increase the route's MED while leaving BGP transport reachability and hop settings incorrect” is an unsafe response to a different problem: a multihop eBGP peer uses loopback addresses but its session times out when directly connected assumptions remain. It is not a valid fix here.
F:“Add a second BGP neighbor and assume the forwarding table automatically load-balances every route” is an unsafe response to a different problem: equal candidate BGP routes are visible but no multipath forwarding entry is installed because eligibility or policy differs. It is not a valid fix here.
Question 359
To prevent recurrence of this precise networking failure, which practice should be adopted? A powered endpoint detects a Junos switch but fails to negotiate voice prioritization because only ordinary LLDP is enabled.
- Review LLDP-MED state and phone compliance during access-switch template audits.
- Test both tagged phone frames and untagged PC frames during phone-port commissioning.
- Capacity-plan PoE power classes and reserved headroom before connecting new powered devices.
- Include LLDP-MED capabilities and network-policy TLVs in phone-vendor acceptance testing.
Explanation
Correct Answer
A:Review LLDP-MED state and phone compliance during access-switch template audits. This guards against base LLDP discovery and LLDP-MED telephony advertisement are distinct capabilities and may require separate enablement.
Incorrect Answers
B:“Test both tagged phone frames and untagged PC frames during phone-port commissioning” belongs to a separate IP Telephony Features issue: a desk phone sends tagged voice traffic, but the switchport permits only the untagged data VLAN. It does not explain the condition tested here.
C:“Capacity-plan PoE power classes and reserved headroom before connecting new powered devices” belongs to a separate IP Telephony Features issue: a high-power phone intermittently reboots whenever all powered endpoints on a switch chassis start simultaneously. It does not explain the condition tested here.
D:“Include LLDP-MED capabilities and network-policy TLVs in phone-vendor acceptance testing” 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 360
The team believes it has resolved this Junos issue: An aggregation broadcast VLAN has a DR/BDR placement that conflicts with the approved design after a maintenance reboot. Which observation best verifies the specific intended result?
- The remote inet6.0 table learns the intended loopback and reachability testing succeeds.
- 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 team explains the selected active route and verifies intended failover without disturbing OSPFv3 adjacency.
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 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.
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 team explains the selected active route and verifies intended failover without disturbing OSPFv3 adjacency” belongs to a separate Interior Gateway Protocols (IGPs) issue: an IPv6 route learned through OSPFv3 is absent from the forwarding table because a more preferred static route covers the same prefix. It does not explain the condition tested here.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests