What should the solutions architect recommend?
Create a load balancer and associate two public subnets from the same Availability Zones as the private instances. Add the private instances to the load balancer.
Create a load balancer and associate two private subnets from the same Availability Zones as the private instances. Add the private instances to the load balancer.
Create an Amazon Machine Image (AMI) of the instances in the private subnet and restore in the public subnet. Create a load balancer and associate two public subnets from the same Availability Zones as the public instances.
Create an Amazon Machine Image (AMI) of the instances in the private subnet and restore in the public subnet. Create a load balancer and associate two private subnets from the same Availability Zones as the public instances.
Explanations:
A load balancer in public subnets can act as an intermediary to route traffic from the internet to the instances in the private subnets. Associating the load balancer with public subnets exposes it to the internet while keeping the EC2 instances secure within private subnets.
A load balancer in private subnets cannot accept internet traffic, so this setup would not allow public internet access to the application.
Moving the instances to public subnets by creating AMIs and restoring them is unnecessary and more administratively burdensome, as associating a public load balancer with private subnets achieves the requirement more efficiently.
Placing the restored instances in public subnets but associating a load balancer with private subnets is ineffective for internet access because a load balancer in private subnets does not allow public internet traffic, defeating the purpose of restoring the instances publicly.