Exam AWS-SysOps All Questions

View all questions & answers for the AWS-SysOps exam

Exam AWS-SysOps topic 1 question 19 discussion

Exam question from Amazon's AWS-SysOps

Question #: 19
Topic #: 1

You have a Linux EC2 web server instance running inside a VPC The instance is In a public subnet and has an EIP associated with it so you can connect to It over the Internet via HTTP or SSH The instance was also fully accessible when you last logged in via SSH. and was also serving web requests on port 80.
Now you are not able to SSH into the host nor does it respond to web requests on port 80 that were working fine last time you checked You have double-checked that all networking configuration parameters (security groups route tables. IGW'EIP. NACLs etc) are properly configured {and you haven't made any changes to those anyway since you were last able to reach the Instance). You look at the EC2 console and notice that system status check shows "impaired."
Which should be your next step in troubleshooting and attempting to get the instance back to a healthy state so that you can log in again?

A. Stop and start the instance so that it will be able to be redeployed on a healthy host system that most likely will fix the "impaired" system status
B. Reboot your instance so that the operating system will have a chance to boot in a clean healthy state that most likely will fix the 'impaired" system status
C. Add another dynamic private IP address to me instance and try to connect via mat new path, since the networking stack of the OS may be locked up causing the ג€impairedג€ system status.
D. Add another Elastic Network Interface to the instance and try to connect via that new path since the networking stack of the OS may be locked up causing the "impaired" system status
E. un-map and then re-map the EIP to the instance, since the IGWVNAT gateway may not be working properly, causing the "impaired" system status

Show Suggested Answer

Suggested Answer: A 🗳️

by pleasespammelater at Jan. 28, 2020, 9:52 p.m.

Disclaimers:

- ExamTopics 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.

Comments

Submit Cancel

pleasespammelater

Highly Voted 3 years, 3 months ago

A is correct. https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html

upvoted 5 times

...

KittieHearts

Most Recent 8 months, 3 weeks ago

Selected Answer: A

If the security group is good and NaCl is good, sometimes the instance itself is not working. Just like a regular computer. A restart will assist

upvoted 1 times

...

albert_kuo

1 year, 6 months ago

B The fact that the system status check shows "impaired" indicates that there might be an issue at the system level, which could be resolved by a reboot. Rebooting the instance allows the operating system to restart in a clean state, potentially resolving any underlying issues that caused the impairment.

upvoted 3 times

albert_kuo

1 year, 3 months ago

Change to A https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html

upvoted 1 times

...

xxxdolorxxx

3 years, 1 month ago

A seems to be the correct answer. The question lays out like "hey it's not anything to do with security". So it's either crashed or the CPU is overloaded or something.

upvoted 1 times

...

RicardoD

3 years, 1 month ago

A is the answer This action will redeploy the EC2 in a healthy host system

upvoted 1 times

...

trulyrajiv

3 years, 1 month ago

If a system status check has failed, you can try one of the following options: Create an instance recovery alarm. For more information, see Create alarms that stop, terminate, reboot, or recover an instance. If you changed the instance type to an instance built on the Nitro System, status checks fail if you migrated from an instance that does not have the required ENA and NVMe drivers. For more information, see Compatibility for resizing instances. For an instance using an Amazon EBS-backed AMI, stop and restart the instance. For an instance using an instance-store backed AMI, terminate the instance and launch a replacement. Wait for Amazon EC2 to resolve the issue.

upvoted 1 times

...

vankarss

3 years, 2 months ago

Answer can be A or B. It does not mention instance store volume vs EBS instance volume

upvoted 1 times

jaribu

3 years, 1 month ago

Answer B is not appropriate because: You can reboot the instance to return it to an unimpaired status. The problem will probably occur again unless you change the instance type.

upvoted 3 times

...

awscertified

3 years, 2 months ago

A. Stop and start the instance so that it will be able to be redeployed on a healthy host system that most likely will fix the "impaired" system status

upvoted 2 times

...

pleasespammelater

3 years, 2 months ago

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html#InitialSteps

upvoted 1 times

...