How does 'bind_ipv6_tcp' differ from 'bind_tcp'?

• A. bind_ipv6_tcp uses HTTP over TCP.
• B. bind_ipv6_tcp runs on Windows only.
• C. bind_ipv6_tcp is similar to bind_tcp but uses IPv6 addresses.
• D. bind_ipv6_tcp initiates a reverse connection.

Answer: (C)

The key idea is the address family used when creating the listening socket. Both options use TCP, but one binds to IPv4 addresses and the other binds to IPv6 addresses. bind_tcp listens on IPv4 (addresses like 127.0.0.1 or a.b.c.d), while bind_ipv6_tcp listens on IPv6 addresses (like ::1 or 2001:db8::1). This difference matters when you want to accept connections over IPv6 or IPv4 distinctly, and it can also affect how the socket handles dual-stack behavior on a given system. The other statements aren’t describing what changes between them: it’s not about HTTP over TCP, not Windows-only, and not about initiating a reverse connection.