Question 280
The HPE AOS-CX switching case is: A distribution route is accepted from a neighbor but the return route is missing in another routing domain. Select TWO: a corrective switching action and separate evidence that the correction worked. (Select TWO.)
Explanation
Correct Answers
The targeted correction for A distribution route is accepted from a neighbor but the return route is missing in another routing domain is: Establish compatible OSPF process, area, interface and adjacency parameters before relying on dynamic campus route convergence. It reduces the risk that an OSPF neighbor mismatch can leave a physical link working while required prefixes never populate the routing table.
A separate operational validation for A distribution route is accepted from a neighbor but the return route is missing in another routing domain is: Peer neighbor state reaches the expected adjacency and learned routes survive an approved uplink failure test. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns bgp peering and route policy boundaries; its associated risk is: An established BGP session does not by itself prove that correct prefixes are advertised or accepted without leaks. The observed case A distribution route is accepted from a neighbor but the return route is missing in another routing domain requires the more specific ospf area and neighbor formation control. The targeted action is: Establish compatible OSPF process, area, interface and adjacency parameters before relying on dynamic campus route convergence.
This alternative concerns vrf segmentation and route leaking control; its associated risk is: Treating VRFs as one shared table can leak restricted networks or leave permitted traffic with no route. The observed case A distribution route is accepted from a neighbor but the return route is missing in another routing domain requires the more specific ospf area and neighbor formation control. The targeted action is: Establish compatible OSPF process, area, interface and adjacency parameters before relying on dynamic campus route convergence.
This alternative concerns vsx active gateway and distributed forwarding; its associated risk is: Inconsistent virtual gateways or failed peer topology can cause duplicate-gateway confusion and asymmetric forwarding. The observed case A distribution route is accepted from a neighbor but the return route is missing in another routing domain requires the more specific ospf area and neighbor formation control. The targeted action is: Establish compatible OSPF process, area, interface and adjacency parameters before relying on dynamic campus route convergence.