A user is trying to connect to a running EC2 instance using SSH. However, the user gets a connection time out
error. Which of the below mentioned options is not a possible reason for rejection?
A.
The access key to connect to the instance is wrong
B.
The security group is not configured properly
C.
The private key used to launch the instance is not correct
D.
The instance CPU is heavily loaded
Explanation:
If the user is trying to connect to a Linux EC2 instance and receives the connection time out error the probable
reasons are:
Security group is not configured with the SSH port
The private key pair is not right
The user name to login is wrong
The instance CPU is heavily loaded, so it does not allow more connections
D.
The instance CPU is heavily loaded
0
0
B.
The security group is not configured properly
0
0
A is correct.
access key is is used for the API tools.
1
0
Chef and raj have it backwards. The question ask what will NOT cause a connection time out error. Both D and B can cause connection time out error.
A is wrong. A security group that does not allow SSH connections will cause a connection time.
D is wrong. A heavily loaded CPU can cause a connection time out as well.
The correct answer is C. Using the wrong private key will generate a Permission denied (publickey,gssapi-keyex,gssapi-with-mic) error. It will not generate a connection time out error.
0
0
Can be B or D. I prefer B.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesConnectionTimeout
1
0
A. used to access AWS ressources programmatically (Not applicable when using SSH)
B. Security group not allowing SSH (Can cause a connection time out)
C. The private key will give an error message (not a time out)
D. Busy CPU (Can cause a connection time out)
A and C are the correct answers
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
0
0
Correct Answer is (A)
Access key is nowhere in the picture while connecting to the instance. it is used for AWS CLI
0
0
Answer is A.
See. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html
0
0
Answer is A
A – not for SSH
B – if port 22 not open, timeout
C – if the instance is a windows instance, timeout
D – if CPU load high, sshd may not able to work, timeout.
0
0
Answer – A
If the user is trying to connect to a Linux EC2 instance and receives the connection time
out error the probable reasons are:
Security group is not configured with the SSH port
The private key pair is not right
The user name to login is wrong
The instance CPU is heavily loaded, so it does not allow more connections
0
0
A
which one is NOT a reason.
0
0
a
0
0
The answer should be A. The question discuss “not the possible reason for connection timed out”
0
0
A is the answer
0
0
A
0
0
A
0
0
C would give a different error, not time out …
0
0