Question #1015
A company is expanding their Amazon WorkSpaces deployment to ensure high availability across two AWS Regions. They have deployed WorkSpaces in a secondary Region for failover and set up a hosted zone in Amazon Route 53. What should the solutions architect do to configure high availability for the solution?
Create a connection alias in the primary Region and in the failover Region. Associate the connection aliases with a directory in each Region. Create a Route 53 failover routing policy. Set Evaluate Target Health to Yes.
Create a connection alias in the primary Region and in the failover Region. Associate the connection aliases with a directory in the primary Region. Create a Route 53 geolocation routing policy.
Create a connection alias in the primary Region. Associate the connection alias with a directory in the primary Region. Create a Route 53 latency routing policy. Set Evaluate Target Health to No.
Create a connection alias in the primary Region. Associate the connection alias with a directory in the failover Region. Create a Route 53 failover routing policy. Set Evaluate Target Health to No.
Explanation
The correct answer is A. To achieve high availability for Amazon WorkSpaces across two AWS Regions:
1. Connection Aliases: Create a connection alias in both the primary and failover Regions. Each alias must be associated with its respective directory (one per Region) to allow users to connect seamlessly using the same alias.
2. Route 53 Failover Policy: Configure a Route 53 failover routing policy with two records: a primary record pointing to the primary Region's alias and a secondary record for the failover Region. Setting 'Evaluate Target Health' to 'Yes' ensures Route 53 automatically redirects traffic to the secondary Region if the primary becomes unhealthy.
Why Other Options Are Incorrect:
- B: Associating both aliases with the primary Region's directory defeats the purpose of failover. Geolocation routing does not handle failover scenarios.
- C: A latency routing policy optimizes for performance, not failover. Using only one connection alias in the primary Region ignores the secondary Region's setup.
- D: Associating the primary Region's alias with the failover Region's directory is incorrect, as aliases must point to their local directories.
Key Points:
- Use connection aliases per Region with local directories.
- Route 53 failover routing with health checks ensures automatic regional failover.
Answer
The correct answer is: A