START WITH THE FOUNDATIONS

IT & Networking Foundations

Trace packets, compare throughput with delay and recognize address boundaries.

Free · No sign-in required3 lessonsWorked examples & practiceBeginner

0 of 3 lessons checked · Progress is saved in this browser.

  1. 01 / SYSTEM VIEWEndpoint
  2. 02 / SYSTEM VIEWNetwork path
  3. 03 / SYSTEM VIEWService

This map connects the course ideas; it is not a detailed engineering schematic.

LESSON 1 / 3 · FREE

Packets and network roles

Your goal: Separate switching, routing and application services.

Understand the idea

An endpoint sends data through interfaces and network devices to a service. Switching and routing operate at different scopes; DNS resolves names rather than carrying every application response. A connection can fail at addressing, transport, name resolution or the application, so identify the layer being tested.

Worked example

A teaching transfer sends 8 megabits over a constant usable 4 megabits/s path. Serialization alone takes 2 seconds, before propagation, processing or protocol effects.

Try it yourself

At a usable 10 megabits/s, how long does 50 megabits take to serialize?

What does DNS primarily provide?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 2: Bits, bytes and throughput →

LESSON 2 / 3 · FREE

Bits, bytes and throughput

Your goal: Convert file size before estimating transfer duration.

Understand the idea

A byte contains eight bits. Network rates and file sizes must use consistent units; decimal MB and binary MiB are different. An ideal transfer estimate uses usable throughput, not an assurance that a nominal interface rate will be reached. Congestion and overhead can change the result.

Worked example

A decimal 20 MB file contains 160 megabits. At 40 megabits/s usable throughput, the ideal duration is 4 seconds.

Try it yourself

A decimal 30 MB file uses a 60 megabits/s usable path. Find ideal duration.

Does an interface’s nominal rate guarantee application throughput?

Background reference ↗ · Original teaching text and fictional practice values.

Continue to lesson 3: Capacity planning and observability →

LESSON 3 / 3 · FREE

Capacity planning and observability

Your goal: Compare demand with a defined capacity boundary.

Understand the idea

Utilization is demand divided by the capacity being measured over a stated interval. A low average can hide bursts, and available bandwidth does not establish acceptable latency. Record loss, delay, errors and service behavior along with utilization when investigating a complaint.

Worked example

A supplied 1,000 megabits/s link carrying 250 megabits/s averages 25 percent utilization for that interval. This does not exclude short saturation bursts.

Try it yourself

A 200 megabits/s capacity carries 80 megabits/s. Find utilization.

Can a low daily average exclude short congestion events?

Background reference ↗ · Original teaching text and fictional practice values.

Choose your next step →

Finish with evidence of your understanding.

Explain each worked example in your own words, check the units and identify one assumption that could change the result. Then use the linked labs or roadmap to apply the ideas to a broader task.

Practice progress is a study aid, not a professional qualification or proof of field competence.

Continue in Enterprise IT Networks

Apply these foundations in an available course, lab or roadmap. The linked resource’s access rules still apply.

Show 12 more available resources

Open the full studio → · Choose another discipline →

About this introductory course

These original lessons use simplified models and explicitly supplied practice values. Calculations teach concepts; they do not select real equipment, establish code compliance or authorize field work. Follow the linked references and advanced resources for deeper study.

Updated · Study progress stays in this browser. There is no certificate or paid gate for these lessons.