100% Latest & Updated Juniper JN0-650 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 980
A network change is required for the following specific situation: An uplink meets long-term bandwidth policy but legitimate short bursts exceed the token-bucket allowance. Which corrective action is most appropriate?
- Apply an approved behavior-aggregate classifier with the intended DSCP-to-class mapping on the real ingress interface.
- Measure burst patterns and adjust the policer burst configuration within the authorized service contract.
- Use a permitted firewall or multifield classifier matching the approved traffic fields and assign its forwarding class.
- Define a controlled rewrite map for each class and verify high-priority markings remain restricted.
Explanation
Correct Answer
B:Policing behavior depends on both committed rate and burst tolerance; a badly chosen burst parameter can penalize valid traffic. Verify this by checking that controlled traffic probes pass valid bursts without permitting sustained rate violations.
Incorrect Answers
A:“Apply an approved behavior-aggregate classifier with the intended DSCP-to-class mapping on the real ingress interface” 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.
C:“Use a permitted firewall or multifield classifier matching the approved traffic fields and assign its forwarding class” belongs to a separate Class of Service (CoS) issue: an application needs priority regardless of incoming DSCP, but an interface uses only a header-based classifier. It does not explain the condition tested here.
D:“Define a controlled rewrite map for each class and verify high-priority markings remain restricted” belongs to a separate Class of Service (CoS) issue: a customer access switch trusts external CoS bits and redistributes high-priority markings to all guest traffic. It does not explain the condition tested here.
Question 981
Select THREE complementary corrective, verification, or preventive controls for this scenario: A campus has configured forwarding classes and schedulers but one uplink carries all traffic through default service because association is missing.
- Associate the approved scheduler map with the correct egress interface and confirm class queue counters.
- Create a scheduler definition in configuration but never bind the scheduler map to egress interfaces.
- Assume any policing rule provides the same paced, buffered behavior as egress shaping.
- Validate classifier, scheduler map and interface association as a complete CoS chain.
- Trust arbitrary user DSCP markings as proof every packet belongs in the high-priority class.
- Voice traffic receives the required scheduled service at the congested egress without starving other classes.
Explanation
Correct Answers
A:Correction: Egress scheduling requires the intended schedulers and their mapping to be applied on the outgoing interface.
D:Prevention of recurrence: Egress scheduling requires the intended schedulers and their mapping to be applied on the outgoing interface.
F:Confirmation: Associate the approved scheduler map with the correct egress interface and confirm class queue counters.
Incorrect Answers
B:“Create a scheduler definition in configuration but never bind the scheduler map to egress interfaces” does not address egress scheduling requires the intended schedulers and their mapping to be applied on the outgoing interface.
C:“Assume any policing rule provides the same paced, buffered behavior as egress shaping” is an unsafe response to a different problem: a WAN customer requires smooth outbound transmission but an ingress drop policer creates unnecessary burst loss. It is not a valid fix here.
E:“Trust arbitrary user DSCP markings as proof every packet belongs in the high-priority class” is an unsafe response to a different problem: a security function needs to classify a subset of traffic by source and destination criteria rather than trusted external markings. It is not a valid fix here.
Question 982
The team believes it has resolved this Junos issue: A lab uses one primary VLAN for many tenants but isolated access ports can still exchange Layer 2 frames after a misconfiguration. Which observation best verifies the specific intended result?
- Two customers can use overlapping inner VLAN numbers without traffic mixing on the transport.
- The VLAN registration propagates to the intended downstream trunk and reaches its member ports.
- Root and forwarding roles match the approved topology under normal and failover conditions.
- Two isolated tenant ports cannot reach each other but can reach the permitted gateway uplink.
Explanation
Correct Answer
D:Two isolated tenant ports cannot reach each other but can reach the permitted gateway uplink. This checks the relevant result after inspect primary and secondary private VLAN roles and port membership; restore approved isolated/community mappings.
Incorrect Answers
A:“Two customers can use overlapping inner VLAN numbers without traffic mixing on the transport” belongs to a separate Ethernet Switching and Spanning Tree issue: a service provider must carry multiple customer VLAN IDs transparently over one metro Ethernet handoff. It does not explain the condition tested here.
B:“The VLAN registration propagates to the intended downstream trunk and reaches its member ports” 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:“Root and forwarding roles match the approved topology under normal and failover conditions” belongs to a separate Ethernet Switching and Spanning Tree issue: a switch with an unexpectedly low bridge priority becomes MSTP root and redirects aggregation traffic through an access closet. It does not explain the condition tested here.
Question 983
A network change is required for the following specific situation: An engineer copies legacy 802.1X fallback settings to a platform whose supported feature matrix excludes them. Which corrective action is most appropriate?
- Configure supported MAC RADIUS under least-privilege policy and register the device MAC with the approved service.
- Assign the authenticated device to the authorized restricted network profile and verify effective VLAN/filter.
- Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls.
- Consult the target release's official 802.1X support matrix and adapt the authorization design to supported methods.
Explanation
Correct Answer
D:802.1X guest and fallback capabilities are platform and Junos variant specific; unsupported features must not be assumed. Verify this by checking that validation shows only supported options in use and the intended access-denial/fallback behavior.
Incorrect Answers
A:“Configure supported MAC RADIUS under least-privilege policy and register the device MAC with the approved service” belongs to a separate Layer 2 Authentication and Access Control issue: a non-802.1X network printer is consistently rejected because its access port permits only EAP supplicants. It does not explain the condition tested here.
B:“Assign the authenticated device to the authorized restricted network profile and verify effective VLAN/filter” belongs to a separate Layer 2 Authentication and Access Control issue: a legacy printer can join after MAC authentication yet is allowed to reach sensitive management segments. It does not explain the condition tested here.
C:“Confirm the actual device and approved MAC record, then restrict the resulting authorization and add compensating controls” belongs to a separate Layer 2 Authentication and Access Control issue: a MAC RADIUS device changes its network adapter and can no longer authenticate because its registered identifier is stale. It does not explain the condition tested here.
Question 984
A network change is required for the following specific situation: A dual-attached Ethernet segment experiences persistent duplicates during link recovery because multihoming election or ESI state differs. Which corrective action is most appropriate?
- Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally.
- 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.
- Inspect shared ESI, DF election and Ethernet-segment routes, then correct the multihoming configuration.
Explanation
Correct Answer
D:EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops. Verify this by checking that BUM traffic follows permitted designated-forwarder behavior with no persistent looping duplicates.
Incorrect Answers
A:“Inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally” belongs to a separate EVPN issue: a fabric advertises Type 3 routes and claims this proves specific remote host MACs are reachable. It does not explain the condition tested here.
B:“Inspect Type 3 routes and VNI import/export membership; repair the intended inclusive-multicast advertisement” belongs to a separate EVPN issue: a VNI is active on two leafs but unknown-unicast or broadcast replication never reaches the remote side. 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” instead concerns another network scenario: A fabric uses conflicting VLAN-to-VNI mappings on two leaf switches, bridging different tenant segments together. It does not address the requirement here.
Question 985
Which suggested shortcut would be especially unsafe for this exact situation? A traffic policer drops small microbursts despite an acceptable average rate because its configured burst size is too tight.
- Test ingress classification separately from egress rewrite at every trust boundary.
- Validate classifier, scheduler map and interface association as a complete CoS chain.
- Document trusted-marking boundaries and test both matched and unmatched multifield traffic.
- Raise the permitted long-term traffic rate indefinitely rather than evaluating burst-size configuration.
Explanation
Correct Answer
D:The tempting alternative fails because policing behavior depends on both committed rate and burst tolerance; a badly chosen burst parameter can penalize valid traffic. The supported action is to measure burst patterns and adjust the policer burst configuration within the authorized service contract.
Incorrect Answers
A:That prevention measure relates to a provider handoff expects specific code-point markings yet a trunk rewrites every service class to default behavior.; it is not the unsafe shortcut described here.
B:That prevention measure relates to a low-latency queue is correctly classified but voice delays because its egress scheduler map is absent from the trunk.; it is not the unsafe shortcut described here.
C:That prevention measure relates to an application needs priority regardless of incoming DSCP, but an interface uses only a header-based classifier.; it is not the unsafe shortcut described here.
Question 986
To prevent recurrence of this precise networking failure, which practice should be adopted? A receiver domain requires discovery of sources known behind another RP, yet inter-RP source information exchange is absent.
- Review interdomain source-advertisement scope and MSDP peer availability for ASM deployments.
- Include source address changes in SSM subscription-management procedures.
- Test multicast source-path behavior under each failover case, not only unicast ping.
- Check multicast and unicast topology alignment whenever routing paths or metrics change.
Explanation
Correct Answer
A:Review interdomain source-advertisement scope and MSDP peer availability for ASM deployments. This guards against MSDP is used in applicable ASM inter-RP designs to exchange active-source information between rendezvous points.
Incorrect Answers
B:“Include source address changes in SSM subscription-management procedures” 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.
C:“Test multicast source-path behavior under each failover case, not only unicast ping” belongs to a separate IP Multicast issue: a redundant network changes the preferred route to the source while packets keep arriving on the other physical link. It does not explain the condition tested here.
D:“Check multicast and unicast topology alignment whenever routing paths or metrics change” 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.
Question 987
The team believes it has resolved this Junos issue: A switch with an unexpectedly low bridge priority becomes MSTP root and redirects aggregation traffic through an access closet. Which observation best verifies the specific intended result?
- Root and forwarding roles match the approved topology under normal and failover conditions.
- Isolated clients reach the shared service but cannot communicate laterally with other isolated clients.
- Two isolated tenant ports cannot reach each other but can reach the permitted gateway uplink.
- The retired VLAN disappears from unintended trunks and valid registered VLANs remain reachable.
Explanation
Correct Answer
A:Root and forwarding roles match the approved topology under normal and failover conditions. This checks the relevant result after compare bridge priority, VLAN or MSTI root and port path costs against design; adjust deliberately.
Incorrect Answers
B:“Isolated clients reach the shared service but cannot communicate laterally with other isolated clients” 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.
C:“Two isolated tenant ports cannot reach each other but can reach the permitted gateway uplink” 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.
D:“The retired VLAN disappears from unintended trunks and valid registered VLANs remain reachable” belongs to a separate Ethernet Switching and Spanning Tree issue: a campus migration removes a VLAN at the source while a trunk continues advertising it unexpectedly. It does not explain the condition tested here.
Question 988
The team believes it has resolved this Junos issue: An access VLAN floods every multicast packet because IGMP snooping state was lost during migration. Which observation best verifies the specific intended result?
- The selected upstream RPF neighbor and packet arrival interface agree, restoring intended multicast flow.
- Subscribed receivers get the stream without unnecessary flood to ports that did not join.
- RPF errors stop and the expected multicast stream reaches the subscribed downstream interfaces.
- The specified groups remain within the approved scope while unrelated enterprise multicast flows continue.
Explanation
Correct Answer
B:Subscribed receivers get the stream without unnecessary flood to ports that did not join. This checks the relevant result after inspect IGMP joins and snooping membership per VLAN and correct membership handling on the actual access ports.
Incorrect Answers
A:“The selected upstream RPF neighbor and packet arrival interface agree, restoring intended multicast flow” belongs to a separate IP Multicast issue: a campus uses a separate inet.2 multicast RPF table and investigators inspect only inet.0, overlooking a stale source route. 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:“The specified groups remain within the approved scope while unrelated enterprise multicast flows continue” belongs to a separate IP Multicast issue: a laboratory's multicast test group leaks to the corporate backbone despite a requirement to keep it within the lab. It does not explain the condition tested here.
Question 989
A network change is required for the following specific situation: A newly deployed IP phone joins the data network because the switch does not advertise the intended voice VLAN through LLDP-MED. Which corrective action is most appropriate?
- Check switch PoE budget, negotiated device requirements and per-port allocation, then rebalance or provision supported power.
- Verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media.
- Enable supported LLDP-MED network policy on the phone-facing port and verify advertisements and phone settings.
- Set supported higher PoE priority for critical voice endpoints and validate the failure budget.
Explanation
Correct Answer
C:LLDP-MED extends device discovery with telephony-related network-policy TLVs that need compatible endpoint behavior. Verify this by checking that the handset learns the authorized voice VLAN and traffic is tagged and prioritized according to design.
Incorrect Answers
A:“Check switch PoE budget, negotiated device requirements and per-port allocation, then rebalance or provision supported power” 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.
B:“Verify ingress voice classification, LLDP-MED policy and egress rewrite treatment for voice media” belongs to a separate IP Telephony Features issue: a handset follows LLDP-MED voice VLAN advertisement but sends SIP media with the wrong priority marking for the campus QoS design. It does not explain the condition tested here.
D:“Set supported higher PoE priority for critical voice endpoints and validate the failure budget” belongs to a separate IP Telephony Features issue: a switch assigns equal PoE power priority to every port and disconnects an emergency phone before low-priority signage during a power shortage. It does not explain the condition tested here.
Question 990
A Junos enterprise team investigates this incident: A fabric advertises Type 3 routes and claims this proves specific remote host MACs are reachable. Which technical explanation most directly identifies the cause or design principle?
- VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic.
- EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops.
- EVPN route types carry different information: Type 1 Ethernet auto-discovery, Type 2 MAC/IP, Type 3 inclusive multicast.
- EVPN Ethernet segment identifiers associate redundant attachments with one multihoming segment and support coordinated convergence.
Explanation
Correct Answer
C:EVPN route types carry different information: Type 1 Ethernet auto-discovery, Type 2 MAC/IP, Type 3 inclusive multicast. The appropriate response is to inspect the route type appropriate to the claimed control-plane information instead of treating all EVPN NLRIs equally.
Incorrect Answers
A:“VNI and bridge-domain mapping determines tenant overlay segmentation; misaligned mappings can misdeliver or isolate traffic” 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.
B:“EVPN multihoming uses Ethernet segment identification and designated-forwarder or split-horizon rules to avoid loops” belongs to a separate EVPN issue: an EVPN multihomed endpoint creates duplicate forwarding when two leafs both forward the same BUM traffic without appropriate split-horizon behavior. It does not explain the condition tested here.
D:“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.
Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests