If you want the Internet-facing load balancer to be connected to the Internet, where must this load balancer reside?

You need to create a load balancer in a VPC network that you are building. You can make your load balancer internal (private) or internet-facing (public). When you make your load balancer internal, a DNS name will be created, and it will contain the private IP address of the load balancer. An internal load balancer is not exposed to the internet. When you make your load balancer internet-facing, a DNS name will be created with the public IP address.

If you want the Internet-facing load balancer to be connected to the Internet, where must this load balancer reside?
A . The load balancer must reside in a subnet that is connected to the internet using the internet gateway.
B . The load balancer must reside in a subnet that is not connected to the internet.
C . The load balancer must not reside in a subnet that is connected to the internet.
D . The load balancer must be completely outside of your VP

Answer: A

Explanation:

When you create an internal Elastic Load Balancer in a VPC, you need to select private subnets that are in the same Availability Zone as your instances. If the VPC Elastic Load Balancer is to be public facing, you need to create the Elastic Load Balancer in a public subnet. A subnet is a public subnet if it is attached to an Internet Gateway (IGW) with a defined route to that gateway. Selecting more than one public subnet increases the availability of your Elastic Load Balancer.

NB – Elastic Load Balancers in EC2-Classic are always Internet-facing load balancers.

Reference: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html