Question 100
At fictional Timberline Operations, a network engineer supporting production campuses is reviewing enterprise campus, data center and SD-WAN architecture during a customer network audit (HCIP-H12-821-SOLUTIONS-025). The observed network issue is: An SDN-WAN solution diagram confuses centralized orchestration with the devices that actually forward WAN packets. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Separate controller management, control policy and forwarding-plane responsibilities in the proposed architecture. The specific reported fault is: An SDN-WAN solution diagram confuses centralized orchestration with the devices that actually forward WAN packets. Confirmation should show: Device configurations and observed traffic follow controller intent without treating the controller as universal data transit. The supporting technical principle is: SDN separates management and control orchestration from packet forwarding where the architecture permits.
Incorrect Answers
“Align VRRP preemption settings and timing with the intended maintenance policy” responds to another technical or business failure: A maintenance engineer expects a higher-priority VRRP router to take back Master instantly although preemption is disabled. That source case depends on: VRRP priority and preemption behavior are separate configured failover choices. The present issue is: An SDN-WAN solution diagram confuses centralized orchestration with the devices that actually forward WAN packets. The more direct action is “Separate controller management, control policy and forwarding-plane responsibilities in the proposed architecture” because SDN separates management and control orchestration from packet forwarding where the architecture permits.
“Design a stable routed IP underlay then add the intended VXLAN or EVPN overlay service” responds to another technical or business failure: A data center project assumes any VXLAN service works without adequate underlay IP reachability between VTEPs. That source case depends on: Overlay reachability depends on reliable underlay transport and consistent endpoint mappings. The present issue is: An SDN-WAN solution diagram confuses centralized orchestration with the devices that actually forward WAN packets. The more direct action is “Separate controller management, control policy and forwarding-plane responsibilities in the proposed architecture” because SDN separates management and control orchestration from packet forwarding where the architecture permits.
“Verify and permit authorized BGP TCP transport in both directions without exposing unrelated services” responds to another technical or business failure: A border router can ping an eBGP peer yet session establishment fails because firewall ACL blocks TCP port 179. That source case depends on: IP reachability alone does not imply that BGP TCP transport is permitted. The present issue is: An SDN-WAN solution diagram confuses centralized orchestration with the devices that actually forward WAN packets. The more direct action is “Separate controller management, control policy and forwarding-plane responsibilities in the proposed architecture” because SDN separates management and control orchestration from packet forwarding where the architecture permits.