Which solution will meet these requirements?

By:
In: SAP-C01
Tagged:
With: 2 Comments
A United Kingdom (UK) company recently completed a successful proof of concept in Amazon WorkSpaces.The company also has a large office in the UnitedStates (US).Staff members from each office regularly travel between the two locations and need access to a corporate WorkSpace without any reconfiguration of their WorkSpaces client.The company has purchased a domain by using Amazon Route 53 for the connection alias.The company will use a Windows profile and document management solution.A solutions architect needs to design the full solution.The solution must use a configuration of WorkSpaces in two AWS Regions and must provide Regional resiliency.

Which solution will meet these requirements?

Create a connection alias in a UK Region and a US Region. Associate the connection alias with a directory in the UK Region. Configure the DNS service for the domain in the connection alias. Configure a geolocation routing policy. Distribute the connection string to the WorkSpaces users.

Create a connection alias in a UK Region. Associated the connection alias with a directory in the UK Region. Configure the DNS service for the domain in the connection alias. Configure a weighted routing policy, with the UK Region set to 1 and a US Region set to 255. Distribute the connection string for the UK Region to the WorkSpaces users.

Create a connection alias in a UK Region and a US Region. Associate the connection aliases with a directory in each Region. Configure the DNS service for the domain in the connection alias. Configure a geolocation routing policy. Distribute the connection string to the WorkSpaces users.

Create a connection alias in a US Region. Associated the connection alias with a directory in the UK Region. Configure the DNS service for the domain in the connection alias. Configure a multivalue answer routing policy. Distribute the connection string for the US Region to the WorkSpaces users.

Explanations:

This option incorrectly associates the connection alias only with a directory in the UK Region, which does not provide redundancy for users in the US. Users traveling between regions need a seamless connection without reconfiguration, which this option does not achieve.

This option only creates a connection alias in the UK Region and uses a weighted routing policy that heavily favors the UK Region, neglecting the US users’ needs for access to a WorkSpace without reconfiguration. It does not provide regional resiliency.

This option creates connection aliases in both UK and US Regions and associates each with a directory in their respective regions. It also configures a geolocation routing policy, allowing users to connect to the nearest region seamlessly, meeting the requirements for regional resiliency and ease of access.

This option creates a connection alias in the US Region but associates it only with the directory in the UK Region. This creates a single point of failure for US users, who would not have direct access to a WorkSpace in their region, violating the requirement for regional resiliency.

2026-03-20

2 Comments

  1. Lawrence
    Author

    I sort that the answer is:
    Create a connection alias in a UK Region and a US Region. Associate the connection aliases with a directory in each Region. Configure the DNS service for the domain in the connection alias. Configure a geolocation routing policy. Distribute the connection string to the WorkSpaces users.

  2. Ruth
    Author

    From what I’ve heard, the answer is:
    Create a connection alias in a UK Region and a US Region. Associate the connection aliases with a directory in each Region. Configure the DNS service for the domain in the connection alias. Configure a geolocation routing policy. Distribute the connection string to the WorkSpaces users.

Leave a Reply to Ruth Cancel reply

Your email address will not be published. Required fields are marked *

16 − 9 =