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 45
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.
Question 441
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: D
Another proposed action is: Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints. That does not directly address the observed condition: 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 more targeted correction is: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
Another proposed action is: Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family. It targets a different dependency; the evidence here is 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.
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: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. The deciding evidence is: 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 evidence for the issue is 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 matching step is: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. This follows the principle that the tunnel transport endpoint route must not depend recursively on the same tunnel it enables.
Question 442
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: C
This other option describes: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The problem to explain is different: 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.
Another proposed finding is: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design. It is not the recorded discriminator, which is 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.
Consider this 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 applicable explanation is: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables. The matching response is: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
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 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.
Question 443
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
The competing option invokes: GR, GRES and NSR address different aspects of routing and Routing Engine continuity and must be separately verified. Evidence for this case: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization. The present evidence is: 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-relevant principle is: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables.
The tunnel transport endpoint route must not depend recursively on the same tunnel it enables. This distinction accounts for 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; another unrelated mechanism would not address the same condition.
A different principle is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for 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 present evidence, however, is 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 relevant rule is: The tunnel transport endpoint route must not depend recursively on the same tunnel it enables.
This alternative invokes: 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 governing distinction for the recorded case is the tunnel transport endpoint route must not depend recursively on the same tunnel it enables.
Question 444
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Intended bounded correction: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: D
A different option checks: Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path. The case-specific acceptance condition is instead the GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
That result would assess another condition: Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped. The correct criterion is directly linked to the finding: 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 GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete. This verifies the required result rather than merely stating the action; the original issue was 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.
Question 445
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
Another caution is: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface. The key risk in this case is: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements.
Another emphasis concerns: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint. The current change is Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately; the material limitation is Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements.
The risk to retain is: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements. The original evidence is 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; widening the change beyond it is not justified.
Another caution is: Successful ordinary IP ping between routers does not prove the tunnel encapsulation source is still configured correctly. The key risk in this case is: Tunnel endpoint recursion can create a forwarding loop and total outage despite syntactically valid tunnel and route statements.
Question 446
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
That check concerns a different signal: 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-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization. The case observation to isolate is 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 focused check here is: 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.
Another investigation would 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. It does not directly establish the reported condition: 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 pre-change check should 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. That check directly 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.
Question 447
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: C
Another possible combination 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. The current record instead supports Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately, verified by the GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
Another potential sequence is: First verify the observed failure (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.); review and authorize the bounded correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.); then independently verify the intended outcome (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.) before production rollout. It has no direct link to the distinguishing 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 evidence indicates: 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. Apply the scoped action: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately. Confirm its effect independently: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
An alternative plan is: First verify the observed failure (The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.); review and authorize the bounded correction (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.); then independently verify the intended outcome (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.) before production rollout. It does not test the case-specific condition: 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.
Question 448
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The change-control boundary 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.). The evidence for this scope is 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.
An alternative release decision is: Observed evidence (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.), limited correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.), independently measurable result (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.). It does not match the current change: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
Another approval action is: 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 relevant evidence and acceptance are 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 and the GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete, respectively.
Another approval package concerns: 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 present scope must instead be justified by 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.
Question 449
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: D
Another fallback concerns pausing 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 current change 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.
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 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 bounded fallback is: 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.
Another option proposes: Pause changes, preserve the differentiating evidence (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), restore the last approved safe network state and reassess ipv6 bgp family activation is omitted on a dual-stack peer. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
A contingency plan would 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. This preserves control of the change linked to 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.
Question 450
A fictional Junos service-provider engineer encounters this scenario: A new static route to a GRE tunnel remote endpoint accidentally resolves through the same GRE tunnel interface meant to reach that endpoint. Distinguishing 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. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: C
A separate release decision would approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope. It does not match the current change: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
An alternative 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 relevant evidence and acceptance are 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 and the GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete, respectively.
The bounded proposal is: 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 separate acceptance measure remains: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
A separate release decision 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. It does not match the current change: Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- 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)
- Juniper JN0-364 Practice Test 47 - 10 Questions (Last Reviewed 03-Oct-2026)