HTTP Alternative uses which port number?

HTTP Alternative uses which port number?

• A. 8080
• B. 2049
• C. 161
• D. 512

Answer: (A)

Ports tell a client where to reach a specific service on a host. HTTP normally uses port 80, but an alternative like 8080 is common for running web services without needing the default port or for development and testing. Because 8080 is widely recognized as a typical HTTP alternative, it’s the go-to choice when you’re not using the standard port, and you’d access the service with a URL that includes the port, such as http://host:8080. The other numbers point to different protocols (for example, 2049 is used by NFS, 161 by SNMP, and 512 is associated with legacy remote services), so they aren’t used for HTTP.

Ports tell a client where to reach a specific service on a host. HTTP normally uses port 80, but an alternative like 8080 is common for running web services without needing the default port or for development and testing. Because 8080 is widely recognized as a typical HTTP alternative, it’s the go-to choice when you’re not using the standard port, and you’d access the service with a URL that includes the port, such as http://host:8080. The other numbers point to different protocols (for example, 2049 is used by NFS, 161 by SNMP, and 512 is associated with legacy remote services), so they aren’t used for HTTP.