A retail chain needs rugged in-store routers, a virtual form for its private data center, and a cloud-hosted presence in AWS for SaaS breakout. Architects must justify placement by platform strengths and limits. Which statement correctly differentiates hardware, virtual, and cloud-hosted WAN Edge options for the rollout?
Select an answer to reveal the explanation.
Short Explanation
You've got the right idea matching each edge to its home turf — it's like picking the right shoes for court, trail, and track. You'll want hardened hardware in dusty stores, elastic virtual edges in your data center, and cloud edges close to your AWS apps for fast breakout.
Full Explanation
The correct statement aligns platform capabilities with site constraints because hardened hardware provides physical ports, bypass power, LTE and tolerance for heat and dust that retail closets require, virtual instances leverage data center hypervisors for elastic CPU, high throughput and HA without new appliances, and native cloud instances instantiate inside AWS close to SaaS for direct breakout and reduced latency. Backhauling SaaS to the data center is operationally sound for centralized inspection but fails the proximity requirement because it adds latency and defeats the purpose of cloud-hosted breakout. Placing virtualized edges on store servers is a legitimate NFV design for flexible sites but fails the rugged requirement because it lacks hardened ports, environmental tolerance and hardware resiliency. Fronting the private data center with cloud-hosted edges is common for hybrid extension but fails the virtual-form requirement because the scenario explicitly mandates on-premises virtualization for scale and control. As an exam caveat, distinguish deployment location from form factor since virtual images can run in AWS yet do not provide the same operational model as cloud-native edges. As a practical check, validate port count and operating temperature for stores, hypervisor support and throughput licensing for the data center, and AWS region availability and peering for SaaS breakout before finalizing placement.