If you want to launch Amazon Elastic Compute Cloud (EC2) instances and assign each instance a
predetermined private IP address you should:
A.
Launch the instance from a private Amazon Machine Image (AMI).
B.
Assign a group of sequential Elastic IP address to the instances.
C.
Launch the instances in the Amazon Virtual Private Cloud (VPC).
D.
Launch the instances in a Placement Group.
E.
Use standard EC2 instances since each instance gets a private Domain Name Service (DNS) already.
When you launch an instance into a VPC, a primary private IP address from the address range of the subnet is assigned to the default network interface (eth0) of the instance. If you don’t specify a primary private IP address, we select an available IP address in the subnet range for you
Source: http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html
0
0
C
0
0
C
0
0
C
0
0
C
Each instance in a VPC has a default network interface (eth0) that is assigned the primary private IP address.
0
0
You can’t launch an instance outside of a VPC.
IMO answer is E.
0
5
The correct Answer is C.
@eduardojn, you can launch instance out side VPC if you are having older AWS account supporting ec2-classic.
3
0
C
0
0
answer is E
Private IP address
EC2-Classic
Your instance receives a private IP address from the EC2-Classic range each time it’s started.
Default Subnet
Your instance receives a static private IP address from the address range of your default subnet.
Nondefault subnet
Your instance receives a static private IP address from the address range of your subnet.
0
0
None of these choices taken by themselves would guarantee the required “predetermined private IP address” getting assigned to the instance. You’d need an ENI for that. But at a bare minimum, in order to attach an ENI with an assigned private IP on it to an instance, you’d need a VPC.
0
0
Answer is C
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html
When you launch an instance into a VPC, a primary private IP address from the IPv4 address range of the subnet is assigned to the default network interface (eth0) of the instance.
0
0
Answer is B
Answer is C
https://aws.amazon.com/articles/5050
0
0
Please disregard the above ANSWER it is meant for another question.
Answer – B
0
0
Incomplete question.
You can have a EC2 instance in a VPC while launching you can assign a pre dertemined IP to the eth0 hence most probable answer is C
E is not an answer DNS has got nothing to do with IP allocation , while VPC also has a default DHCP whch does IP allocation.
0
0
The answer is C.
A. Launch the instance from a private Amazon Machine Image (AMI).
INCORRECT – AMI image can’t specify the private IP
B. Assign a group of sequential Elastic IP address to the instances.
INCORRECT – Elastic IPs are not sequential.
C. Launch the instances in the Amazon Virtual Private Cloud (VPC).
CORRECT – You can create ENI’s with specific private IPs under VPC then assign the ENI when you launch the instances.
D. Launch the instances in a Placement Group.
WRONG – Irrelevant
E. Use standard EC2 instances since each instance gets a private Domain Name Service (DNS) already.
WRONG – Irrelevant
0
0