Socket programming basics in Computer Networks - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of a socket in network programming?

Choose the best description of what a socket does in computer networks.

A It stores large amounts of data temporarily during network communication.

B It encrypts data before sending it over the internet to ensure security.

C It manages the physical connection cables between computers.

D It acts as an endpoint for sending and receiving data between two machines over a network.

💡 Hint

Think about how two programs communicate over a network.

A socket is like a door or endpoint that allows two computers to send and receive data. It does not handle encryption, storage, or physical cables directly.

📋 Factual

intermediate

Which protocol is commonly used with sockets for reliable communication?

Identify the protocol that ensures data is delivered reliably and in order when using sockets.

A IP (Internet Protocol)

B TCP (Transmission Control Protocol)

C UDP (User Datagram Protocol)

D FTP (File Transfer Protocol)

💡 Hint

Consider which protocol manages connection and guarantees delivery.

TCP is a connection-oriented protocol that ensures reliable, ordered delivery of data. UDP is faster but does not guarantee delivery. IP handles addressing, and FTP is an application protocol.

🚀 Application

advanced

What happens if a server socket is not bound to a port before listening?

Consider a server program that creates a socket but does not bind it to any port before calling listen(). What will be the result?

A The server will raise an error because binding to a port is required before listening.

B The server will listen on a random available port, making it hard for clients to connect.

C The server will listen on the default HTTP port 80 automatically.

D The server will accept connections but only from the local machine.

💡 Hint

Think about the role of binding in socket setup.

Binding assigns a specific port to the socket. Without binding, the server cannot listen on any port, so an error occurs.

🔍 Analysis

advanced

Why might a client socket fail to connect to a server socket?

Analyze the possible reasons a client socket cannot establish a connection to a server socket.

A All of the above.

B The client socket uses UDP instead of TCP to connect to a TCP server socket.

C Network firewall or security settings block the connection.

D The server is not running or not listening on the specified port.

💡 Hint

Consider all common causes of connection failure.

Connection failures can happen if the server is down, protocols mismatch, or network security blocks the traffic.

❓ Reasoning

expert

What is the effect of setting the socket option SO_REUSEADDR on a server socket?

Explain what happens when a server socket sets the SO_REUSEADDR option before binding.

A It encrypts the data sent through the socket for secure communication.

B It limits the number of simultaneous connections the server can accept.

C It allows the socket to bind to a port that is in the TIME_WAIT state, enabling quick restarts.

D It automatically closes the socket after a timeout period.

💡 Hint

Think about how servers restart quickly after closing connections.

SO_REUSEADDR allows a socket to bind to a port even if previous connections on that port are still in the TIME_WAIT state, which helps servers restart without waiting.

Practice

1. What is the primary purpose of a socket in computer networks?

easy

A. To enable communication between two programs over a network

B. To store files on a server

C. To encrypt data before sending

D. To manage user permissions on a device

Solution

1. Step 1: Understand what a socket does

   A socket is an endpoint for sending or receiving data across a network connection.

2. Step 2: Identify the main function

   Its main role is to allow two programs on different devices to communicate.

3. Final Answer:

   To enable communication between two programs over a network -> Option A

4. Quick Check:

   Socket = communication endpoint [OK]

Hint: Remember sockets connect programs for data exchange [OK]

Common Mistakes:

• Confusing sockets with file storage
• Thinking sockets encrypt data
• Assuming sockets manage user permissions

2. Which of the following is the correct order of steps in basic socket programming?

easy

A. Bind, create socket, listen, accept, send/receive, close

B. Create socket, bind, listen, accept, send/receive, close

C. Create socket, listen, bind, accept, send/receive, close

D. Accept, create socket, bind, listen, send/receive, close

Solution

1. Step 1: Recall the socket programming sequence

   The correct sequence starts by creating a socket, then binding it to an address and port.

2. Step 2: Follow the connection steps

   After binding, the server listens for connections, accepts them, then sends/receives data, and finally closes the socket.

3. Final Answer:

   Create socket, bind, listen, accept, send/receive, close -> Option B

4. Quick Check:

   Socket steps = create, bind, listen, accept, send/receive, close [OK]

Hint: Remember: Create, Bind, Listen, Accept, Communicate, Close [OK]

Common Mistakes:

• Binding before creating socket
• Listening before binding
• Accepting before listening

3. Consider this Python server code snippet:

import socket
s = socket.socket()
s.bind(('localhost', 12345))
s.listen(1)
conn, addr = s.accept()
data = conn.recv(1024)
print(data.decode())
conn.close()
s.close()

What will be printed if the client sends the message "Hello"?

medium

A. Error: decode() not found

B. b'Hello'

C. Hello

D. None

Solution

1. Step 1: Understand data reception

   The server receives bytes data from the client using conn.recv(1024).

2. Step 2: Decode bytes to string

   The data.decode() converts bytes to a readable string, so printing it shows "Hello".

3. Final Answer:

   Hello -> Option C

4. Quick Check:

   Bytes decoded to string = Hello [OK]

Hint: recv() returns bytes; decode() converts to string [OK]

Common Mistakes:

• Expecting bytes output without decoding
• Assuming decode() causes error
• Thinking recv() returns None

4. Identify the error in this socket server code snippet:

import socket
s = socket.socket()
s.listen(1)
s.bind(('localhost', 12345))
conn, addr = s.accept()

medium

A. Calling listen() before bind()

B. Missing socket creation

C. accept() called without listen()

D. bind() called after accept()

Solution

1. Step 1: Check the order of socket calls

   The socket must be bound to an address before it starts listening.

2. Step 2: Identify the incorrect sequence

   Here, listen() is called before bind(), which is incorrect and will cause an error.

3. Final Answer:

   Calling listen() before bind() -> Option A

4. Quick Check:

   Bind before listen [OK]

Hint: Always bind socket before listen() [OK]

Common Mistakes:

• Calling listen() before bind()
• Confusing accept() and listen() order
• Forgetting to create socket

5. You want to write a server that handles multiple clients one after another using sockets. Which approach correctly applies socket programming basics?

hard

A. Create socket, accept client without binding or listening, communicate, close socket

B. Bind socket, create socket, listen, accept client, communicate, close socket

C. Create socket, bind, accept client, listen, communicate, close socket

D. Create socket, bind, listen, accept client, communicate, close client socket, then accept next client

Solution

1. Step 1: Understand sequential client handling

   The server must create a socket, bind it, and listen before accepting clients one by one.

2. Step 2: Follow correct order for each client

   For each client, accept the connection, communicate, close the client socket, then accept the next client.

3. Final Answer:

   Create socket, bind, listen, accept client, communicate, close client socket, then accept next client -> Option D

4. Quick Check:

   Correct socket lifecycle for multiple clients = Create socket, bind, listen, accept client, communicate, close client socket, then accept next client [OK]

Hint: Bind and listen once; accept and close per client [OK]

Common Mistakes:

• Accepting without binding or listening
• Calling listen after accept
• Binding before creating socket