100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 400
A maintenance patch accidentally loops an access segment and repeated topology changes appear in protection counters. Independently, the review flags the potentially unsafe practice “Re-enable blocked access ports without investigating recurring BPDUs”. Which validation addresses the risk without assuming a particular cause?
- Inspect protection alarm cause and recovery behavior
- Review BPDU receive counters and loop-protection state
- Disable BPDU protection on all user-facing ports to hide alerts
- Inspect protection placement relative to expected root path
Explanation
Correct Answer
A:Premature release can restore the loop threat. Protection should contain the risk and have a defined restoration path.
Incorrect Answers
B:Loop protection helps prevent erroneous forwarding after control-plane loss.
C:Ignoring unauthorized BPDUs can allow topology manipulation.
D:Root protection discourages an unexpected downstream root takeover.
Question 401
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. The objective is to identify ingress label push. Which Junos configuration or design action best satisfies the objective?
- Force every router to preserve all labels after the exit interface
- Assume every transit router must perform an IP longest-prefix lookup for each labeled packet
- Confirm an ingress label is applied for the selected forwarding equivalence class
- Declare all labeled traffic healthy from one IGP ping
Explanation
Correct Answer
C:MPLS ingress can push a label that identifies an LSP.
Incorrect Answers
A:Leaving a transport label after intended termination can break delivery.
B:Label forwarding follows label binding rather than ordinary IP lookup at every hop.
D:Plain IP reachability is not proof of label-switched forwarding.
Question 402
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. The objective is to examine transit label swap. Which operational choice should be prioritized in this design?
- Verify transit forwarding swaps the incoming label to the expected outgoing label
- Declare all labeled traffic healthy from one IGP ping
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Force every router to preserve all labels after the exit interface
Explanation
Correct Answer
A:LSRs generally map incoming labels to outgoing next-hop labels.
Incorrect Answers
B:Plain IP reachability is not proof of label-switched forwarding.
C:MPLS forwarding requires suitable label treatment at ingress.
D:Leaving a transport label after intended termination can break delivery.
Question 403
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. The objective is to understand egress label removal. Which routing or switching control best fits the requirement?
- Declare all labeled traffic healthy from one IGP ping
- Assume every transit router must perform an IP longest-prefix lookup for each labeled packet
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Check penultimate-hop popping or configured explicit-null behavior
Explanation
Correct Answer
D:Label removal before the egress affects the final forwarding step.
Incorrect Answers
A:Plain IP reachability is not proof of label-switched forwarding.
B:Label forwarding follows label binding rather than ordinary IP lookup at every hop.
C:MPLS forwarding requires suitable label treatment at ingress.
Question 404
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. The objective is to verify end-to-end LSP. Which verification should be performed before approving the change?
- Trace the selected LSP and test customer traffic across it
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Assume every transit router must perform an IP longest-prefix lookup for each labeled packet
- Force every router to preserve all labels after the exit interface
Explanation
Correct Answer
A:An LSP that appears configured may lack usable data-plane labels.
Incorrect Answers
B:MPLS forwarding requires suitable label treatment at ingress.
C:Label forwarding follows label binding rather than ordinary IP lookup at every hop.
D:Leaving a transport label after intended termination can break delivery.
Question 405
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. Two objectives apply: (1) identify ingress label push; and (2) understand egress label removal. Which TWO controls together satisfy the requirements? Choose TWO.
- Confirm an ingress label is applied for the selected forwarding equivalence class
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Force every router to preserve all labels after the exit interface
- Check penultimate-hop popping or configured explicit-null behavior
- Declare all labeled traffic healthy from one IGP ping
Explanation
Correct Answers
A:MPLS ingress can push a label that identifies an LSP.
D:Label removal before the egress affects the final forwarding step.
Incorrect Answers
B:MPLS forwarding requires suitable label treatment at ingress.
C:Leaving a transport label after intended termination can break delivery.
E:Plain IP reachability is not proof of label-switched forwarding.
Question 406
An ingress PE sends traffic across an MPLS core and operators trace labels through two transit routers toward a customer exit. Three objectives apply: (1) examine transit label swap; (2) understand egress label removal; and (3) verify end-to-end LSP. Which THREE controls together satisfy the requirements? Choose THREE.
- Assume every transit router must perform an IP longest-prefix lookup for each labeled packet
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Check penultimate-hop popping or configured explicit-null behavior
- Declare all labeled traffic healthy from one IGP ping
- Trace the selected LSP and test customer traffic across it
- Verify transit forwarding swaps the incoming label to the expected outgoing label
Explanation
Correct Answers
C:Label removal before the egress affects the final forwarding step.
E:An LSP that appears configured may lack usable data-plane labels.
F:LSRs generally map incoming labels to outgoing next-hop labels.
Incorrect Answers
A:Label forwarding follows label binding rather than ordinary IP lookup at every hop.
B:MPLS forwarding requires suitable label treatment at ingress.
D:Plain IP reachability is not proof of label-switched forwarding.
Question 407
A packet reaches the correct destination only after label processing; one transit router unexpectedly drops it following an LSP migration. Independently, the review flags the potentially unsafe practice “Assume an unlabeled packet will be label-switched without an ingress imposition”. Which inspection best evaluates that practice?
- Inspect ingress FEC and imposed label stack
- Declare all labeled traffic healthy from one IGP ping
- Inspect label pop behavior and egress packet header
- Inspect incoming-label and outgoing-label forwarding entries
Explanation
Correct Answer
A:MPLS forwarding requires suitable label treatment at ingress. MPLS ingress can push a label that identifies an LSP.
Incorrect Answers
B:Plain IP reachability is not proof of label-switched forwarding.
C:Label removal before the egress affects the final forwarding step.
D:LSRs generally map incoming labels to outgoing next-hop labels.
Question 408
A packet reaches the correct destination only after label processing; one transit router unexpectedly drops it following an LSP migration. Independently, the review flags the potentially unsafe practice “Assume every transit router must perform an IP longest-prefix lookup for each labeled packet”. Which evidence most directly tests the flagged assumption?
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Inspect label pop behavior and egress packet header
- Compare MPLS forwarding entries and customer traffic counters
- Inspect incoming-label and outgoing-label forwarding entries
Explanation
Correct Answer
D:Label forwarding follows label binding rather than ordinary IP lookup at every hop. LSRs generally map incoming labels to outgoing next-hop labels.
Incorrect Answers
A:MPLS forwarding requires suitable label treatment at ingress.
B:Label removal before the egress affects the final forwarding step.
C:An LSP that appears configured may lack usable data-plane labels.
Question 409
A packet reaches the correct destination only after label processing; one transit router unexpectedly drops it following an LSP migration. Independently, the review flags the potentially unsafe practice “Force every router to preserve all labels after the exit interface”. Which diagnostic check tests this potentially unsafe choice?
- Assume an unlabeled packet will be label-switched without an ingress imposition
- Compare MPLS forwarding entries and customer traffic counters
- Inspect incoming-label and outgoing-label forwarding entries
- Inspect label pop behavior and egress packet header
Explanation
Correct Answer
D:Leaving a transport label after intended termination can break delivery. Label removal before the egress affects the final forwarding step.
Incorrect Answers
A:MPLS forwarding requires suitable label treatment at ingress.
B:An LSP that appears configured may lack usable data-plane labels.
C:LSRs generally map incoming labels to outgoing next-hop labels.
Question 410
A packet reaches the correct destination only after label processing; one transit router unexpectedly drops it following an LSP migration. Independently, the review flags the potentially unsafe practice “Declare all labeled traffic healthy from one IGP ping”. Which validation addresses the risk without assuming a particular cause?
- Inspect label pop behavior and egress packet header
- Inspect ingress FEC and imposed label stack
- Assume every transit router must perform an IP longest-prefix lookup for each labeled packet
- Compare MPLS forwarding entries and customer traffic counters
Explanation
Correct Answer
D:Plain IP reachability is not proof of label-switched forwarding. An LSP that appears configured may lack usable data-plane labels.
Incorrect Answers
A:Label removal before the egress affects the final forwarding step.
B:MPLS ingress can push a label that identifies an LSP.
C:Label forwarding follows label binding rather than ordinary IP lookup at every hop.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests