AD Connector Pre-Requisites

Answer - A,B and D.

The AWS documentation mentions this clearly.

Set up a VPC with the following:

At least two subnets.

Each of the subnets must be in a different Availability Zone.

The VPC must be connected to your on-premises network through a virtual private network (VPN) connection or AWS Direct Connect.

The VPC must have default hardware tenancy.

For more information on the pre-requisites for AD connector , please refer to the below link:

http://docs.aws.amazon.com/directoryservice/latest/admin-guide/prereq_connector.html

The AD connector available in AWS enables you to connect your AWS resources with an existing Active Directory infrastructure. This allows you to use your existing AD credentials to authenticate AWS resources.

The pre-requisites for using the AD connector are as follows:

A. There should be at least 2 subnets in the VPC with each in a different Availability Zone: The AD Connector must be deployed in at least 2 subnets in different Availability Zones for high availability. This means that if one of the subnets fails, the other subnet can continue to provide access to the Active Directory resources.

B. The VPC must be connected to your on-premises network: To use AD connector, your VPC must be connected to your on-premises network using VPN or AWS Direct Connect. This ensures that the Active Directory resources in your on-premises environment can be accessed from your VPC.

C. The VPC must have shared tenancy: The VPC in which you are deploying the AD Connector must have shared tenancy. This means that the VPC is shared by multiple AWS accounts. If your VPC has dedicated tenancy, you cannot use AD Connector.

D. The VPC must have default hardware tenancy: The VPC must have default hardware tenancy, which means that the instances launched in the VPC will use the same hardware as other AWS customers.

Therefore, the correct answers are A, B, and C.