Ransford's Notes

Core path

Your path through this level

Progress saves in this browser and syncs after you sign in

Completed

0 of 8

Pick up where you left off

Layers are responsibilities PDU naming prevents confusion Mapping is approximate What belongs where Names to addresses Subnet reasoning Request flow Prove the layer

Optional

Full module map

Use this if you want the shape of the level before you start

Show

Module 1.1Layers are responsibilities

Use models to isolate problems. Do not treat layers like folders on disk.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain layers are responsibilities in your own words and apply it to a realistic scenario.
Use models to isolate problems. Do not treat layers like folders on disk.
Check the assumption "The model is not the network" and explain what changes if it is false.
Check the assumption "Evidence beats confidence" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Chanting layers. Layer talk can hide uncertainty. The goal is a testable statement.
Skipping order. If you skip steps, you misdiagnose. Follow the chain from names to transport to encryption to application.

Module 1.2PDU naming prevents confusion

Segment, packet, and frame are not synonyms. Naming the unit clarifies the layer.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain pdu naming prevents confusion in your own words and apply it to a realistic scenario.
Segment, packet, and frame are not synonyms. Naming the unit clarifies the layer.
Check the assumption "Encapsulation has direction" and explain what changes if it is false.
Check the assumption "You can name the unit" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Packet for everything. Using one word for everything hides the problem. Be precise.
Mixing data and headers. People forget which headers belong to which layer. The model fixes that.

Module 1.3Mapping is approximate

OSI and TCP/IP map loosely. Do not force a perfect one to one story.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain mapping is approximate in your own words and apply it to a realistic scenario.
OSI and TCP/IP map loosely. Do not force a perfect one to one story.
Check the assumption "The mapping is a learning aid" and explain what changes if it is false.
Check the assumption "Real stacks blur layers" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
One to one myth. Forcing a perfect mapping creates confident wrong answers.
Treating layers as ownership. Layers are responsibilities, not team boundaries.

Module 1.4What belongs where

Layer thinking works when you can place a protocol at a layer for a reason.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain what belongs where in your own words and apply it to a realistic scenario.
Layer thinking works when you can place a protocol at a layer for a reason.
Check the assumption "You can justify placement" and explain what changes if it is false.
Check the assumption "Boundaries are conceptual" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Layer confusion. If you cannot say what a layer does, you cannot troubleshoot it.
Blaming a layer. Layers are not enemies. They are a way to ask the right next question.

Module 1.5Names to addresses

Names are for humans. Addresses are for routing. DNS is the bridge.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain names to addresses in your own words and apply it to a realistic scenario.
Names are for humans. Addresses are for routing. DNS is the bridge.
Check the assumption "Caching exists" and explain what changes if it is false.
Check the assumption "You can inspect" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
DNS blamed without proof. DNS is often the cause, but not always. Test it.
Stale cache surprises. Old answers can persist. Know where caching occurs.

Module 1.6Subnet reasoning

Subnetting is about what is local, what is routed, and what must be sent to a gateway.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain subnet reasoning in your own words and apply it to a realistic scenario.
Subnetting is about what is local, what is routed, and what must be sent to a gateway.
Check the assumption "CIDR is a model" and explain what changes if it is false.
Check the assumption "Gateways exist" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Off by one ranges. Small mistakes create big confusion. Work carefully and verify.
Mixing address and network. A host address and a network address are different things. Keep them separate.

Module 1.7Request flow

A web request is a chain. Diagnose the chain step by step.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain request flow in your own words and apply it to a realistic scenario.
A web request is a chain. Diagnose the chain step by step.
Check the assumption "Order matters" and explain what changes if it is false.
Check the assumption "Each step is testable" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Misdiagnosed slowness. People blame the server when DNS is slow, or blame the network when the server is slow. Measure.
Skipping evidence. Troubleshooting without evidence becomes superstition.

Module 1.8Prove the layer

A good troubleshooting note states the layer, the evidence, and the next test.

Open

Prerequisites

No previous technical background required
Read the section explanation before using tools

Outcomes

Explain prove the layer in your own words and apply it to a realistic scenario.
A good troubleshooting note states the layer, the evidence, and the next test.
Check the assumption "You state assumptions" and explain what changes if it is false.
Check the assumption "You change one variable" and explain what changes if it is false.

Practice

Complete one guided exercise and explain your decision in plain language
Use the recap only after reading the main section

Artefact and failure modes

A short module note with one key definition and one practical example
Guessing. Guessing is how problems become long and expensive. Tests are cheaper.
Tool worship. Tools help, but the model is what makes tool output meaningful.

What changes at this level

Level expectations

Each level is independent but clearly deeper than the last. This panel makes the jump explicit.

Learning contract

Assessment outcomes

Read the explanation first, then use the tools to test the idea. Skip any tool that is not useful for your goal.

Network models certification assessment. Foundations

Timed assessment with free access. You need an account so attempts and certificate naming stay attached to you.

Practice before your timed attempt

Complete summary practice if any layer diagnostics feel weak.
Review one real troubleshooting flow before you begin.
Sign in and start the timed attempt when your reasoning is stable.

See sample questions Practice first Summary and games Sign in Track CPD

Assessments issue certificates and need your name. Sign in to continue.

Before you start

First-try attempts that reach the top 20 may be invited to publish to a child-safe public leaderboard.

You choose whether to publish. If you decline, your top 20 record is not saved.

Network models certification assessment. Foundations

This assessment is timed. Question count and pass threshold are shown for your session when it loads.

Enter your full name. This name is locked for your certificates.

You can retake as many times as you like. Attempts are tracked. Recent questions are avoided when possible.

Rules

Time limit is 75 minutes.
The question count is shown when your session loads.
The pass threshold is shown in your attempt details.
You can retake and attempts are tracked.
Copy and context menu actions are restricted to reduce casual cheating.

Track CPD Back to course

Course materials are protected by intellectual property rights.View terms

Preparing the page...