Pass Juniper JN0-364 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Juniper JN0-364 Practice Test 44
Question 430
A fictional Junos service-provider engineer encounters this scenario: A provider extends a management segment through GRE across an IPv4 transport core, but large application packets fail while small probes succeed. Distinguishing evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
Another proposed approval would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.
A separate release decision would approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope. It does not match the current change: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.
The approval decision should consider Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The specific proposal is: Approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope. Its measurable outcome is: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.
Another proposed approval would approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.
Question 431
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: B
Another proposed action is: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. That does not directly address the observed condition: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The more targeted correction is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
The evidence for the issue is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The matching step is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. This follows the principle that IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service.
Another option proposes: Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls. The specific correction is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. The deciding evidence is: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
That alternative concerns: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. The relevant evidence is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The corresponding fix is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
Question 432
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
Another piece of evidence concerns the route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The current incident instead shows: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. This distinction supports the action: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
Another alternative would address Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter as decisive. The actual evidence in this case is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
This other option describes: Interface bundle detail shows three collecting and distributing members while one physical port is inconsistently selected or has uncorrected errors. The problem to explain is different: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
The record points to the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. After confirming the clue, the appropriate response is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
Question 433
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. Evidence for this case: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The present evidence, however, is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The relevant rule is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service.
The relevant principle is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. The case evidence is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The practical response is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
The competing option invokes: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables. Evidence for this case: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The present evidence is: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The case-relevant principle is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service.
That principle concerns another fact pattern: VRRP gateway ownership depends on priority, advertisement reception and configured preemption/tracking behavior. Evidence for this case: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design. Here the key fact is: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Question 434
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Intended bounded correction: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: C
That result would assess another condition: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete. The correct criterion is directly linked to the finding: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another proposed result is: A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold. It would not independently establish the required outcome: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
The expected outcome is the correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic. It links the scoped action to the documented condition: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
Question 435
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly. The original evidence is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer; widening the change beyond it is not justified.
This limitation concerns another setting: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface. The observed facts here make a different caution decisive: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly.
Another caution is: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements. The key risk in this case is: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly.
Another emphasis concerns: An established BGP TCP session does not guarantee every requested network layer address family is negotiated. The current change is Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints; the material limitation is Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly.
Question 436
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: B
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The case observation to isolate is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
The pre-change check should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. That check directly concerns the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The case observation to isolate is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Question 437
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: A
The case evidence indicates: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Apply the scoped action: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. Confirm its effect independently: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
An alternative plan is: First verify the observed failure (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.); review and authorize the bounded correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.); then independently verify the intended outcome (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.) before production rollout. It does not test the case-specific condition: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another possible combination is: First verify the observed failure (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.); review and authorize the bounded correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.); then independently verify the intended outcome (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.) before production rollout. The current record instead supports Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints, verified by the correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
Another potential sequence is: First verify the observed failure (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout. It has no direct link to the distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Question 438
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: B
An alternative release decision is: Observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.). It does not match the current change: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
The change-control boundary is: Observed evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), limited correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.), independently measurable result (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.). The evidence for this scope is the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another approval package concerns: Observed evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), limited correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.), independently measurable result (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.). The present scope must instead be justified by the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
An alternative release decision is: Observed evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), limited correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.), independently measurable result (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.). It does not match the current change: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
Question 439
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address. The case-specific risk is Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly. The original evidence remains: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another option proposes: Pause changes, preserve the differentiating evidence (The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.), restore the last approved safe network state and reassess gre route recursion creates a transport forwarding loop. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address.
Another fallback concerns pausing changes, preserve the differentiating evidence (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.), restore the last approved safe network state and reassess ospfv3 adjacency is healthy but destination ipv6 route is missing. The current change concerns the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
Another recovery route would pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large. It does not preserve the condition of this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The bounded fallback is: Pause changes, preserve the differentiating evidence (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.), restore the last approved safe network state and reassess gre interface is reachable only from the wrong source address.
Question 440
A fictional Junos service-provider engineer encounters this scenario: After a Junos loopback renumbering, a point-to-point GRE tunnel loses service even though routers can still ping each other's transit interfaces. Distinguishing evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: A
The bounded proposal is: Approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.
Another proposed approval would approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
A separate release decision would approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope. It does not match the current change: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.
An alternative approval would approve only the bounded change (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.) after independently checking (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer and the correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic, respectively.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 42 - 10 Questions (Last Reviewed 08-Oct-2026)
- Juniper JN0-364 Practice Test 43 - 10 Questions (Last Reviewed 07-Oct-2026)
- Juniper JN0-364 Practice Test 44 - 10 Questions (Last Reviewed 06-Oct-2026)
- Juniper JN0-364 Practice Test 45 - 10 Questions (Last Reviewed 05-Oct-2026)
- Juniper JN0-364 Practice Test 46 - 10 Questions (Last Reviewed 04-Oct-2026)