Answer-first summary for fast verification
Answer: Only Elastic IP can be used by requesting limit increase, since AWS does not assign a public IP to an instance with multiple ENIs.
Explanation for Answer A: Option A is the correct choice because AWS does not automatically assign a public IP to an instance with multiple Elastic Network Interfaces (ENIs). In this scenario, the organization has specified two distinct network interfaces for each instance, which means they need a way to access these instances over the internet. Since the account's elastic IP allocation is limited per region, the organization should request a limit increase to accommodate their requirement of having a public IP for each of the 20 instances (10 for WordPress and 10 for Joomla). This will allow them to maintain the desired architecture and ensure that each instance can be accessed over the internet using a distinct domain through Route 53. Using Elastic IPs is a viable solution in this case, as it provides a static IP address that can be associated with an instance, regardless of the number of ENIs it has. This ensures that the instances remain accessible over the internet, even if the primary network interface fails or is removed. It's important to note that while using Elastic IPs is a valid approach, the organization should also consider the implications of exceeding the elastic IP limit and the associated costs. Requesting a limit increase is a proactive step to ensure that they can meet their requirements without facing any disruptions or additional expenses.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A business wishes to host both a Word press blog and a Joomla content management system on a same VPC server. The business want to use Route 53 to generate distinct domains for each application. Each of these two programs may have around 10 instances inside the business. During the instance's launch, the organization specified two distinct network interfaces (main + secondary ENIs) with their unique Elastic IPs. The advice was to utilize a public IP from AWS rather than an elastic IP, since the account's elastic IP allotment is limited per region. Which course of action would you suggest to the organization?
A
Only Elastic IP can be used by requesting limit increase, since AWS does not assign a public IP to an instance with multiple ENIs.
B
AWS VPC does not attach a public IP to an ENI; so the only way is to use an Elastic IP.
C
I agree with the suggestion but will prefer that the organization should use separate subnets with each ENI for different public IPs.
D
I agree with the suggestion and it is recommended to use a public IP from AWS since the organization is going to use DNS with Route 53.
No comments yet.