Computer Networks: TExES Computer Science 8-12 241
A computer network connects devices so they can exchange data and share resources.
- For TExES Computer Science 8-12 (241), distinguish LANs and WANs, domain names and IP addresses, ports and protocols, and services such as DNS and DHCP.
- A browser request uses several layers; HTTP does not imply that every exchange uses TCP.
On this page12 sections
- What does a network connect?
- Names, addresses, and ports answer different questions
- What does DHCP do?
- Follow a fictional browser request
- TCP provides a reliable ordered byte stream
- Application protocols and layers
- Wireless access, routers, and switches
- Network security and responsible use
- Separate common network failures
- A study method for network questions
- Client-server and peer communication
- How the topic appears on TExES 241
Networking appears in the Computer Science 8-12 (241) framework’s technology core, which calls out networks such as LANs, WANs, intranets, and the Internet. This guide explains the basic roles of common terms and follows a fictional browser request. It stays at an introductory level and avoids treating one typical configuration as a rule for every network.
What does a network connect?
A network links computing devices so they can communicate, access services, and share resources. A local area network, or LAN, serves a limited setting such as a home, office, or school. A wide area network, or WAN, connects networks over larger geographic areas. The Internet is a global interconnection of networks that communicate using the Internet Protocol suite. An intranet is a private network or collection of services intended for an organization’s users, though it may use Internet technologies.
These labels describe different aspects of a network. A device might connect to a school LAN that reaches an organization’s WAN and accesses services through the public Internet. Network boundaries, ownership, and security policy matter. The phrase “on the Internet” does not tell you whether a service is publicly accessible, what address it uses, or which users are authorized.
Names, addresses, and ports answer different questions
A domain name is a human-readable name used to identify a service or host in a naming system. An IP address identifies a network-layer endpoint for routing packets. DNS, the Domain Name System, helps translate a domain name into DNS records, which may include one or more IP addresses and other service information. The relationship is not permanently one name to one fixed address: records can change, and a service can use multiple addresses.
A port number identifies an application endpoint on a host in transport-layer protocols such as TCP or UDP. An IP address helps route data to a host; a port helps deliver it to the appropriate transport service. A URL may specify a scheme, host name, port, and resource path. These pieces are related but not interchangeable. A port is not a physical socket, and DNS does not itself deliver the web page.
| Term | Role | Question it helps answer |
|---|---|---|
| Domain name | Human-readable name in DNS | Which named service is requested? |
| IP address | Network-layer destination or source | Where should packets be routed? |
| Port | Transport-layer application endpoint | Which service on a host is involved? |
| DNS | Name-resolution system | What records are associated with this name? |
| DHCP | Configuration protocol/service | How can a device obtain network settings? |
| HTTP | Application-layer web protocol | How does a client request and receive web resources? |
What does DHCP do?
Dynamic Host Configuration Protocol, or DHCP, can provide a device with network configuration such as an IP address, subnet information, a default router, and DNS server settings. Details depend on the network and its configuration. DHCP is distinct from DNS: DHCP helps a device obtain configuration, while DNS resolves names using records. A device can have a valid address and still fail to resolve a particular name, or resolve a name and then fail to reach the service.
The distinction is practical when troubleshooting. If a new device has no expected network configuration, DHCP may be relevant. If the device can reach a known address but cannot resolve a host name, examine name-resolution configuration. If a name resolves but a connection attempt fails, the cause may be routing, a firewall, a port, server availability, or another condition. These are diagnostic categories, not a guarantee about a specific failure.
Follow a fictional browser request
Imagine a student enters https://library.example/resource in a browser. The browser parses the URL and identifies a host name, scheme, and requested path. It may use cached information, but if name resolution is needed, the system asks DNS infrastructure for relevant records. The response may supply an IP address or direct the resolver through other records. DNS resolution does not guarantee that the destination is reachable or that the resource exists.
The client then needs a way to communicate with the destination. Depending on the protocol and configuration, it may establish a transport connection or use another transport. The destination address identifies where traffic is routed; a port identifies the intended service endpoint for protocols that use ports. Security mechanisms such as TLS may establish and protect a session. The browser then sends an application-level request for the resource, and the server or intermediary returns a response.
If the response contains a link to an image, stylesheet, or script, the browser may make additional requests. A page can therefore involve more than one host, address, connection, and application response. A successful DNS lookup is only one stage in the process. A name may resolve while the server is down, the route is blocked, the service refuses a connection, or the application returns an error response.
TCP provides a reliable ordered byte stream
Transmission Control Protocol, or TCP, provides a connection-oriented, reliable, ordered byte-stream service to applications. Its mechanisms use sequence information and acknowledgments, and can retransmit data when needed. The application can read a stream of bytes, but TCP does not preserve application message boundaries. An application protocol must define how its messages are framed or interpreted.
Reliability does not mean delivery regardless of failure. A connection can break, a host can stop responding, or an application can fail. TCP mechanisms help detect and recover from some loss and ordering problems while a connection remains usable, but they cannot guarantee that a remote application processed a request or committed a transaction. Applications often need their own error handling and confirmation logic.
Do not say that all HTTP traffic uses TCP. HTTP/1.1 and HTTP/2 are commonly carried over TCP with TLS for HTTPS, while HTTP/3 uses QUIC, which is carried over UDP. For an introductory question, identify what transport is specified rather than assuming a universal mapping from HTTP to TCP.
Application protocols and layers
Protocols define rules for communication. HTTP is an application protocol for web requests and responses. DNS has its own query and response formats. TCP and UDP are transport protocols, and IP supports addressing and routing at the network layer. A simplified layered model helps assign responsibilities, but real implementations include details and interactions that a diagram can hide.
Layering is useful because the same application can use different lower-level technologies, and different applications can share transport services. It also helps diagnose problems. If an application response arrives, some lower-level connectivity worked for that transaction; if the connection cannot be established, the application may never receive a request. Still, do not infer a single precise fault merely from a symptom without evidence.
Wireless access, routers, and switches
A switch commonly forwards frames within a local network based on link-layer information. A router forwards packets between networks using network-layer routes. A wireless access point provides a way for wireless devices to join a network; it may be integrated with routing and switching functions in a consumer device. These roles are conceptually distinct even when one physical box performs several of them.
A network diagram should identify interfaces and boundaries instead of labeling every box generically as “the router.” A packet’s route may cross multiple devices and administrative domains. Network address translation, firewalls, proxies, and load balancers can change what a client observes. Those technologies are beyond a basic name-resolution explanation, but they help explain why one name may be served by several endpoints or why a client’s local address differs from a public service’s view.
Network security and responsible use
Network access is governed by authorization, acceptable-use rules, privacy obligations, and technical controls. A network diagram or packet capture can reveal sensitive data, so analysis should use systems and data the learner is authorized to inspect. Encryption can protect data in transit, but it does not establish that a user, device, or application is trustworthy. Authentication, authorization, secure configuration, and endpoint protections address different questions.
For an educational scenario, favor safe diagnosis: verify the intended network, check approved configuration, consult documentation, and escalate access problems through the responsible administrator. Do not test credentials or scan systems without explicit authorization. The 241 framework includes digital safety, privacy, and lawful technology use alongside its technical competencies, so sound computing practice includes both conceptual accuracy and responsible conduct.
Separate common network failures
| Observed symptom | Possible layer or service to inspect | What the symptom does not prove |
|---|---|---|
| Name cannot be resolved | DNS settings, records, resolver reachability | That the web server is down |
| Known address is unreachable | Local link, routing, filtering, destination status | That DNS is broken |
| Connection is refused or times out | Port, service state, route, filtering, server load | That the application returned an HTTP error |
| HTTP error response received | Application or intermediary response | That IP routing failed |
| Page loads but content is wrong | Application data, cache, version, permissions | That the network transport corrupted it |
The same visible problem can have several causes, and different layers can fail independently. A DNS answer can be stale; a firewall can block one port while allowing another; a server can accept a connection and then return a not-found response. Distinguish a failure to resolve a name, a failure to establish communication, and an application-level response. That vocabulary makes both troubleshooting and selected-response reasoning more precise.
A study method for network questions
- Draw the client, local network, resolver, and destination as separate roles.
- Mark the name, address, transport endpoint, and application resource separately.
- Trace which service acts at each step and what result it returns.
- Identify the layer named in the question before selecting a troubleshooting action.
- Check whether the prompt says TCP, UDP, HTTP version, TLS, or another protocol.
- Avoid turning common configurations into universal requirements.
Try explaining a scenario without relying on jargon: a name is looked up, an address is used to route packets, a transport endpoint is contacted, and an application exchange requests a resource. Then attach terms such as DNS, IP, port, TCP, or HTTP to the correct stage. If the explanation still works after removing a brand name or vendor product, you likely understand the protocol roles rather than a single interface.
Client-server and peer communication
Many network services follow a client-server pattern. A client initiates a request, while a server offers a service and responds. The roles describe an interaction, not necessarily permanent hardware categories: one computer can act as a client in one exchange and a server in another. Peer-to-peer systems distribute some responsibilities among participating devices. The best model depends on the application, trust requirements, availability needs, and how resources are managed.
A server name also does not guarantee that one physical machine handles every request. A service may use replicas, caches, load balancers, or cloud infrastructure. DNS responses can direct clients to different destinations, and intermediaries can process requests. For foundational exam reasoning, keep the logical service separate from a particular machine unless the scenario explicitly equates them.
How the topic appears on TExES 241
The official framework places network knowledge under Domain I, Technology Applications Core, Competency 001, which explicitly names LANs, WANs, intranets, and the Internet. That domain has an approximate weighting, not a fixed count for any one network concept. A candidate should understand how network terminology relates to hardware, software, digital information, privacy, and troubleshooting.
The exam page describes a 100-question selected-response CAT with a five-hour total appointment. Network questions may ask for a concept distinction or present a scenario. Practice by mapping each symptom to the process stage it concerns, then eliminate choices that assign DNS, DHCP, IP routing, ports, transport, or application protocols the wrong job.
Common questions
Does DNS always return exactly one IP address?
No. DNS can return different record types and multiple addresses. Responses depend on records and configuration and can change over time. For a reliable answer, state the relevant assumption and verify it against the official framework or language documentation before applying it to a new example.
Are a port and an IP address interchangeable?
No. An IP address supports routing at the network layer. A port identifies a transport endpoint on a host for protocols that use ports. For a reliable answer, state the relevant assumption and verify it against the official framework or language documentation before applying it to a new example.
Does TCP preserve application messages?
No. TCP provides an ordered byte stream. The application protocol must define message boundaries or framing. For a reliable answer, state the relevant assumption and verify it against the official framework or language documentation before applying it to a new example.
Does HTTP always use TCP?
No. HTTP/3 uses QUIC over UDP. Identify the HTTP version and transport specified instead of assuming all HTTP uses TCP. For a reliable answer, state the relevant assumption and verify it against the official framework or language documentation before applying it to a new example.