A ferry terminal runs stable single-area OSPF today and is adding a second campus that should not share a full identical LSDB with the terminal. When is introducing another normal area appropriate?
Select an answer to reveal the explanation.
Short Explanation
One ferry dock can share one clipboard; a second campus usually deserves its own clipboard tied back to the main office. Add a normal area when scale or failure domains call for it — still hung off area 0 via an ABR. One printer isn't a reason to carve areas.
Full Explanation
A ferry terminal on stable single-area OSPF should introduce another normal area when scale or failure-domain separation justifies a second campus that should not share a full identical LSDB with the terminal. The new normal area attaches through an ABR to backbone area 0 so inter-area routing remains hierarchical while each campus keeps a smaller intra-area LSDB. That is the appropriate time to expand beyond a single area—not for trivial edge changes.
Adding another area whenever a single printer joins an access VLAN is unnecessary churn; one printer does not justify multi-area redesign. Permanently disabling backbone area 0 while adding areas violates multi-area backbone rules. Replacing OSPF with static routes on every PC abandons dynamic routing rather than solving LSDB separation with a proper second area.
Exam caveat: multi-area OSPF helps when LSDB size, SPF domain, or administrative boundaries matter; small campuses often stay single-area longer. When you do split, ensure ABR attachment to area 0 (or an accepted remedial design). ENCOR emphasizes purposeful area introduction, not area sprawl for every closet.
Operational check: measure LSDB size and SPF frequency at the terminal, define the second campus area on ABRs tied to area 0, and verify Type-3 exchange without full Type-1 flooding between campuses. Confirm ferry-terminal intra-area detail stays local and the new campus failure does not force identical LSDB churn on terminal routers. Keep printer/VLAN adds inside existing areas unless a real scale or failure-domain driver appears.