JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
Before changing configuration at Northshore Utilities, an engineer investigates: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Which first diagnostic most directly tests the suspected cause?
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 negotiated BGP families, IPv6 received/advertised paths, policy terms and next-hop reachability for inet6.
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 negotiated BGP families, IPv6 received/advertised paths, policy terms and next-hop reachability for inet6.
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: Inspect negotiated BGP families, IPv6 received/advertised paths, policy terms and next-hop reachability for inet6.
Inspect negotiated BGP families, IPv6 received/advertised paths, policy terms and next-hop reachability for inet6. BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
At Canal City University, a service provider router shows this failure: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. What is the best targeted configuration or operations action?
That would address a separate configuration fault: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. This stem identifies a different cause, corrected by: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path. The case-specific reason is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient. A direct acceptance test is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
The other action is relevant when An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. The current case instead requires: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path. The distinction is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
That would address a separate configuration fault: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. This stem identifies a different cause, corrected by: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
A change auditor at Canal City University must validate remediation of this finding: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Which test outcome is the strongest acceptance evidence?
IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises. A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
The observation confirms a different component's behavior. Its source context is: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. In this case the success criterion is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
That check proves something else, such as: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. It could pass while the stated problem remains. The targeted evidence here is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
The operations training team at Canal City University discusses this issue: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Which technical explanation matches the intended correction?
IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation. The key distinction is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient. Accordingly the remedy is: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
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: IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation.
This explains a separate protocol behavior: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. In the current facts, the controlling mechanism is: IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation.
The statement can be true when A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. But it does not explain the reported failure. Here: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
At Canal City University, a service acceptance review considers the unresolved issue: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Which operational exposure follows most directly?
The concern could occur elsewhere when An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. For the stated scenario, the immediate risk is: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint. The direct mitigation is: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
It is a risk in another topology or protocol state: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. Here the most direct failure path is: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
The concern could occur elsewhere when A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. For the stated scenario, the immediate risk is: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
Before changing configuration at Canal City University, an engineer investigates: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. Which first diagnostic most directly tests the suspected cause?
This check may help with another root cause, for example: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. It does not test the first failed condition; start with: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes. A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
The check diagnoses a different layer of service. Its source issue is: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. The relevant initial check is: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
That evidence could be normal while the reported defect persists. It is aimed at: An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. Instead inspect: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
During a Junos network change at Maple Coast Retail, the engineer observes: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Which remediation most directly fixes the described problem?
Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path. The case-specific reason is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient. A direct acceptance test is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
This action may apply to a different problem, for example: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. It does not repair the stated failure boundary. The case-specific reason is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
This action may apply to a different problem, for example: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. It does not repair the stated failure boundary. The case-specific reason is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
The other action is relevant when Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. The current case instead requires: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path. The distinction is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
The Junos team at Maple Coast Retail needs a success criterion for this defect: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Which observed result most precisely confirms the intended repair?
The observation confirms a different component's behavior. Its source context is: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. In this case the success criterion is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises. A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
The observation confirms a different component's behavior. Its source context is: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. In this case the success criterion is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
The observation confirms a different component's behavior. Its source context is: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. In this case the success criterion is: IPv6 packets traverse the IPv4-only section inside the intended tunnel, with correct decapsulation and end-to-end IPv6 reachability without fragmentation surprises.
While analyzing a service failure at Maple Coast Retail, the following is observed: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Which mechanism best explains the underlying control-plane or forwarding behavior?
This explains a separate protocol behavior: 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 the current facts, the controlling mechanism is: IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation.
IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation. The key distinction is: A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient. Accordingly the remedy is: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
This explains a separate protocol behavior: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. In the current facts, the controlling mechanism is: IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation.
This explains a separate protocol behavior: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. In the current facts, the controlling mechanism is: IPv6-in-IPv4 tunneling carries IPv6 payloads through an IPv4 transport network by adding outer IPv4 encapsulation.
The following provider defect remains uncorrected at Maple Coast Retail: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. For the stated scenario, the immediate risk is: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
The concern could occur elsewhere when An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. For the stated scenario, the immediate risk is: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
That consequence is more closely associated with another deficiency, such as: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. The described fault instead exposes: Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint.
Unaccounted encapsulation overhead and incorrect family setup can blackhole larger IPv6 packets or expose an unintended endpoint. The direct mitigation is: Create an appropriate IPv6-over-IPv4 tunnel between reachable endpoints, enabling correct IPv6 routing and MTU handling over the encapsulated path.
A support escalation at Maple Coast Retail describes: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. It does not test the first failed condition; start with: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes. A tunnel transports one protocol through another; adding IPv6 addresses to an unchanged IPv4-only transit link is not sufficient.
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: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
The check diagnoses a different layer of service. Its source issue is: 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. The relevant initial check is: Verify outer IPv4 reachability, tunnel encapsulation family, IPv6 tunnel addressing and effective path MTU using appropriately sized probes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.