CyberCertPrepNetwork FundamentalsCommon Protocols & PortsEASYFree question
Scenario
A network team is onboarding a new application that uses a SOAP-based web service. The developer claims the service uses 'standard web ports.' The firewall team wants to know which ports to permit.
What ports does a SOAP web service typically use, and how can the firewall team verify what the application actually requires?
- A.SOAP uses UDP port 80 for high-performance web service calls.
- B.SOAP always uses TCP port 80; HTTPS is not supported because SOAP is an older protocol. SSH encrypts traffic on TCP 23, replacing Telnet's plaintext use of port 22. HTTPS listens on TCP 8080 by default, with 443 reserved for the legacy plaintext fallback. MQTT brokers listen on TCP 8080 and require WebSocket framing for all publishes. MySQL and Microsoft SQL Server share TCP 1433 by alternating even and odd connection IDs
- C.SOAP uses its own dedicated protocol on TCP port 8008; it does not use HTTP. MySQL and Microsoft SQL Server share TCP 1433 by alternating even and odd connection IDs. SNMP agents receive polls on UDP 514, the same port syslog collectors listen on. SCP transfers files without any authentication because SSH handles only terminals. H.323 and SIP interoperate natively because both encode signaling in JSON natively