A customer is running a multi-tier web application farm in a virtual private cloud (VPC) that is not connected to
their corporate network. They are connecting to the VPC over the Internet to manage all of their Amazon EC2
instances running in both the public and private subnets. They have only authorized the bastion-security-group
with Microsoft Remote Desktop Protocol (RDP) access to the application instance security groups, but the
company wants to further limit administrative access to all of the instances in the VPC. Which of the following
Bastion deployment scenarios will meet this requirement?
A.
Deploy a Windows Bastion host on the corporate network that has RDP access to all instances in the VPC.
B.
Deploy a Windows Bastion host with an Elastic IP address in the public subnet and allow SSH access to the
bastion from anywhere.
C.
Deploy a Windows Bastion host with an Elastic IP address in the private subnet, and restrict RDP access to
the bastion from only the corporate public IP addresses.
D.
Deploy a Windows Bastion host with an auto-assigned Public IP address in the public subnet, and allow
RDP access to the bastion from only the corporate public IP addresses.
D
http://www.aiotestking.com/amazon/which-of-the-following-bastion-deployment-scenarios-will-meet-this-requirement/
0
0
Yes, the answer is D. Because the request is to have controlled access to other instances, so Bastion host required. But Bastion host should be in public subnet. Also, the request is for RDP and not SSH, so option B becomes invalid.
0
0
Earlier I thought C. But C is wrong because C is denying network from Corporate network and approving all other connections. Opposite of what we desire.
“with an Elastic IP address in the private subnet, and RESTRICT RDP access to
the bastion from only the corporate public IP addresses.”
Hence, D.
0
0
D
0
0