Question 470
At Riverside Building, a campus route policy should treat tagged partner prefixes differently from ordinary routes. Which AOS-CX or Aruba networking design choice resolves this specific dependency?
Explanation
Correct Answer
For Riverside Building, the decisive mechanism is BGP community route policy. BGP communities are policy labels requiring an explicit matching route policy. Match the approved BGP community in a route map and apply the correct import/export action establishes the needed configuration in the case rather than merely measuring a symptom.
Incorrect Answers
This is relevant to OSPF network type, where oSPF network type affects hello behavior and DR election on multiaccess segments In the Riverside Building case, Changing that neighboring feature does not implement the missing function. The specific mechanism is bGP communities are policy labels requiring an explicit matching route policy
This is relevant to OSPF hello and dead timers, where oSPF timer mismatches can prevent reliable adjacency even when IP connectivity exists In the Riverside Building case, Changing that neighboring feature does not implement the missing function. The specific mechanism is bGP communities are policy labels requiring an explicit matching route policy
This is relevant to OSPF area membership, where oSPF neighbors on a link must agree on essential area and protocol parameters In the Riverside Building case, Changing that neighboring feature does not implement the missing function. The specific mechanism is bGP communities are policy labels requiring an explicit matching route policy