JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During provider troubleshooting at Cedar Coast Telecom, this symptom is observed: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. Which targeted inspection should precede remediation?
Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges. Encapsulation overhead directly affects path MTU; a successful minimum-size tunnel ping does not prove large application packets can pass.
This check may help with another root cause, for example: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. It does not test the first failed condition; start with: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
This check may help with another root cause, for example: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. It does not test the first failed condition; start with: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
That evidence could be normal while the reported defect persists. It is aimed at: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Instead inspect: Measure underlay and tunnel MTUs, send size-controlled probes and inspect ICMP fragmentation-needed or packet captures at tunnel edges.
A production change request at Orion Transit Exchange includes this finding: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. What should the engineer change to address it?
That would address a separate configuration fault: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. This stem identifies a different cause, corrected by: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended. The case-specific reason is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular. A direct acceptance test is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
The other action is relevant when An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. The current case instead requires: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended. The distinction is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
That would address a separate configuration fault: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. This stem identifies a different cause, corrected by: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
After Orion Transit Exchange applies its proposed fix to this problem — A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. — which observation best proves the specific failure has been resolved?
That check proves something else, such as: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. It could pass while the stated problem remains. The targeted evidence here is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
This would be valid for another situation: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. It does not establish that the failing boundary in this scenario works; verify: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops. Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
That check proves something else, such as: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. It could pass while the stated problem remains. The targeted evidence here is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
An architecture review at Orion Transit Exchange examines the following symptom: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. What Junos or protocol mechanism is most directly responsible?
The statement can be true when Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. But it does not explain the reported failure. Here: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
That principle belongs to a different service stage: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. The directly relevant mechanism is: GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path.
This explains a separate protocol behavior: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. In the current facts, the controlling mechanism is: GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path.
GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path. The key distinction is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular. Accordingly the remedy is: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
The team at Orion Transit Exchange defers a fix for this condition: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. For the stated scenario, the immediate risk is: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
That consequence is more closely associated with another deficiency, such as: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. The described fault instead exposes: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
It is a risk in another topology or protocol state: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. Here the most direct failure path is: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic. The direct mitigation is: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
During provider troubleshooting at Orion Transit Exchange, this symptom is observed: A GRE tunnel's outer destination route is accidentally learned through the GRE interface itself, causing the tunnel to recursively depend on its own availability. Which targeted inspection should precede remediation?
This check may help with another root cause, for example: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. It does not test the first failed condition; start with: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices. Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
The check diagnoses a different layer of service. Its source issue is: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. The relevant initial check is: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
This check may help with another root cause, for example: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. It does not test the first failed condition; start with: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
At Baystone Energy, a service provider router shows this failure: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. What is the best targeted configuration or operations action?
The other action is relevant when A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. The current case instead requires: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended. The distinction is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
That would address a separate configuration fault: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. This stem identifies a different cause, corrected by: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
This action may apply to a different problem, for example: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. It does not repair the stated failure boundary. The case-specific reason is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended. The case-specific reason is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular. A direct acceptance test is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
A change auditor at Baystone Energy must validate remediation of this finding: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. Which test outcome is the strongest acceptance evidence?
The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops. Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
That check proves something else, such as: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. It could pass while the stated problem remains. The targeted evidence here is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
The observation confirms a different component's behavior. Its source context is: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. In this case the success criterion is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
The observation confirms a different component's behavior. Its source context is: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. In this case the success criterion is: The outer endpoint route remains stable on the real underlay while inner customer routes use the GRE interface without recursive next-hop loops.
The operations training team at Baystone Energy discusses this issue: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. Which technical explanation matches the intended correction?
The statement can be true when A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. But it does not explain the reported failure. Here: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path. The key distinction is: Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular. Accordingly the remedy is: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
That principle belongs to a different service stage: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. The directly relevant mechanism is: GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path.
This explains a separate protocol behavior: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. In the current facts, the controlling mechanism is: GRE requires an underlay path to its remote outer endpoint that is independent of the tunnel's own inner forwarding path.
At Baystone Energy, a service acceptance review considers the unresolved issue: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. Which operational exposure follows most directly?
Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic. The direct mitigation is: Ensure the GRE outer destination resolves via the physical underlay and keep inner service routes directed through the GRE interface only as intended.
That consequence is more closely associated with another deficiency, such as: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. The described fault instead exposes: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
That consequence is more closely associated with another deficiency, such as: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. The described fault instead exposes: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
It is a risk in another topology or protocol state: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. Here the most direct failure path is: Recursive resolution can bring the tunnel down or create persistent encapsulation loops and blackhole inner traffic.
Before changing configuration at Baystone Energy, an engineer investigates: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. Which first diagnostic most directly tests the suspected cause?
The check diagnoses a different layer of service. Its source issue is: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. The relevant initial check is: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
That evidence could be normal while the reported defect persists. It is aimed at: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. Instead inspect: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices. Outer endpoint transport and inner tunneled reachability are distinct routing layers; sending the underlay endpoint through its own tunnel is circular.
The check diagnoses a different layer of service. Its source issue is: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. The relevant initial check is: Inspect the outer endpoint route and recursive next hop with the tunnel enabled/disabled, then compare inner route choices.
Please check your mailbox for a message from support@examlabs.com and follow the directions.