Which of the below mentioned options is not a possible reason for this?

A user has launched an EC2 instance. The instance got terminated as soon as it was launched.
Which of the below mentioned options is not a possible reason for this?

A user has launched an EC2 instance. The instance got terminated as soon as it was launched.
Which of the below mentioned options is not a possible reason for this?

A.
The user account has reached the maximum EC2 instance limit

B.
The snapshot is corrupt

C.
The AMI is missing. It is the required part

D.
The user account has reached the maximum volume limit

Explanation:
When the user account has reached the maximum number of EC2 instances, it will not be allowed
to launch an instance. AWS will throw an ‘InstanceLimitExceeded’ error. For all other reasons,
such as “AMI is missing part”, “Corrupt Snapshot” or ”Volume limit has reached” it will launch an
EC2 instance and then terminate it.



Leave a Reply 8

Your email address will not be published. Required fields are marked *


Mohit Gadkari

Mohit Gadkari

D??

Sachin

Sachin

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_InstanceStraightToTerminated.html

What To Do If An Instance Immediately Terminates

After you launch an instance, we recommend that you check its status to confirm that it goes from the pending state to the running state, not the terminated state.

The following are a few reasons why an instance might immediately terminate:

You’ve reached your EBS volume limit. For information about the volume limit, and to submit a request to increase your volume limit, see Request to Increase the Amazon EBS Volume Limit.

An EBS snapshot is corrupt.

The instance store-backed AMI you used to launch the instance is missing a required part (an image.part.xx file).

Flyboy

Flyboy

The answer matches the question, “Which of the below mentioned options is a possible reason for this?” The word NOT should be removed.

B. The question did not say the EC2 was being launched from a snapshot.

C. An AMI would not be ‘missing’. Invalid.

D. Volume? Garbage made up answer.

Flyboy

Flyboy

Disregard response above.

Bill

Bill

Sachin’s answer is correct. A is the only one that does not belong.

Bala

Bala

Tricky but good question

Answer A :

Explanation:
When the user account has reached the maximum number of EC2 instances, it will not be allowed
to launch an instance. AWS will throw an ‘InstanceLimitExceeded’ error. For all other reasons,
such as “AMI is missing part”, “Corrupt Snapshot” or ”Volume limit has reached” it will launch an
EC2 instance and then terminate it.