A company completed a successful Amazon Workspaces proof of concept. They now want to make Workspaceshighly available across two AWS Regions. Workspaces are deployed in the failover Region. A hosted zone is available in Amazon Route 53. What should the solutions architect do?

Question

Accepted Answer

A. Create a connection alias in the primary Region and in the failover Region. Associate each with a For multi-Region WorkSpaces deployments with high availability, a connection alias must be created in *each* Region (primary and failover) and then associated with the respective WorkSpaces directory in that specific Region. This setup allows users to connect to the nearest available WorkSpace and supports failover by directing traffic to the healthy Region.

Answer

B. Create a connection alias in both Regions. Associate both with a directory in the primary Region. Associating connection aliases from both regions with a *single* directory in the primary region would not support multi-region high availability or failover, as the failover WorkSpaces would not be linked to their respective aliases.

Answer

C. Create a connection alias in the primary Region. Associate with the directory in the primary Creating a connection alias only in the primary region and associating it with the primary directory would not provide a mechanism for users to connect to WorkSpaces in the failover region.

Answer

D. Create a connection alias in the primary Region. Associate it with the directory in the failover Associating a connection alias in the primary region with a directory in the failover region is an incorrect configuration; connection aliases must be associated with a directory within the same region.

A company completed a successful Amazon Workspaces proof of concept. They now want to make Workspaceshighly available across two AWS Regions. Workspaces are deployed in the failover Region. A hosted…

Question

Options

How the community answered

Why each option

Community Discussion