A company has set up a Direct Connect connection between its on-premises location and its AWS VPC. It wants to set up redundancy in case the Direct Connect connection fails. What can the company do in this regard?

Answer options:

A.Set up another Direct Connect connection.
B.Set up an IPSec VPN Connection.
C.Set up S3 connection.
D.Set up a connection via EC2 instances.

Answer – A and B
Options A and B are CORRECT because with A you can have a redundant Direct Connect setup as a backup if the main Direct Connect connection fails (even though it is an expensive solution, it will work). With B, VPN is an alternate way for the connection between AWS and on-premises infrastructure (even though the connectivity is slow, it will work).
More information on Direct Connect:
If you have established a second AWS Direct Connect connection, traffic will failover to the second link automatically. We recommend enabling Bidirectional Forwarding Detection (BFD) when configuring your connections to ensure fast detection and failover. If you have configured a backup IPsec VPN connection instead, all VPC traffic will failover to the VPN connection automatically. Traffic to/from public resources such as Amazon S3 will be routed over the Internet. If you do not have a backup AWS Direct Connect link or an IPSec VPN link, then Amazon VPC traffic will be dropped in the event of a failure. Traffic to/from public resources will be routed over the Internet.
For more information on Direct Connect FAQ’s, please visit the below URL
https://aws.amazon.com/directconnect/faqs/