1D0-61A · Question #57
The official CIW Web site has an IP address of 72.44.192.233. Which technology allows the site, instead of having to remember and enter the IP address?
The correct answer is B. DNS. DNS (Domain Name System) acts as the internet's phone book, translating human-readable domain names like www.ciwcertified.com into machine-readable IP addresses like 72.44.192.233 - so users never need to memorize numeric addresses. A (SSL) is wrong - SSL/TLS handles encryption…
Question
The official CIW Web site has an IP address of 72.44.192.233. Which technology allows the site, instead of having to remember and enter the IP address?
Options
- ASSL
- BDNS
- CHTTP
- DNNTP
How the community answered
(26 responses)- A4% (1)
- B92% (24)
- D4% (1)
Explanation
DNS (Domain Name System) acts as the internet's phone book, translating human-readable domain names like www.ciwcertified.com into machine-readable IP addresses like 72.44.192.233 - so users never need to memorize numeric addresses.
- A (SSL) is wrong - SSL/TLS handles encryption and secure communication, not name resolution.
- C (HTTP) is wrong - HTTP is the protocol for transferring web pages, not for resolving names to addresses.
- D (NNTP) is wrong - NNTP (Network News Transfer Protocol) is for Usenet newsgroups, completely unrelated to name resolution.
Memory tip: Think of DNS as a Directory for Names to Search - just like a phone book maps a person's name to their number, DNS maps a domain name to an IP address.
Topics
Community Discussion
6DNS, Domain Name System, is the answer here. Think of it as the internet's phone book: it maps human-readable hostnames like www.ciwcertified.com to machine-readable IP addresses like 72.44.192.233, so users never have to memorize numeric strings. SSL (A) handles encryption, HTTP (C) is the transfer protocol for web pages, and NNTP (D) is for newsgroups, none of which perform name-to-address resolution. The correct answer is B, DNS.
The phone book analogy is solid, though a modern spin helps: think of DNS less like a static phone book and more like a live dispatch operator, since records get updated constantly via TTL-controlled caches rather than sitting in a printed edition that goes stale overnight.
I went with D on this one because NNTP is the protocol that handles the translation layer between human-readable names and the underlying network addressing, and when I spun up a local server to test name resolution in my home lab, the NNTP configuration was the piece that made the friendly address work instead of the raw numbers.
Ola, what you are describing is actually DNS, Domain Name System, which is option B, the protocol responsible for resolving human-readable hostnames to their corresponding IP addresses. NNTP, Network News Transfer Protocol, is a completely separate protocol designed for distributing and retrieving Usenet newsgroup articles, so whatever name resolution you observed in your lab was DNS doing the work behind the scenes, not NNTP.
I keep coming back to D on this one and here is my thinking. Picture a big community bulletin board at a library, where instead of remembering every librarian's extension number, you just look up their name on the board and it points you where to go. NNTP works as that kind of network-wide directory service that organizes and distributes information across nodes so you do not have to track raw numbers yourself. The way I see it, the question is really asking what handles the translation layer between a human-readable name and a numeric address on the network, and NNTP fits that role of being the connective tissue that passes identifiers between systems. I know some folks jump to B right away but DNS feels like it is more about caching than active resolution in a live browsing scenario, whereas NNTP is the protocol actually moving that lookup information through the news and network infrastructure in real time.
Mateus, your bulletin-board analogy is spot on, but it actually describes DNS perfectly: DNS is the protocol that translates human-readable hostnames into numeric IP addresses, while NNTP is a completely separate protocol designed for distributing Usenet newsgroup articles and has no role in name-to-address resolution.