100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 150
A network change is required for the following specific situation: A multihomed CE is attached to two leafs but one leaf advertises a different ESI, preventing expected redundancy behavior. Which corrective action is most appropriate?
- Align the intended ESI and supported LAG mode, then inspect relevant EVPN Type 1 and Type 4 routes.
- Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement.
- 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
A:EVPN Ethernet segment identifiers associate redundant attachments with one multihoming segment and support coordinated convergence. Verify this by checking that both peers report a consistent Ethernet segment and failover preserves authorized connectivity.
Incorrect Answers
B:“Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement” belongs to a separate EVPN issue: a bridge domain has valid unicast Type 2 entries yet remote VTEPs do not discover a new participating segment for BUM forwarding. 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 fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. It does not explain the condition tested here.
D:“Check relevant BGP EVPN Type 2 advertisements, MAC mobility updates and import policy for the affected bridge domain” belongs to a separate EVPN issue: a host moves between leafs and the destination leaf still forwards toward the previous MAC location. It does not explain the condition tested here.
Question 151
A network change is required for the following specific situation: An aggregation network sees customer VLAN IDs collide because several tenants share the same single-tagged provider infrastructure. Which corrective action is most appropriate?
- Design supported stacked VLAN tagging and verify S-tag/C-tag placement at the correct ingress and egress.
- Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately.
- Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated.
- Inspect primary and secondary private VLAN roles and port membership; restore approved isolated/community mappings.
Explanation
Correct Answer
A:Q-in-Q encapsulation can place a provider outer tag around customer VLAN tags to isolate transport context. Verify this by checking that two customers can use overlapping inner VLAN numbers without traffic mixing on the transport.
Incorrect Answers
B:“Compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately” belongs to a separate Ethernet Switching and Spanning Tree issue: a network replacement changes VSTP root elections, causing backup links to forward for a critical VLAN. It does not explain the condition tested here.
C:“Map the trusted endpoints to the proper community secondary VLAN and keep other groups segregated” 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.
D:“Inspect primary and secondary private VLAN roles and port membership; restore approved isolated/community mappings” belongs to a separate Ethernet Switching and Spanning Tree issue: a shared guest access VLAN allows two untrusted hotel-room ports to communicate directly, violating the isolation design. It does not explain the condition tested here.
Question 152
To prevent recurrence of this precise networking failure, which practice should be adopted? A redundant L2 topology creates a broadcast storm after an edge port connected to another switch is treated as an endpoint.
- Include MVRP adjacency and registration checks in trunk-change reviews.
- Audit edge classifications and apply appropriate BPDU protection on true client-facing ports.
- Maintain representative match and nonmatch tests for filter-based VLAN policies.
- Test gateway and approved shared-service access alongside lateral isolation in PVLAN reviews.
Explanation
Correct Answer
B:Audit edge classifications and apply appropriate BPDU protection on true client-facing ports. This guards against spanning-tree edge-port assumptions are intended for non-switching endpoints, not redundant bridging connections.
Incorrect Answers
A:“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:“Maintain representative match and nonmatch tests for filter-based VLAN policies” belongs to a separate Ethernet Switching and Spanning Tree issue: a campus onboarding policy puts cameras on the normal data VLAN even though a targeted filter-based VLAN should steer them. It does not explain the condition tested here.
D:“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.
Question 153
For this case, select TWO complementary measures or outcome checks that directly resolve the problem: Customer traffic emerges with the provider service tag still attached and is rejected by an endpoint expecting ordinary Ethernet.
- Assume naming a quarantine VLAN automatically steers matching traffic without an applied filter.
- A packet capture shows the contracted customer tag or untagged frame at the endpoint.
- Use a catch-all quarantine match without analyzing which hosts also traverse the interface.
- Inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation.
- Assume every endpoint supports stacked 802.1Q tags even when the customer ordered a single-tagged handoff.
Explanation
Correct Answers
B:A packet capture shows the contracted customer tag or untagged frame at the endpoint. The specific steps required are to inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation.
D:Inspect the ingress/egress tag-processing configuration and correct the service handoff encapsulation. This addresses the dependency that Q-in-Q requires deliberate tagging and untagging at service boundaries, with customer tags retained according to the handoff contract.
Incorrect Answers
A:“Assume naming a quarantine VLAN automatically steers matching traffic without an applied filter” is an unsafe response to a different problem: a campus onboarding policy puts cameras on the normal data VLAN even though a targeted filter-based VLAN should steer them. It is not a valid fix here.
C:“Use a catch-all quarantine match without analyzing which hosts also traverse the interface” is an unsafe response to a different problem: a filter-based VLAN security design uses a rule that catches too many packets and steers legitimate devices into quarantine. It is not a valid fix here.
E:“Assume every endpoint supports stacked 802.1Q tags even when the customer ordered a single-tagged handoff” does not address Q-in-Q requires deliberate tagging and untagging at service boundaries, with customer tags retained according to the handoff contract.
Question 154
A Junos enterprise team investigates this incident: A receiver port stops getting multicast because IGMP membership was not processed by the access switch after an interface move. Which technical explanation most directly identifies the cause or design principle?
- Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root.
- 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.
- IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication.
Explanation
Correct Answer
D:IGMP reports express receiver interest, and IGMP snooping uses that interest to constrain Layer 2 replication. The appropriate response is to inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
Incorrect Answers
A:“Reverse Path Forwarding checks whether multicast packets arrive on the interface selected toward the source or tree root” 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.
B:“Policy selectors must match the intended multicast group and source ranges so unrelated services are not blocked or leaked” belongs to a separate IP Multicast issue: an edge router uses a broad multicast filter that blocks valid collaboration groups alongside restricted lab streams. It does not explain the condition tested here.
C:“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 streaming application expects a source-specific group to accept traffic from any origin, contrary to its (S,G) subscription. It does not explain the condition tested here.
Question 155
Which suggested shortcut would be especially unsafe for this exact situation? Two eBGP sessions over different transports are expected to provide ECMP but only one forwarding next hop appears.
- Use multivariable path-selection lab tests before changing MED-based policy.
- Include show route hidden and policy term hit checks in BGP troubleshooting playbooks.
- Test expected best-path behavior before modifying LOCAL_PREF across internal peers.
- Add a second BGP neighbor and assume the forwarding table automatically load-balances every route.
Explanation
Correct Answer
D:The tempting alternative fails because BGP equal-cost multipath requires appropriate configured support and matching eligible path attributes, not merely two established sessions. The supported action is to compare BGP best-path and multipath eligibility conditions, then enable approved multipath behavior and validate forwarding.
Incorrect Answers
A:That prevention measure relates to two equal LOCAL_PREF and AS-path candidates remain tied until MED influences the choice under the applicable comparison rules.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a remote prefix appears in incoming BGP updates yet never becomes active after a new route policy was applied.; it is not the unsafe shortcut described here.
C:That prevention measure relates to an enterprise chooses a different BGP exit after import policy assigns a higher local preference to the backup path.; it is not the unsafe shortcut described here.
Question 156
A network change is required for the following specific situation: A branch receives two external paths with different metric-type assumptions after a policy change and prefers the wrong exit. Which corrective action is most appropriate?
- Verify the aggregate range, component prefixes and ABR advertisements, then correct the summary policy to the approved address plan.
- Review external metric type and value at the originator, then apply the documented traffic-engineering policy.
- Inspect network type, interface priority and existing election state, then plan a controlled DR/BDR change.
- Check IPv6 link-local addressing, OSPFv3 neighbor state and relevant ICMPv6 connectivity on the actual interface.
Explanation
Correct Answer
B:OSPF external route costs and metric types affect path choice and must reflect intended topology and failover behavior. Verify this by checking that the preferred primary route wins when healthy and the backup becomes active on a controlled failure.
Incorrect Answers
A:“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.
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:“Check IPv6 link-local addressing, OSPFv3 neighbor state and relevant ICMPv6 connectivity on the actual interface” belongs to a separate Interior Gateway Protocols (IGPs) issue: an OSPFv3 adjacency on a dual-stack campus changes state because engineers treat IPv4 interface reachability as proof of IPv6 control-plane health. It does not explain the condition tested here.
Question 157
To prevent recurrence of this precise networking failure, which practice should be adopted? A streaming application expects a source-specific group to accept traffic from any origin, contrary to its (S,G) subscription.
- Include source address changes in SSM subscription-management procedures.
- Review interdomain source-advertisement scope and MSDP peer availability for ASM deployments.
- Include routed-interface PIM enrollment in the multicast deployment checklist.
- Monitor IGMP membership churn and snooping state when moving clients between VLANs.
Explanation
Correct Answer
A:Include source address changes in SSM subscription-management procedures. This guards against ASM and SSM use different membership and source-selection semantics; an SSM receiver must identify its desired sender.
Incorrect Answers
B:“Review interdomain source-advertisement scope and MSDP peer availability for ASM deployments” belongs to a separate IP Multicast issue: a multicast source is active in a different PIM domain but the local ASM RP never learns the source mapping. It does not explain the condition tested here.
C:“Include routed-interface PIM enrollment in the multicast deployment checklist” belongs to a separate IP Multicast issue: a PIM sparse-mode segment cannot maintain neighbor state because PIM is configured on the wrong routed interface. It does not explain the condition tested here.
D:“Monitor IGMP membership churn and snooping state when moving clients between VLANs” belongs to a separate IP Multicast issue: a receiver port stops getting multicast because IGMP membership was not processed by the access switch after an interface move. It does not explain the condition tested here.
Question 158
A Junos enterprise team investigates this incident: A forwarding-class configuration sends critical routing packets to a queue used for bulk backups and adjacency stability degrades under load. Which technical explanation most directly identifies the cause or design principle?
- Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings.
- Scheduler priority and bandwidth allocation affect queuing service but must balance fairness and starvation concerns.
- Forwarding classes select output queues; an incorrect class-to-queue association can cause head-of-line delays.
- Queue schedulers and buffer parameters influence service rate and delay/drop behavior at congested egress.
Explanation
Correct Answer
C:Forwarding classes select output queues; an incorrect class-to-queue association can cause head-of-line delays. The appropriate response is to review the forwarding class and queue map for control and data traffic and apply the intended assignments.
Incorrect Answers
A:“Junos egress rewrite rules map internal forwarding class and PLP back into supported packet header markings” belongs to a separate Class of Service (CoS) issue: a provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior. It does not explain the condition tested here.
B:“Scheduler priority and bandwidth allocation affect queuing service but must balance fairness and starvation concerns” belongs to a separate Class of Service (CoS) issue: two queues use the same scheduler priority, but the business expects one to always win during contention. It does not explain the condition tested here.
D:“Queue schedulers and buffer parameters influence service rate and delay/drop behavior at congested egress” 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.
Question 159
A Junos enterprise team investigates this incident: An engineer copies legacy 802.1X fallback settings to a platform whose supported feature matrix excludes them. Which technical explanation most directly identifies the cause or design principle?
- 802.1X guest and fallback capabilities are platform and Junos variant specific; unsupported features must not be assumed.
- Authentication success and postauthentication VLAN/policy assignment are separate stages whose feature support may vary.
- Captive portals presume interactive browser capabilities, making them unsuitable as the sole access method for headless devices.
- 802.1X authorization depends on the authenticator, supplicant and authentication-server conversation being correctly connected.
Explanation
Correct Answer
A:802.1X guest and fallback capabilities are platform and Junos variant specific; unsupported features must not be assumed. The appropriate response is to consult the target release's official 802.1X support matrix and adapt the authorization design to supported methods.
Incorrect Answers
B:“Authentication success and postauthentication VLAN/policy assignment are separate stages whose feature support may vary” belongs to a separate Layer 2 Authentication and Access Control issue: an EAP-compliant endpoint authenticates while the required policy attribute is absent or ignored in switch port authorization. It does not explain the condition tested here.
C:“Captive portals presume interactive browser capabilities, making them unsuitable as the sole access method for headless devices” 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:“802.1X authorization depends on the authenticator, supplicant and authentication-server conversation being correctly connected” belongs to a separate Layer 2 Authentication and Access Control issue: a campus access interface keeps a compliant supplicant blocked while EAP requests never reach the expected authentication backend. It does not explain the condition tested here.
Question 160
A Junos enterprise team investigates this incident: Two newly deployed distribution switches report identical OSPF router IDs, causing inconsistent LSAs in the area. Which technical explanation most directly identifies the cause or design principle?
- Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability.
- OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior.
- OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication.
- Local import policy can affect installed route visibility independently of the remote origination of LSAs.
Explanation
Correct Answer
B:OSPF identifies routers by unique router ID; collisions can destabilize LSDB and adjacency behavior. The appropriate response is to assign unique stable router IDs, confirm interfaces, and recheck adjacency and LSDB after controlled reconvergence.
Incorrect Answers
A:“Unrestricted OSPF export policy can originate unintended external routes, changing enterprise reachability” 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.
C:“OSPFv3 adjacency depends on participating interfaces and valid IPv6 link-local neighbor communication” 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.
D:“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.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests