City finance flags operational complexity before purchasing SD-WAN controllers. Which limitation should architects acknowledge at principle depth?
Select an answer to reveal the explanation.
Short Explanation
Smart systems still need drivers. Controllers and new ops workflows are real costs—finance is right to ask. Benefits are great; pretending complexity is zero is marketing, not ENCOR.
Full Explanation
City finance flagging operational complexity before purchasing SD-WAN controllers is correctly answered by acknowledging that SD-WAN introduces controller dependency and operational learning compared with a purely static traditional WAN mindset. Benefits are real, but architects must budget for orchestration platforms, new troubleshooting skills, certificate and control-connection health, policy lifecycle, and change-management discipline. Pretending complexity is zero is marketing, not ENCOR principle depth. Municipal buyers should treat controllers as production dependencies with HA, backups, and staff training—not optional dashboards.
Claiming SD-WAN overlays remove any need for IP addressing on WAN edges is false. Guaranteeing unlimited throughput with zero monitoring tools is false. Saying limitations include mandatory removal of all branch firewalls worldwide is not a recognized SD-WAN limitation and misstates security design.
Exam caveat: Known limitations include controller dependency and operational complexity—not removal of IP addresses, firewalls, or monitoring.
Operational check: present finance with training, controller HA, and monitoring costs alongside bandwidth savings; pilot one clinic to measure actual ops overhead before a county-wide purchase commitment.