Doug has created a VPC with CIDR 10.201.0.0/16 in his AWS account. In this VPC he has created a public subnet with CIDR block 10.201.31.0/24.
While launching a new EC2 from the console, he is not able to assign the private IP address 10.201.31.6 to this instance.
Which is the most likely reason for this issue?

A. Private address IP 10.201.31.6 is currently assigned to another interface

B. Private IP address 10.201.31.6 is reserved by Amazon for IP networking purposes.

C. Private IP address 10.201.31.6 is blocked via ACLs in Amazon infrastructure as a part of platform security.

D. Private IP address 10.201.31.6 is not part of the associated subnet's IP address range.








 

Suggested Answer: A

Community Answer: A

In Amazon VPC, you can assign any Private IP address to your instance as long as it is: Part of the associated subnet's IP address range
Not reserved by Amazon for IP networking purposes Not currently assigned to another interface
Reference:
http://aws.amazon.com/vpc/faqs/


This question is in SAP-C01 AWS Certified Solutions Architect – Professional Exam
For getting AWS Certified Solutions Architect – Professional Certificate



Disclaimers:
The website is not related to, affiliated with, endorsed or authorized by Amazon.
Trademarks, certification & product names are used for reference only and belong to Amazon.
The website does not contain actual questions and answers from Amazon's Certification Exam.