Question 880
Operations wants to avoid recurrence of this design flaw: Several SaaS applications suffer high latency when all remote-site traffic hairpins through headquarters. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Monitor service destinations, split-tunnel permissions and cloud on-ramp SLAs. This control targets the underlying design risk. Cloud on-ramp designs can reduce unnecessary backhaul but must preserve security inspection and policy controls. The follow-up acceptance check remains: Selected SaaS traffic uses the intended nearer cloud entry point with measured improved latency.
Incorrect Answers
MPLS or provider WAN integration can extend private routed connectivity toward cloud attachments where the carrier supports it. The repeat risk here is different: Cloud on-ramp designs can reduce unnecessary backhaul but must preserve security inspection and policy controls. A directly relevant preventive control is: Monitor service destinations, split-tunnel permissions and cloud on-ramp SLAs.
Dedicated cloud connectivity can provide a managed private network path, but still requires peering and physical redundancy design. The repeat risk here is different: Cloud on-ramp designs can reduce unnecessary backhaul but must preserve security inspection and policy controls. A directly relevant preventive control is: Monitor service destinations, split-tunnel permissions and cloud on-ramp SLAs.
NETCONF and RESTCONF may access YANG-modeled data but use different transport and operation encodings. The repeat risk here is different: Cloud on-ramp designs can reduce unnecessary backhaul but must preserve security inspection and policy controls. A directly relevant preventive control is: Monitor service destinations, split-tunnel permissions and cloud on-ramp SLAs.