A county jail facilities team temporarily loses a contiguous path to area 0 while fiber work isolates a new OSPF area. What is the purpose of configuring an OSPF virtual link in that situation?

When a county jail facilities team temporarily loses a contiguous path to area 0 because fiber work isolates a new OSPF area, an OSPF virtual link provides a logical tunnel through a configured transit area so the disconnected area can regain backbone connectivity to area 0. The virtual link restores the architectural requirement that every area have a path to a contiguous backbone, allowing ABR relationships and inter-area flooding to resume without waiting for the physical fiber path to return. It is a contiguity bandage, not a replacement for fixing the underlay when possible—which is why that purpose statement is correct. Replacing all OSPF metrics with BGP local preference across the jail campus does not restore OSPF backbone contiguity and confuses BGP path attributes with OSPF area design. Converting every Ethernet segment into an NBMA cloud without neighbor statements neither creates backbone reachability nor addresses area isolation. Forcing totally stubby behavior on area 0 itself is invalid and irrelevant; area 0 is the backbone, not a stub, and stub flags do not heal a partitioned area. Exam caveat: virtual links require a transit area that both endpoints can reach, use router IDs as endpoints, and are generally discouraged as permanent design; exam items still expect you to know their purpose for temporary backbone repair. Operational check: configure the virtual link on both ABRs with matching area and router-ID endpoints; verify with show ip ospf virtual-links that the link is up; confirm the formerly isolated area’s ABR again shows connectivity into area 0 and inter-area routes return.