A windows machine in one VPC needs to join the AD domain in another VPC. VPC Peering has been established. But the domain join is not working. What is the other step that needs to be followed to…

The correct answer is C. Ensure the security groups for the AD hosted subnet has the right rule for relevant subnets. In addition to VPC peering and setting the right route tables, the security groups for the AD EC2 instance needs to ensure the right rules are put in place for allowing incoming traffic. Option A and B is invalid because changing the connection type will not help. This is a…

Submitted by yaw92· Mar 6, 2026Infrastructure Security

Question

A windows machine in one VPC needs to join the AD domain in another VPC. VPC Peering has been established. But the domain join is not working. What is the other step that needs to be followed to ensure that the AD domain join can work as intended?

Options

AChange the VPC peering connection to a VPN connection
BChange the VPC peering connection to a Direct Connect connection
CEnsure the security groups for the AD hosted subnet has the right rule for relevant subnets
DEnsure that the AD is placed in a public subnet

How the community answered

(53 responses)

A
13% (7)
B
2% (1)
C
79% (42)
D
6% (3)

Explanation

In addition to VPC peering and setting the right route tables, the security groups for the AD EC2 instance needs to ensure the right rules are put in place for allowing incoming traffic. Option A and B is invalid because changing the connection type will not help. This is a problem with the Security Groups. Option D is invalid since the AD should not be placed in a public subnet https://docs.aws.amazon.com/quickstart/latest/active- directory-ds/ingress.html

Topics

#VPC peering#Active Directory#security groups#network connectivity

Community Discussion

No community discussion yet for this question.

Full SCS-C02 Practice