Multiple Choice
A user has created a subnet in VPC and launched an EC2 instance within it. The user has not selected the option to assign the IP address while launching the instance. The user has 3 elastic IPs and is trying to assign one of the Elastic IPs to the VPC instance from the console. The console does not show any instance in the IP assignment screen. What is a possible reason that the instance is unavailable in the assigned IP console?
A) The IP address may be attached to one of the instances
B) The IP address belongs to a different zone than the subnet zone
C) The user has not created an internet gateway
D) The IP addresses belong to EC2 Classic; so they cannot be assigned to VPC
Correct Answer:

Verified
Correct Answer:
Verified
Q351: The SysOps Administrator must integrate an existing
Q352: A user has launched an EBS backed
Q353: A user has developed an application which
Q354: In Amazon CloudFront, if you have chosen
Q355: A company wants to increase the availability
Q357: A company runs an application that uses
Q358: Does AWS offer any web-based graphic user
Q359: A SysOps Administrator has created an Amazon
Q360: A user has configured ELB with Auto
Q361: A SysOps Administrator maintains several Amazon EC2