Question 500
At a healthcare organization connecting redundant facilities, a Junos specialist investigates this scenario: An IPv6 static prefix is installed locally but not redistributed to the OSPFv3 domain. The correction must not expose administrative network prefixes. Which limitation should guide the change control?
Explanation
Correct Answer
For a healthcare organization connecting redundant facilities, the relevant safeguard is: Check address families and filtering carefully to avoid importing every static IPv6 route. It matters while implementing: Match the intended IPv6 static route in a scoped export policy under the OSPFv3 process. The fault involves: Junos requires a suitable route export policy to originate eligible non-OSPFv3 routes. The required acceptance result remains: Other OSPFv3 routers learn the specified external IPv6 prefix without unrelated statics.
Incorrect Answers
OSPF interarea summary-LSA generation can be governed with supported routing policies on ABRs. The appropriate correction for the reported case is: Check address families and filtering carefully to avoid importing every static IPv6 route.
OSPF automatic cost derives from reference bandwidth, which must be planned consistently in the domain. Fixing that different mechanism would not address the current root cause: junos requires a suitable route export policy to originate eligible non-OSPFv3 routes.
Neighbor compatibility depends on matching Hello and dead intervals for the participating link. Its verification is distinct from the reported condition: An IPv6 static prefix is installed locally but not redistributed to the OSPFv3 domain. The correction must not expose administrative network prefixes.