HP JBT study materials
HP JBT study resources

HP JBT: Networking and Web Technologies

HP JBT · Work through your exam, one topic at a time.

All guide sections

Networking and Web Technologies

What this domain tests

Networking and web technologies covers the TCP/IP model, addressing and subnetting, transport protocols, DNS, HTTP, TLS, and web application basics such as REST, cookies, and same-origin policy.

Core rules

  • TCP is connection-oriented, reliable, ordered, and uses a three-way handshake; UDP is connectionless and does not guarantee delivery.
  • IPv4 addresses are 32 bits; a /24 has 256 addresses, 254 usable after network and broadcast.
  • DNS resolves names to addresses; caching at resolver, OS, and browser reduces latency but can serve stale records until TTL expires.
  • HTTP is stateless; cookies and sessions add state. Status codes: 2xx success, 3xx redirect, 4xx client error, 5xx server error.
  • HTTPS is HTTP over TLS, providing confidentiality, integrity, and server authentication.
  • REST uses resources and HTTP verbs; GET should be safe and idempotent; PUT and DELETE are idempotent; POST generally is not.
  • Same-origin policy compares scheme, host, and port; CORS relaxes it with server headers.

Worked example

Split 192.168.1.0/24 into four equal subnets. Borrow 2 bits: new prefix /26. Block size is 64 addresses. Subnets: .0/26 with usable .1-.62, .64/26 with .65-.126, .128/26 with .129-.190, and .192/26 with .193-.254. Each has 62 usable hosts because 64 minus network and broadcast. Borrowing bits doubles the number of subnets and halves hosts per subnet.

Traps

Counting the network and broadcast addresses as usable. Confusing a /26 mask (255.255.255.192) with a /24. Assuming HTTPS encrypts the destination IP or DNS query by itself. Treating 301 and 302 as interchangeable for SEO and caching. Forgetting that CORS is enforced by the browser, not the server. Assuming UDP is always faster in every application.