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 multivalue answer 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 weighted routing policy.
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 Yes.
Explanations:
This option creates connection aliases in both the primary and failover Regions, ensuring that WorkSpaces are accessible from either region. By associating each connection alias with its respective directory and setting up a Route 53 failover routing policy with Evaluate Target Health set to Yes, it allows for automatic failover to the standby region when the primary is unavailable, achieving high availability.
While this option creates connection aliases in both regions, associating both aliases with the directory in the primary Region does not provide a failover mechanism. The Route 53 multivalue answer routing policy does not allow for true failover, as it merely provides multiple responses, but does not monitor the health of the endpoints.
This option only creates a connection alias in the primary Region and associates it with a directory there, lacking any high availability features. The Route 53 weighted routing policy would distribute traffic between multiple resources, but does not support failover to a secondary region if the primary fails, thus failing to meet the high availability requirement.
This option creates a connection alias in the primary Region and associates it with a directory in the failover Region, which is not correct since connection aliases must be associated with directories in their respective regions. Although a Route 53 failover routing policy is proposed, it would not function properly due to the incorrect association of the connection alias.
I outline that the answer is:
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.