QuizzesWhat Happens When You Type a URL — Concept Check
advanced
computer-networks

What Happens When You Type a URL — Concept Check

Questions on What Happens When You Type a URL. The classic interview question: typing "https://google.com" triggers a precise sequence spanning DNS resolution, TCP connection, TLS handshake, HTTP request, server processing, and browser rendering — touching nearly every layer of the network stack.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on What Happens When You Type a URL — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.After typing 'http://example.com', the browser loads the page over HTTPS. Why?

    • AThe DNS server redirects to HTTPS.
    • BThe browser defaults to HTTPS for all URLs.
    • CThe server forces HTTPS using a redirect.
    • DThe site enforces HTTPS via HSTS.
  2. 2.A user complains that 'https://example.com' is slow to load. DNS queries show repeated lookups. What could be optimized?

    • AIncrease the server's bandwidth.
    • BEnable DNS caching in the browser.
    • CUse a different domain registrar.
    • DSwitch to a faster DNS server.
  3. 3.During a TLS handshake, the browser fails to validate the server's certificate. What might be the cause?

    • AThe server's IP address changed recently.
    • BThe server uses a self-signed certificate.
    • CThe certificate chain is incomplete.
    • DThe browser has outdated root certificates.
  4. 4.Why might a browser fetch resources from a CDN edge rather than the origin server?

    • AOrigin servers are always slower than CDN edges.
    • BCDN edges reduce latency by being geographically closer.
    • CBrowsers prefer CDN edges for security reasons.
    • DCDN edges have more bandwidth than origin servers.
  5. 5.A webpage's JavaScript is blocking rendering. What is a potential solution?

    • ASwitch to a faster DNS provider.
    • BLoad JavaScript after all HTML is parsed.
    • CIncrease the server's processing power.
    • DUse the 'async' or 'defer' attribute in script tags.
  6. 6.What happens if a browser can't find a domain in its DNS cache or the OS cache?

    • AIt performs a full recursive DNS lookup.
    • BIt defaults to a backup domain.
    • CIt uses the last known IP address.
    • DIt switches to a different DNS protocol.
  7. 7.Why might a browser upgrade an HTTP request to HTTPS before any network request is made?

    • AThe domain is on the HSTS preload list.
    • BThe browser defaults to HTTPS for security.
    • CThe DNS server mandates HTTPS.
    • DThe server enforces HTTPS via redirects.
  8. 8.A website's HTML loads, but images and CSS are missing. What could be the issue?

    • AThe browser's cache is full.
    • BThe resources are blocked by CORS policy.
    • CThe DNS server is misconfigured.
    • DThe server is down for maintenance.