Question 430
At Harbor Civic, an infrastructure review by the government network operations team is evaluating citizen service reachability across a county-service branch network while testing an alternate WAN provider (FT-B-15-03). The review finds that hundreds of branches use manually maintained peer addresses and create inconsistent overlay settings. Any correction must respect this operating requirement: case data must remain within approved agency boundaries. Which architectural or operational principle best explains the appropriate correction?
Explanation
Correct Answer
The relevant design principle is: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics. In this citizen service reachability decision, the control is assessed using observable network or policy state, not the engineer's assumption. The failure is that hundreds of branches use manually maintained peer addresses and create inconsistent overlay settings; the intended approach is to adopt approved scalable FortiManager templates with shared overlay design and site-specific identity. The distinguishing confirmation is that A new branch forms the intended hub tunnels without per-peer manual configuration drift.
Incorrect Answers
The source case reports that hundreds of branches use manually maintained peer addresses and create inconsistent overlay settings. The proposed explanation concerns: Overlay redundancy requires backup control-plane and data-plane continuity. The reported symptom instead follows: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics; separate observed path selection from configuration intent.
The source case reports that hundreds of branches use manually maintained peer addresses and create inconsistent overlay settings. The alternative states a real but different technical principle: Loopback-based routing can decouple control-plane identity from one underlay interface; consider the specific security and routing boundary. The facts in this question are explained by: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics; separate observed path selection from configuration intent.
The source case reports that hundreds of branches use manually maintained peer addresses and create inconsistent overlay settings. That principle controls the offered alternative: Application-aware and internet-service matching can be more stable than static cloud IP lists; avoid assuming a healthy session proves all services work. It is not the causal distinction established here: Parameterized overlay deployment reduces duplicated manual configuration in large fabrics; separate observed path selection from configuration intent.