Question 750
At a healthcare organization connecting redundant facilities, a Junos specialist investigates this scenario: An OSPF stub area receives or expects external LSA behavior incompatible with its intended design. The correction must not expose administrative network prefixes. What risk must the implementation avoid?
Explanation
Correct Answer
For a healthcare organization connecting redundant facilities, the relevant safeguard is: Do not make an ASBR-dependent area stub without checking redistribution requirements. It matters while implementing: Configure a compatible stub-area type throughout the area and validate ABR default behavior. The fault involves: A conventional stub area limits external LSAs and uses a suitable default route for outside reachability. The required acceptance result remains: Area routers learn a usable default route without inappropriate external LSAs.
Incorrect Answers
Junos first chooses active routing-table entries using protocol route preference before forwarding installation. The appropriate correction for the reported case is: Do not make an ASBR-dependent area stub without checking redistribution requirements.
Junos requires a suitable route export policy to originate eligible non-OSPFv3 routes. Fixing that different mechanism would not address the current root cause: a conventional stub area limits external LSAs and uses a suitable default route for outside reachability.
OSPF neighbors on a common link must agree on the area identifier used in Hello processing. Its verification is distinct from the reported condition: An OSPF stub area receives or expects external LSA behavior incompatible with its intended design. The correction must not expose administrative network prefixes.