Question

Complete the following Windows PowerShell cmdlet to test TCP connectivity with secure HTTP. Test-NetConnection ComputerName PLABDM01 -Port A.443 B.445 C.446 D.80

Answer 1

The correct cmdlet to test TCP connectivity with secure HTTP is 'Test-NetConnection ComputerName -Port 443'. The other options are incorrect because they represent different ports.

Step-by-step explanation:

The correct cmdlet to test TCP connectivity with secure HTTP is:

• Test-NetConnection ComputerName -Port 443

This cmdlet checks the TCP connectivity on port 443, which is the default port for secure HTTP (HTTPS) communication. It will provide information about whether the connection was successful or not.

The other options given (445, 446, and 80) are incorrect because:

• Port 445 is used for Server Message Block (SMB) communication.
• Port 446 is not commonly used for secure HTTP communication.
• Port 80 is the default port for unsecured HTTP communication.

Therefore, the correct option is B.443. This cmdlet can be used in Windows PowerShell to test TCP connectivity for various purposes, including troubleshooting network connections and checking if a specific port is open or blocked.

Answer 2

Note that the port number with which you can complete the above Windows PowerShell cmdlet to test TCP connectivity with secure HTTP is Port 443 (Option A)

Port 443 is the standard port for HTTPS, the secure version of HTTP. HTTPS is used by websites and other online services to protect your data from being intercepted by eavesdroppers.

To test TCP connectivity with secure HTTP using Windows PowerShell, you can complete the cmdlet as follows:

Test-NetConnection -ComputerName PLABDM01 -Port 443

In this example, the -Port parameter is set to 443` which is the default port for secure HTTP (HTTPS).

This cmdlet will check the TCP connectivity to the specified computer (PLABDM01) on port 443, indicating whether the connection can be established.