JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During provider troubleshooting at Brightwood Public Works, this symptom is observed: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. Instead inspect: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
That evidence could be normal while the reported defect persists. It is aimed at: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. Instead inspect: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
The check diagnoses a different layer of service. Its source issue is: A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. The relevant initial check is: Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state.
Inspect OSPFv3 neighbor status and IPv6 route/LSA information separately from OSPFv2 state. IPv4 OSPFv2 and IPv6 OSPFv3 control-plane adjacencies are distinct even when they share the physical link.
A production change request at Clearwater Analytics includes this finding: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. What should the engineer change to address it?
Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability. The case-specific reason is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family. A direct acceptance test is: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
This action may apply to a different problem, for example: A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. It does not repair the stated failure boundary. The case-specific reason is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
This action may apply to a different problem, for example: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. It does not repair the stated failure boundary. The case-specific reason is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
The other action is relevant when A provider migrated a tunnel endpoint to a new loopback address without updating the remote GRE destination, while physical IP connectivity still works. The current case instead requires: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability. The distinction is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
After Clearwater Analytics applies its proposed fix to this problem — An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. — which observation best proves the specific failure has been resolved?
The observation confirms a different component's behavior. Its source context is: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. In this case the success criterion is: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes. BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
This would be valid for another situation: A provider cannot run native IPv6 across an intermediate IPv4-only segment yet needs an approved IPv6 connectivity path. It does not establish that the failing boundary in this scenario works; verify: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
The observation confirms a different component's behavior. Its source context is: A static route was added for a GRE remote endpoint via the tunnel, and packets flap as the route resolves into the encapsulation path. In this case the success criterion is: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
An architecture review at Clearwater Analytics examines the following symptom: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. What Junos or protocol mechanism is most directly responsible?
This explains a separate protocol behavior: An edge has working IPv4 defaults but no IPv6 path to a remote subnet after the customer's IPv6 handoff is enabled. In the current facts, the controlling mechanism is: MP-BGP uses address-family reachability attributes to carry IPv6 prefixes; an Established BGP session does not automatically enable every address family.
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: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
MP-BGP uses address-family reachability attributes to carry IPv6 prefixes; an Established BGP session does not automatically enable every address family. The key distinction is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family. Accordingly the remedy is: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability.
This explains a separate protocol behavior: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. In the current facts, the controlling mechanism is: MP-BGP uses address-family reachability attributes to carry IPv6 prefixes; an Established BGP session does not automatically enable every address family.
The team at Clearwater Analytics defers a fix for this condition: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. What failure is most likely if no targeted control is applied?
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: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy. The direct mitigation is: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability.
That consequence is more closely associated with another deficiency, such as: An IPv6-only provider link forms an IPv4 OSPF adjacency but does not exchange any IPv6 routes because OSPFv3 was never enabled. The described fault instead exposes: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
It is a risk in another topology or protocol state: A service uses a GRE tunnel across a reduced-MTU carrier link, and oversized packets are dropped while basic ping succeeds. Here the most direct failure path is: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
During provider troubleshooting at Clearwater Analytics, this symptom is observed: An established IPv4 BGP peer exchanges inet unicast prefixes but receives no IPv6 routes because the IPv6 address family is not configured. Which targeted inspection should precede remediation?
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: 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: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. 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.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: 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 Northshore Utilities, a service provider router shows this failure: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. What is the best targeted configuration or operations action?
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: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability. The case-specific reason is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family. A direct acceptance test is: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
That would address a separate configuration fault: Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. This stem identifies a different cause, corrected by: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability.
The other action is relevant when A migration enables OSPFv3 on one transit interface but the neighbor is configured only for OSPFv2, leaving the IPv6 topology unadvertised. The current case instead requires: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability. The distinction is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
A change auditor at Northshore Utilities must validate remediation of this finding: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Which test outcome is the strongest acceptance evidence?
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: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
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 IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes. BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
This would be valid for another situation: 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. It does not establish that the failing boundary in this scenario works; verify: The IPv6 prefixes appear in the intended inet6 route table and are advertised or received with appropriate MP-BGP family and next-hop attributes.
The operations training team at Northshore Utilities discusses this issue: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Which technical explanation matches the intended correction?
MP-BGP uses address-family reachability attributes to carry IPv6 prefixes; an Established BGP session does not automatically enable every address family. The key distinction is: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family. Accordingly the remedy is: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability.
The statement can be true when Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. But it does not explain the reported failure. Here: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
The statement can be true when An IPv6 service route points to a next-hop address on the wrong logical link, while neighbor discovery succeeds on the real transit interface. But it does not explain the reported failure. Here: BGP transport/session establishment is separate from exchanging NLRI for the selected IPv6 family.
That principle belongs to a different service stage: Two remote routers intend to exchange isolated routes through GRE, but the local tunnel configuration still names the retired remote outer endpoint even though the new endpoint is reachable over the underlay. The directly relevant mechanism is: MP-BGP uses address-family reachability attributes to carry IPv6 prefixes; an Established BGP session does not automatically enable every address family.
At Northshore Utilities, a service acceptance review considers the unresolved issue: A dual-stack customer expects IPv6 routes over an existing BGP relationship, but the session negotiates only IPv4 unicast capability. Which operational exposure follows most directly?
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
The concern could occur elsewhere when Two dual-stack edges plan to transport IPv6 packets across an IPv4-only core, but the existing tunnel encapsulates the wrong protocol family. For the stated scenario, the immediate risk is: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy. The direct mitigation is: Enable and validate appropriate multiprotocol BGP IPv6-unicast family capability and import/export policy with usable IPv6 next-hop reachability.
That consequence is more closely associated with another deficiency, such as: Small GRE-tunneled packets work but larger TCP segments stall after a path change because GRE encapsulation exceeds the underlay MTU. The described fault instead exposes: IPv6 routes are absent and dual-stack service only partially works even though BGP session state appears healthy.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.