Which two protocols can cause TCP starvation? (Choose two)

TFTP (Trivial File Transfer Protocol) uses UDP as its transport protocol, which lacks congestion control mechanisms. When TFTP traffic is heavy, it can flood network links, causing packet loss and retransmissions for TCP-based applications, leading to TCP starvation.

SNMP (Simple Network Management Protocol) primarily uses UDP for its operations and, similar to TFTP, does not implement congestion control. High volumes of SNMP traffic can disproportionately consume bandwidth, hindering the performance of TCP applications.

SMTP (Simple Mail Transfer Protocol) uses TCP as its transport protocol, which incorporates congestion avoidance mechanisms, preventing it from causing starvation for other TCP-based applications.

HTTPS (Hypertext Transfer Protocol Secure) uses TCP as its underlying transport protocol and includes congestion control mechanisms, ensuring it backs off during network congestion.

FTP (File Transfer Protocol) uses TCP for both its control and data connections. As a TCP-based application, it implements congestion control, meaning it will reduce its sending rate during network congestion rather than starving other TCP traffic.