Ultimate access to all questions.
Explanation:
AWS Global Accelerator provides two static IP addresses that act as a fixed entry point to your application endpoints in a single or multiple AWS Regions. You can route traffic to an Application Load Balancer (ALB) through Global Accelerator. Since ALBs automatically scale and their IP addresses change, you cannot directly assign Elastic IPs to them (unlike Network Load Balancers). Thus, putting Global Accelerator in front of the ALB meets the requirement of providing a maximum of two static IP addresses.
No comments yet.
Question 3
A company is running an application on a group of Amazon EC2 instances behind an Application Load Balancer. The EC2 instances run across three Availability Zones. The company needs to provide the customers with a maximum of two static IP addresses for their applications. How should a SysOps administrator meet these requirement?
A
Add AWS Global Accelerator in front of the Application Load Balancer.
B
Add an internal Network Load Balancer behind the Application Load Balancer.
C
Configure the Application Load Balancer in only two Availability Zones.
D
Create two Elastic IP addresses and assign them to the Application Load Balancer.