A solutions architect is designing a hybrid architecture to extend an on-premises environment to AWS. The company requires a highly available connection with consistent low latency to an AWS Region, wants to minimize costs, and is willing to accept slower traffic if the primary connection fails. What should the solutions architect do?

The correct solution provisions an AWS Direct Connect connection for the primary, highly available, and low-latency connection, fulfilling the core requirements. A VPN connection serves as a cost-effective backup. While a VPN offers slower traffic compared to Direct Connect, this aligns with the company's willingness to accept slower performance during a failover scenario to minimize costs. The other options are less optimal: Two VPN tunnels would not provide the required consistent low latency for the primary connection. Two Direct Connect connections would be more expensive than a Direct Connect primary with a VPN backup, contradicting the cost minimization goal. Direct Connect does not have a "failover attribute" that automatically creates a backup connection via the AWS CLI; failover typically involves redundant physical connections or a VPN fallback.