
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.