Difficulty: Easy
Correct Answer: All of the above
Explanation:
Introduction / Context:
The client–server model underpins most Internet applications. A client initiates a request, and a server listens and responds. Understanding which common protocols follow this pattern builds intuition about how applications interact over TCP/IP networks.
Given Data / Assumptions:
Concept / Approach:
TELNET clients connect to a TELNET server for remote terminal sessions. FTP clients connect to FTP servers for file operations. DNS resolvers (clients) query authoritative or recursive DNS servers to translate names to addresses. Each follows the core client–server pattern of request/response.
Step-by-Step Solution:
Verification / Alternative check:
Port/service mappings show well-known server ports (e.g., 21 for FTP control, 23 for TELNET, 53 for DNS) with client ephemeral ports making requests, confirming client–server behavior.
Why Other Options Are Wrong:
Common Pitfalls:
Confusing peer-to-peer with client–server; mixing DNS client caching with authoritative service—both still follow a request/response model.
Final Answer:
All of the above
Discussion & Comments