A company validated Amazon WorkSpaces in a proof of concept and now requires high availability across two AWS Regions. WorkSpaces is deployed in a failover Region and a hosted zone exists in Amazon Route 53. What should the solutions architect configure to enable high availability for WorkSpaces across the two Regions?

The correct option enables high availability for Amazon WorkSpaces across two Regions by leveraging connection aliases and Route 53 failover routing. A connection alias is essential for directing WorkSpaces client connections to the appropriate directory. By creating a connection alias in each Region and associating it with the local directory, you ensure that WorkSpaces can be accessed from either Region. The Route 53 failover routing policy, with "Evaluate Target Health" set to "Yes," automatically directs traffic to the healthy primary alias, and switches to the secondary (failover) alias if the primary becomes unhealthy. Incorrect options: Associating both connection aliases with a directory in the primary Region would not provide regional failover for the WorkSpaces directory itself. A multivalue answer routing policy does not inherently provide failover based on health checks in the same way a failover policy does. Creating a connection alias only in the primary Region would not allow for WorkSpaces access in the failover Region. A weighted routing policy distributes traffic but doesn't provide automatic failover based on health. Associating a primary Region connection alias with a failover Region directory is an incorrect configuration and would not facilitate regional failover.