Configuring On-Premises Servers
Question
Your company currently has a VPC hosted in AWS.
There is a private hosted zone in place for the instances in this VPC.
You need your On-premises servers to be able to resolve the AD DNS requests for instances in the VPC.
You need to do this with the least amount of effort.
What steps would you? Choose 2 answers from the options given below.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer - A and C.
Options B and D are invalid because even though feasible would require more effort to set up.
The AWS Documentation mentions the following.
Simple AD forwards DNS requests to the IP address of the Amazon-provided DNS servers for your VPC.
These DNS servers will resolve names configured in your Route 53 private hosted zones.
By pointing your on-premises computers to your Simple AD, you can now resolve DNS requests to the private hosted zone.
For more information on Simple AD, please refer to the below URL.
https://docs.aws.amazon.com/directoryservice/latest/admin-guide/simple_ad_dns.htmlTo enable your On-premises servers to resolve the AD DNS requests for instances in the VPC, you have two options:
Option 1: Set up a Simple AD in AWS and make On-premises servers point to it.
Step 1: Create a Simple AD in AWS Directory Service.
Step 2: Configure the VPC to use the Simple AD for DNS resolution.
Step 3: Update the DNS settings on your On-premises servers to use the IP addresses of the Simple AD's DNS servers.
Option 2: Set up an Active Directory Domain Controller in the AWS VPC and make On-premises servers point to it.
Step 1: Launch a new EC2 instance to act as a Domain Controller.
Step 2: Configure the instance as a Domain Controller by installing Active Directory and promoting it to a Domain Controller.
Step 3: Join the EC2 instance to the VPC and create a new subnet for it.
Step 4: Update the DNS settings on your On-premises servers to use the IP address of the new Domain Controller.
Option 1 is the simpler and more cost-effective option, as it requires fewer steps and resources. However, Option 2 may be necessary if you need more control over the configuration of the Domain Controller and want to customize it beyond what is available in Simple AD.
