A wastewater plant places remote clinics in a totally stubby OSPF area so they only need a default from the ABR. Which behavior should operators expect inside that area?
Select an answer to reveal the explanation.
Short Explanation
Totally stubby is the “just give me a default” neighborhood—the ABR hands clinics a default and keeps external and extra inter-area clutter out. Perfect for simple remote sites. They shouldn’t see the whole AS-external scrapbook.
Full Explanation
A totally stubby OSPF area allows internal routers to receive a default route from the ABR while suppressing detailed external and inter-area Type-3 routes beyond that default-injection behavior. A wastewater plant placing remote clinics in a totally stubby area so they only need a default from the ABR should expect exactly that: a default for reachability without carrying the full set of external and inter-area detail inside the clinic area. That shrinks LSDBs and CPU burden at remote civic sites.
Internal routers do not still receive all AS-external LSAs while blocking defaults—that reverses totally stubby behavior. The ABR does not flood every Internet BGP prefix as Type-5 into a totally stubby area by design. Totally stubby areas do not require EIGRP variance before OSPF defaults can be installed; variance is an EIGRP concept unrelated to OSPF area flags.
Exam caveat: if a clinic must inject a local external such as an LTE backup, an NSSA may be required instead of totally stubby; choose area type based on whether local ASBR behavior is needed. Operational check: confirm clinic routers see a default from the ABR, confirm absence of detailed Type-5 and excess Type-3 clutter as designed, and test reachability to core and Internet destinations via that default.