AWS Certified Developer - Associate
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
Your company is utilizing an internet-facing load balancer within a VPC. The public DNS name assigned to this load balancer is myDns-1234567890.us-east-1.elb.amazonaws.com. When client applications initially load, they capture the load balancer's DNS name and resolve it to an IP address to directly reference the underlying IP. Despite the client applications functioning properly at first, they unexpectedly cease to work after some time. What could be the reason for this behavior?
Explanation:
Overall explanation Correct option:
The load balancer is highly available and its public IP may change. The DNS name is constant
When your load balancer is created, it receives a public DNS name that clients can use to send requests. The DNS servers resolve the DNS name of your load balancer to the public IP addresses of the load balancer nodes for your load balancer. Never resolve the IP of a load balancer as it can change with time. You should always use the DNS name.
Incorrect options:
Your security groups are not stable - You security groups to allow your load balancer to work with registered instances. It is stable if set correctly. If your application is working and stops after a while, the issue is not with the security groups.
You need to enable stickiness - This enables the load balancer to bind a user's session to a specific instance, so this has no impact on the issue described in the given use-case.
You need to disable multi-AZ deployments - This has been added as a distractor and this has no bearing on the use-case. The change is happening with the IP of the load balancer.