Question 150
At fictional Granite Logistics, an HPE edge-to-cloud solution architect supporting distribution applications is assessing HPE end-to-end architecture and integration during an infrastructure scaling exercise (HPE-HPE0-V27-DESIGN-038). The reported customer challenge is: A multi-site customer expects branch traffic to stay local even though default routes send all sessions through headquarters. Which customer-focused architecture or engineering action most directly addresses the situation?
Explanation
Correct Answer
The most directly responsive action is: Design appropriate local breakout and application-specific SD-WAN routing policies. The specific customer situation is: A multi-site customer expects branch traffic to stay local even though default routes send all sessions through headquarters. The expected validation is: Branch-local transactions continue during an induced headquarters tunnel outage. The governing architecture or business principle is: Application path placement should follow business intent and transport reliability.
Incorrect Answers
“Design VRFs and policy-controlled intertenant route exchange” supports the separate task “Design VRFs and policy-controlled intertenant route exchange”, not the reported problem: a multi-site customer expects branch traffic to stay local even though default routes send all sessions through headquarters. This case instead calls for “Design appropriate local breakout and application-specific SD-WAN routing policies”.
“Define supported mobility, SSID-to-VLAN and identity policy for user movement” concerns the separate step “Define supported mobility, SSID-to-VLAN and identity policy for user movement”. The reported issue is that a multi-site customer expects branch traffic to stay local even though default routes send all sessions through headquarters, so the direct response is to design appropriate local breakout and application-specific SD-WAN routing policies.
“Distribute name-resolution and external routing dependencies across planned fault domains” concerns the alternative task “Distribute name-resolution and external routing dependencies across planned fault domains”, but the stated failure is that a multi-site customer expects branch traffic to stay local even though default routes send all sessions through headquarters. The required measure is to design appropriate local breakout and application-specific SD-WAN routing policies.