Question

18. Using the correctly decrypted Administrator password and RDP, you cannot log in to a Windows instance you just launched. Which of the following is a possible reason?

A. There is no security group rule that allows RDP access over port 3389 from your IP address.
B. The instance is a Reserved Instance.
C. The instance is not using enhanced networking.
D. The instance is not an Amazon EBS-optimized instance.

Answer 1

One possible reason for being unable to log in to a Windows instance after correctly decrypting the Administrator password and using RDP is that there is no security group rule that allows RDP access over port 3389 from your IP address.

Step-by-step explanation:

One possible reason for being unable to log in to a Windows instance after correctly decrypting the Administrator password and using RDP is that there is no security group rule that allows RDP access over port 3389 from your IP address. Security groups control inbound and outbound traffic for instances, and in this case, it's likely that the necessary rule to allow RDP access has not been configured. To resolve the issue, you would need to modify the security group associated with the instance to add a rule allowing RDP access from your IP address.

It's important to note that the other options provided, such as the instance being a Reserved Instance, the instance not using enhanced networking, or the instance not being an Amazon EBS-optimized instance, are unlikely to be the cause of the problem in this scenario. These options are not directly related to RDP access to the instance.