100% Latest & Updated Juniper JN0-364 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 430
A new RSVP-TE LSP fails to signal after the operator includes a transit link with insufficient reservable bandwidth. Independently, the review flags the potentially unsafe practice “Mark the LSP Up as soon as its configuration is accepted”. Which validation addresses the risk without assuming a particular cause?
- Configure RSVP only at the ingress while all transit routers lack RSVP
- Inspect LSP operational state and reservation path
- Inspect recorded route and requested ERO for the LSP
- Inspect RSVP admission failure and TE database link bandwidth
Explanation
Correct Answer
B:A valid stanza may signal no working RSVP path. Successful LSP signaling is separate from mere configuration syntax.
Incorrect Answers
A:Missing transit signaling blocks an RSVP-TE path.
C:An ERO or CSPF policy can steer RSVP LSPs off the pure IGP shortest path.
D:Insufficient available TE resources can prevent setup.
Question 431
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. The objective is to inspect transport route resolution. Which Junos configuration or design action best satisfies the objective?
- Keep forwarding indefinitely toward a withdrawn label binding
- Assume BGP prefix receipt alone proves label imposition in hardware
- Terminate the LSP at an unrelated core router to simplify the route
- Check protocol next-hop resolution through the appropriate MPLS transport routing table
Explanation
Correct Answer
D:BGP routes using MPLS transport need usable labeled next-hop resolution.
Incorrect Answers
A:Stale labels can cause blackholes after path failure.
B:Control-plane route receipt is not hardware label-forwarding proof.
C:Wrong endpoint can send traffic away from intended PE.
Question 432
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. The objective is to verify egress LSP destination. Which operational choice should be prioritized in this design?
- Assume BGP prefix receipt alone proves label imposition in hardware
- Keep forwarding indefinitely toward a withdrawn label binding
- Ensure the LSP endpoint corresponds to the advertised service next-hop
- Assume a global default route substitutes for every missing transport LSP
Explanation
Correct Answer
C:Transport endpoints must align with route recursion.
Incorrect Answers
A:Control-plane route receipt is not hardware label-forwarding proof.
B:Stale labels can cause blackholes after path failure.
D:Generic IP reachability does not always provide the intended labeled transport.
Question 433
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. The objective is to check labeled forwarding action. Which routing or switching control best fits the requirement?
- Assume a global default route substitutes for every missing transport LSP
- Verify ingress imposes the expected transport labels for the resolved service route
- Terminate the LSP at an unrelated core router to simplify the route
- Keep forwarding indefinitely toward a withdrawn label binding
Explanation
Correct Answer
B:A resolved LSP must yield valid label push operations.
Incorrect Answers
A:Generic IP reachability does not always provide the intended labeled transport.
C:Wrong endpoint can send traffic away from intended PE.
D:Stale labels can cause blackholes after path failure.
Question 434
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. The objective is to validate fallback safely. Which verification should be performed before approving the change?
- Assume a global default route substitutes for every missing transport LSP
- Assume BGP prefix receipt alone proves label imposition in hardware
- Terminate the LSP at an unrelated core router to simplify the route
- Test failure behavior when the primary transport LSP withdraws
Explanation
Correct Answer
D:Transport convergence must avoid persistent invalid recursion.
Incorrect Answers
A:Generic IP reachability does not always provide the intended labeled transport.
B:Control-plane route receipt is not hardware label-forwarding proof.
C:Wrong endpoint can send traffic away from intended PE.
Question 435
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. Two objectives apply: (1) verify egress LSP destination; and (2) validate fallback safely. Which TWO controls together satisfy the requirements? Choose TWO.
- Assume a global default route substitutes for every missing transport LSP
- Keep forwarding indefinitely toward a withdrawn label binding
- Ensure the LSP endpoint corresponds to the advertised service next-hop
- Test failure behavior when the primary transport LSP withdraws
- Terminate the LSP at an unrelated core router to simplify the route
Explanation
Correct Answers
C:Transport endpoints must align with route recursion.
D:Transport convergence must avoid persistent invalid recursion.
Incorrect Answers
A:Generic IP reachability does not always provide the intended labeled transport.
B:Stale labels can cause blackholes after path failure.
E:Wrong endpoint can send traffic away from intended PE.
Question 436
An ingress PE receives service routes whose BGP next hops should resolve over RSVP transport LSPs, but the active LSP is missing from the transport lookup. Three objectives apply: (1) verify egress LSP destination; (2) check labeled forwarding action; and (3) validate fallback safely. Which THREE controls together satisfy the requirements? Choose THREE.
- Assume BGP prefix receipt alone proves label imposition in hardware
- Keep forwarding indefinitely toward a withdrawn label binding
- Test failure behavior when the primary transport LSP withdraws
- Verify ingress imposes the expected transport labels for the resolved service route
- Ensure the LSP endpoint corresponds to the advertised service next-hop
- Terminate the LSP at an unrelated core router to simplify the route
Explanation
Correct Answers
C:Transport convergence must avoid persistent invalid recursion.
D:A resolved LSP must yield valid label push operations.
E:Transport endpoints must align with route recursion.
Incorrect Answers
A:Control-plane route receipt is not hardware label-forwarding proof.
B:Stale labels can cause blackholes after path failure.
F:Wrong endpoint can send traffic away from intended PE.
Question 437
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 “Assume a global default route substitutes for every missing transport LSP”. Which inspection best evaluates that practice?
- Assume BGP prefix receipt alone proves label imposition in hardware
- Inspect next-hop resolution through inet.3 or appropriate transport table
- Observe alternate transport path and FIB during controlled LSP loss
- Compare BGP next hop, LSP to-address and route resolution
Explanation
Correct Answer
B:Generic IP reachability does not always provide the intended labeled transport. BGP routes using MPLS transport need usable labeled next-hop resolution.
Incorrect Answers
A:Control-plane route receipt is not hardware label-forwarding proof.
C:Transport convergence must avoid persistent invalid recursion.
D:Transport endpoints must align with route recursion.
Question 438
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 “Terminate the LSP at an unrelated core router to simplify the route”. Which evidence most directly tests the flagged assumption?
- 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
D:Wrong endpoint can send traffic away from intended PE. Transport endpoints must align with route recursion.
Incorrect Answers
A:Transport convergence must avoid persistent invalid recursion.
B:Control-plane route receipt is not hardware label-forwarding proof.
C:BGP routes using MPLS transport need usable labeled next-hop resolution.
Question 439
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 “Assume BGP prefix receipt alone proves label imposition in hardware”. Which diagnostic check tests this potentially unsafe choice?
- Inspect selected forwarding next hop and imposed MPLS label
- Inspect next-hop resolution through inet.3 or appropriate transport table
- Keep forwarding indefinitely toward a withdrawn label binding
- Compare BGP next hop, LSP to-address and route resolution
Explanation
Correct Answer
A:Control-plane route receipt is not hardware label-forwarding proof. A resolved LSP must yield valid label push operations.
Incorrect Answers
B:BGP routes using MPLS transport need usable labeled next-hop resolution.
C:Stale labels can cause blackholes after path failure.
D:Transport endpoints must align with route recursion.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests