Which sequence correctly describes how a web server delivers a web page to a user's computer?

Which sequence correctly describes how a web server delivers a web page to a user's computer?

• A. The server sends a single large file without splitting into packets.
• B. When a URL is typed into the address bar, the web server sends the requested page as a series of packets, which are reassembled by the NIC and rendered by the browser.
• C. The browser renders the HTML after the server sends the packets.
• D. The DNS resolves the URL and nothing is transferred over the internet.

Answer: (B)

Web pages are delivered over the internet in packets and must be reassembled before the browser can display them. When you request a page, the server sends the content in many small packets using TCP. These packets travel across the network and are reassembled into the complete HTML by the receiving device’s network stack, after which the browser parses the HTML and renders the page. So the sequence is packetized delivery, reassembly, then rendering in the browser. This matches the idea that the server sends the page as a series of packets, which are reassembled, and then rendered by the browser. The other statements don’t fit: data isn’t sent as a single large file over the internet; rendering typically waits for the data to be correctly reassembled; and DNS resolves a domain to an IP, but actual page data is transferred afterward.

Web pages are delivered over the internet in packets and must be reassembled before the browser can display them. When you request a page, the server sends the content in many small packets using TCP. These packets travel across the network and are reassembled into the complete HTML by the receiving device’s network stack, after which the browser parses the HTML and renders the page. So the sequence is packetized delivery, reassembly, then rendering in the browser. This matches the idea that the server sends the page as a series of packets, which are reassembled, and then rendered by the browser. The other statements don’t fit: data isn’t sent as a single large file over the internet; rendering typically waits for the data to be correctly reassembled; and DNS resolves a domain to an IP, but actual page data is transferred afterward.