Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam AWS-SysOps topic 1 question 685 discussion

Exam question from Amazon's AWS-SysOps
Question #: 685
Topic #: 1
[All AWS-SysOps Questions]

After launching a new Amazon EC2 instance from a Microsoft Windows 2012 Amazon Machine Image (AMI), the SysOps Administrator is unable to connect to the instance using Remote Desktop Protocol (RDP). The instance is also unreachable. As part of troubleshooting, the Administrator deploys a second instance from a different AMI using the same configuration and is able to connect to the instance.
What should be the next logical step in troubleshooting the first instance?

  • A. Use AWS Trusted Advisor to gather operating system log files for analysis.
  • B. Use VPC Flow Logs to gather operating system log files for analysis.
  • C. Use EC2Rescue to gather operating system log files for analysis.
  • D. Use Amazon Inspector to gather operating system log files for analysis.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
Reference:
https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-remote-desktop-connection-ec2-windows/

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
saumenP
Highly Voted 2 years, 7 months ago
C is correct
upvoted 8 times
...
NoCrapEva
Highly Voted 2 years, 7 months ago
B: You have to use VPC Flow Logs, EC2 rescue will not work as you cannot connect via RDP... as per this ref: https://aws.amazon.com/premiumsupport/knowledge-center/ec2rescue-windows-troubleshoot/ EC2Rescue requires an EC2 Windows instance that meets the following specifications: Windows Server 2008 R2 or later NET Framework 3.5 SP1 or later installed Is accessible from a Remote Desktop Protocol (RDP) connection
upvoted 7 times
KhatriRocks
2 years, 6 months ago
Yes when I read the blog, so I also chose B as the option.
upvoted 1 times
shammous
2 years, 6 months ago
You need to read the answer carefully my friend: "Use VPC Flow Logs to gather operating system log files for analysis." Flow logs is not meant for gathering OS log files. It can only help with: - Diagnosing overly restrictive security group rules - Monitoring the traffic that is reaching your instance - Determining the direction of the traffic to and from the network interfaces EC2Rescue, on the other hand, is meant for for gathering OS log files. It's true that you can't access it via RDP, but you can via other means like SSH ...
upvoted 3 times
nisoshabangu
2 years, 6 months ago
Other means like SSH? I don't think so SSH is linux. unless there is an option for serial connection.
upvoted 3 times
...
...
...
xenodamus
1 year, 5 months ago
EC2 Rescue would be used from another instance that you could attach the existing EBS volume to.
upvoted 1 times
...
...
albert_kuo
Most Recent 9 months, 2 weeks ago
Selected Answer: C
Using EC2Rescue is an effective way to gather relevant system logs and perform diagnostics on the first instance, allowing the SysOps Administrator to identify and troubleshoot the underlying cause of the connectivity and reachability issues.
upvoted 1 times
...
Cyril_the_Squirl
2 years, 5 months ago
C is correct. https://aws.amazon.com/premiumsupport/knowledge-center/ec2rescue-windows-troubleshoot/
upvoted 1 times
...
Huy
2 years, 5 months ago
C is correct. VPC Flow Logs is not able to gather operating system log files for analysis.
upvoted 1 times
...
abhishek_m_86
2 years, 5 months ago
C. Use EC2Rescue to gather operating system log files for analysis. Seem correct
upvoted 1 times
...
Chirantan
2 years, 5 months ago
C is correct EC2Rescue for EC2 Windows is a troubleshooting tool that you can run on your Amazon EC2 Windows Server instances. Use the tool to troubleshoot OS-level issues and to collect advanced logs and configuration files for further analysis. The following are some common issues that EC2Rescue can address: Instance connectivity issues due to firewall, Remote Desktop Protocol (RDP), or network interface configuration. OS boot issues due to a blue screen or stop error, a boot loop, or a corrupted registry. Any issues that might need advanced log analysis and troubleshooting.
upvoted 3 times
...
shamith
2 years, 5 months ago
c https://aws.amazon.com/premiumsupport/knowledge-center/troubleshootremote- desktop-connection-ec2-windows/
upvoted 1 times
...
jerry19
2 years, 6 months ago
After reviewing everyone's excellent comments....answer is C. "Then, use EC2Rescue to troubleshoot Amazon EC2 Windows Server instance issues: Instance connectivity issues: Use the Diagnose and Rescue feature in Offline instance mode. OS boot issues: Use the Restore feature in Offline instance mode. Advanced logs and troubleshooting: Use the Capture logs feature in either Current instance mode or Offline instance mode." VPC Flow logs have nothing to do with os log files only interfaces to specific source you are troubleshooting. The info is in the same link everyone keeps referencing.
upvoted 1 times
...
NivNZ
2 years, 6 months ago
EC2Rescue requires an Amazon EC2 Windows instance that: * Runs on Windows Server 2008 R2 or later * Has .NET Framework 3.5 SPI or later installed * Is accessible from an RDP connection Above info is from https://aws.amazon.com/premiumsupport/knowledge-center/ec2rescue-windows-troubleshoot/ Since RDP isn't possible in our scenario, I reckon B is the answer
upvoted 1 times
NivNZ
2 years, 6 months ago
I take it back. C is the answer because VPC flow logs cannot be used to give OS sys log files for analysis.
upvoted 3 times
Bigdss
2 years, 5 months ago
EC2Rescue can be run as SSM Document hence you don't need RDP access.
upvoted 2 times
...
...
...
whgustn28
2 years, 6 months ago
https://aws.amazon.com/premiumsupport/knowledge-center/ec2rescue-windows-troubleshoot/ C should be just fine as AWS already stated EC2Rescue is a way to go for this case.
upvoted 1 times
...
jackdryan
2 years, 6 months ago
I'll go with C
upvoted 1 times
...
MFDOOM
2 years, 6 months ago
C. Use EC2Rescue to gather operating system log files for analysis.
upvoted 1 times
...
mbspark
2 years, 6 months ago
C Is Correct. Even though you can't RDP and the documentation states that is a requirement, what you CAN do with EC2Rescue is "offline" mode. Notice in the question, it tells you that you can deploy a 2nd instance. So you take the volume of the "bad" Offline instance, and attach that volume to the "good" instance and THEN run EC2Rescue on the volume from the Good instance.
upvoted 1 times
moon_lee
2 years, 6 months ago
@mbspark - is it? because the "good" instance is from a different AMI if im not mistaken.
upvoted 2 times
...
...
ataraxium
2 years, 6 months ago
Answer = 'B' I would think, since EC2 Rescue requires RDP, but that is unavailable.
upvoted 2 times
...
waterzhong
2 years, 6 months ago
C. Use EC2Rescue to gather operating system log files for analysis.
upvoted 1 times
...
KhatriRocks
2 years, 6 months ago
System Requirements EC2Rescue requires an EC2 Windows instance that meets the following specifications: Windows Server 2008 R2 or later NET Framework 3.5 SP1 or later installed Is accessible from a Remote Desktop Protocol (RDP) connection Note: EC2Rescue can only be run on Windows Server 2008 R2 or later, but it can also analyze the offline volumes of Windows Server 2008 or later
upvoted 1 times
MrDEVOPS
2 years, 6 months ago
its C :- Ec2 rescue only supports windows server 2008 or later(which means 2012 too.)
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...