100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 440
BGP remains Established and the destination is advertised, yet traffic never enters the intended MPLS label-switched path. Independently, the review flags the potentially unsafe practice “Keep forwarding indefinitely toward a withdrawn label binding”. Which validation addresses the risk without assuming a particular cause?
- Observe alternate transport path and FIB during controlled LSP loss
- Assume BGP prefix receipt alone proves label imposition in hardware
- Inspect next-hop resolution through inet.3 or appropriate transport table
- Compare BGP next hop, LSP to-address and route resolution
Explanation
Correct Answer
A:Stale labels can cause blackholes after path failure. Transport convergence must avoid persistent invalid recursion.
Incorrect Answers
B:Control-plane route receipt is not hardware label-forwarding proof.
C:BGP routes using MPLS transport need usable labeled next-hop resolution.
D:Transport endpoints must align with route recursion.
Question 441
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. The objective is to account for label header overhead. Which Junos configuration or design action best satisfies the objective?
- Include transport and service label stack overhead in the physical MTU budget
- Assume every hardware platform has unlimited label stack support
- Conclude MTU is healthy based only on tiny ICMP probes
- Raise MTU only on ingress while leaving a smaller transit hop untouched
Explanation
Correct Answer
A:Each MPLS label adds encapsulation bytes to a packet.
Incorrect Answers
B:Platform forwarding capacity is not unbounded.
C:Small pings may pass where labeled payload frames fail.
D:The limiting hop still constrains the full path.
Question 442
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. The objective is to check path MTU consistency. Which operational choice should be prioritized in this design?
- Assume MPLS labels consume zero additional packet length
- Conclude MTU is healthy based only on tiny ICMP probes
- Assume every hardware platform has unlimited label stack support
- Compare effective MTU settings across all hops in the LSP
Explanation
Correct Answer
D:One smaller transit MTU can drop otherwise valid packets.
Incorrect Answers
A:Label stacks increase frame size and can hit MTU limits.
B:Small pings may pass where labeled payload frames fail.
C:Platform forwarding capacity is not unbounded.
Question 443
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. The objective is to reproduce size-dependent failure. Which routing or switching control best fits the requirement?
- Test representative large packets with configured label treatment
- Assume MPLS labels consume zero additional packet length
- Assume every hardware platform has unlimited label stack support
- Raise MTU only on ingress while leaving a smaller transit hop untouched
Explanation
Correct Answer
A:Size sensitivity helps distinguish MTU from routing reachability.
Incorrect Answers
B:Label stacks increase frame size and can hit MTU limits.
C:Platform forwarding capacity is not unbounded.
D:The limiting hop still constrains the full path.
Question 444
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. The objective is to validate hardware support. Which verification should be performed before approving the change?
- Raise MTU only on ingress while leaving a smaller transit hop untouched
- Assume MPLS labels consume zero additional packet length
- Conclude MTU is healthy based only on tiny ICMP probes
- Check the deployed platform and interface support the required label stack depth
Explanation
Correct Answer
D:ASIC and release constraints can affect encapsulation capability.
Incorrect Answers
A:The limiting hop still constrains the full path.
B:Label stacks increase frame size and can hit MTU limits.
C:Small pings may pass where labeled payload frames fail.
Question 445
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. Two objectives apply: (1) account for label header overhead; and (2) reproduce size-dependent failure. Which TWO controls together satisfy the requirements? Choose TWO.
- Assume every hardware platform has unlimited label stack support
- Conclude MTU is healthy based only on tiny ICMP probes
- Raise MTU only on ingress while leaving a smaller transit hop untouched
- Test representative large packets with configured label treatment
- Include transport and service label stack overhead in the physical MTU budget
Explanation
Correct Answers
D:Size sensitivity helps distinguish MTU from routing reachability.
E:Each MPLS label adds encapsulation bytes to a packet.
Incorrect Answers
A:Platform forwarding capacity is not unbounded.
B:Small pings may pass where labeled payload frames fail.
C:The limiting hop still constrains the full path.
Question 446
An operator enables additional MPLS label stacking on a transport path, and small pings work while larger service packets disappear. Three objectives apply: (1) account for label header overhead; (2) check path MTU consistency; and (3) validate hardware support. Which THREE controls together satisfy the requirements? Choose THREE.
- Include transport and service label stack overhead in the physical MTU budget
- Assume every hardware platform has unlimited label stack support
- Compare effective MTU settings across all hops in the LSP
- Check the deployed platform and interface support the required label stack depth
- Conclude MTU is healthy based only on tiny ICMP probes
- Assume MPLS labels consume zero additional packet length
Explanation
Correct Answers
A:Each MPLS label adds encapsulation bytes to a packet.
C:One smaller transit MTU can drop otherwise valid packets.
D:ASIC and release constraints can affect encapsulation capability.
Incorrect Answers
B:Platform forwarding capacity is not unbounded.
E:Small pings may pass where labeled payload frames fail.
F:Label stacks increase frame size and can hit MTU limits.
Question 447
After adding a second transport label to an LSP, only large customer payloads fail across one core link with restrictive MTU. Independently, the review flags the potentially unsafe practice “Assume MPLS labels consume zero additional packet length”. Which inspection best evaluates that practice?
- Conclude MTU is healthy based only on tiny ICMP probes
- Review device feature support and label-imposition counters
- Calculate expected frame size with the actual label stack
- Inspect each core interface MTU and drop counters
Explanation
Correct Answer
C:Label stacks increase frame size and can hit MTU limits. Each MPLS label adds encapsulation bytes to a packet.
Incorrect Answers
A:Small pings may pass where labeled payload frames fail.
B:ASIC and release constraints can affect encapsulation capability.
D:One smaller transit MTU can drop otherwise valid packets.
Question 448
After adding a second transport label to an LSP, only large customer payloads fail across one core link with restrictive MTU. Independently, the review flags the potentially unsafe practice “Raise MTU only on ingress while leaving a smaller transit hop untouched”. Which evidence most directly tests the flagged assumption?
- Inspect each core interface MTU and drop counters
- Assume every hardware platform has unlimited label stack support
- Compare results for small and large encapsulated test traffic
- Calculate expected frame size with the actual label stack
Explanation
Correct Answer
A:The limiting hop still constrains the full path. One smaller transit MTU can drop otherwise valid packets.
Incorrect Answers
B:Platform forwarding capacity is not unbounded.
C:Size sensitivity helps distinguish MTU from routing reachability.
D:Each MPLS label adds encapsulation bytes to a packet.
Question 449
After adding a second transport label to an LSP, only large customer payloads fail across one core link with restrictive MTU. Independently, the review flags the potentially unsafe practice “Conclude MTU is healthy based only on tiny ICMP probes”. Which diagnostic check tests this potentially unsafe choice?
- Compare results for small and large encapsulated test traffic
- Raise MTU only on ingress while leaving a smaller transit hop untouched
- Calculate expected frame size with the actual label stack
- Review device feature support and label-imposition counters
Explanation
Correct Answer
A:Small pings may pass where labeled payload frames fail. Size sensitivity helps distinguish MTU from routing reachability.
Incorrect Answers
B:The limiting hop still constrains the full path.
C:Each MPLS label adds encapsulation bytes to a packet.
D:ASIC and release constraints can affect encapsulation capability.
Question 450
After adding a second transport label to an LSP, only large customer payloads fail across one core link with restrictive MTU. Independently, the review flags the potentially unsafe practice “Assume every hardware platform has unlimited label stack support”. Which validation addresses the risk without assuming a particular cause?
- Review device feature support and label-imposition counters
- Compare results for small and large encapsulated test traffic
- Calculate expected frame size with the actual label stack
- Raise MTU only on ingress while leaving a smaller transit hop untouched
Explanation
Correct Answer
A:Platform forwarding capacity is not unbounded. ASIC and release constraints can affect encapsulation capability.
Incorrect Answers
B:Size sensitivity helps distinguish MTU from routing reachability.
C:Each MPLS label adds encapsulation bytes to a packet.
D:The limiting hop still constrains the full path.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests