Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

🧑‍💻 AWS Foundation Sale - Certified Cloud & AI Practitioner Mock Exams for only $12.99 each!

Find answers, ask questions, and connect with our
community around the world.

Home Forums Azure Poorly worded question and (possibily) incomplete answer

  • Poorly worded question and (possibily) incomplete answer

     Nikee-TutorialsDojo updated 6 months, 2 weeks ago 2 Members · 2 Posts
  • samabc

    Member
    July 10, 2025 at 9:00 pm

    Your company has an Azure subscription that contains a virtual network with a subnet named TDSub1 and a virtual machine named TD1 with a public IP address and is configured to allow Remote Desktop Connections.TDSub1 is the subnet of TD1.

    Badly worded:

    > You created two network security groups named TDSG-TD1 attached to the network interface of TD1 and TDSG-TDSub1 attached to TDSub1.

    Better wording:
    You created two network security groups. One is named TDSG-TD1 and is attached to the network interface of TD1. The other network security group is named TDSG-TDSub1 and is attached to TDSub1.

    Answer is incomplete?

    > You should modify the current custom rule of TDSG-TD1 by changing the ICMP protocol to TCP protocol or you can create a new inbound security rule in TDSG-TD1 that allows port 3389 traffic from the Internet using TCP protocol.

    I believe the above is true, but also I think the security rule needs to be added to TDSG-TDSub1 as is mentioned in the Planned Changes section.

  • Nikee-TutorialsDojo

    Administrator
    July 11, 2025 at 8:56 am

    Hello Samabc,

    Thank you for the feedback. You’re right on both points. We’ll update the wording to improve clarity and revise the answer to ensure it reflects the need to configure the appropriate security rules in both TDSG-TD1 and TDSG-TDSub1. Thanks again for pointing it out.

    If you need further assistance, please don’t hesitate to contact us.

    Best Regards,

    Nikee @ Tutorials Dojo

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content