35  Layered Models: Knowledge Checks

In 60 Seconds

Test your understanding of network layering through scenario-based questions covering encapsulation overhead calculations, MAC vs. IP vs. port addressing distinctions, ARP resolution mechanics, layer-by-layer troubleshooting, and subnet calculations – all applied to IoT contexts like smart agriculture and industrial monitoring.

35.1 Learning Objectives

By the end of these knowledge checks, you will be able to:

  • Apply encapsulation concepts: Trace data flow through network layers with header addition/removal
  • Explain addressing: Distinguish MAC, IP, and port addressing at different layers
  • Apply ARP: Understand IP-to-MAC resolution for local network communication
  • Troubleshoot by layer: Use systematic layer-by-layer approach to diagnose network issues
  • Calculate subnets: Determine network addresses, broadcast addresses, and usable host ranges

35.2 Prerequisites

Required Chapters:

Estimated Time: 20 minutes

Purpose: These questions test deep understanding, not memorization. Each explanation reveals the reasoning behind correct answers.

Strategy:

  1. Read the scenario carefully
  2. Think through your answer before looking at options
  3. Select your choice
  4. Study the explanation even if correct

Scoring guidance:

  • 0-40%: Review the model comparison chapter
  • 40-70%: Good foundation, review explanations
  • 70-100%: Strong understanding, ready for advanced topics

35.3 Understanding Checks

Scenario: You’re designing a smart agriculture system where soil moisture sensors send readings to a cloud analytics platform. Each sensor transmits a 20-byte reading through Wi-Fi. When you analyze the network traffic, you discover each transmission actually sends 62 bytes (20-byte payload + 8-byte UDP + 20-byte IP + 14-byte Ethernet).

Think about:

  1. Why does a 20-byte sensor reading require 62 bytes on the network?
  2. Which layer adds routing information to help data find its way from farm to cloud?

Key Insight: The Network Layer (Layer 3) adds the 20-byte IP header containing source and destination addresses, enabling routers to forward your sensor data across the internet. Without this addressing, your data would be trapped on the local network. UDP (Transport Layer 4) adds reliability options, Ethernet (Data Link Layer 2) adds local delivery addressing, and the Physical Layer converts everything to radio signals.

Verify Your Understanding:

  • If you deploy 100 sensors transmitting every minute, how much of your cellular bandwidth is consumed by protocol overhead? (Answer: 42 bytes overhead / 62 total = 68% overhead! This explains why edge processing and data aggregation save significant bandwidth costs.)

Scenario: Your smart factory uses Zigbee sensors on the factory floor communicating with a gateway that forwards data to the cloud via Ethernet. A sensor sends a temperature reading that arrives at the gateway via Zigbee radio, and the gateway must forward it to the cloud server.

Think about:

  1. What happens to the packet headers as it transitions from Zigbee to Ethernet?
  2. Which OSI layers remain unchanged through this translation?

Key Insight: The gateway operates at Layers 1-3, performing protocol translation. It strips the Zigbee Physical (L1) and MAC (L2) headers, extracts the IP packet (L3+), then wraps it in new Ethernet L2 and Physical L1 headers. Critically, the IP addressing (L3), TCP/UDP ports (L4), and application payload (L7) remain completely unchanged. This is why IP-based IoT protocols work so well - they provide end-to-end addressing independent of the underlying wireless technology.

Verify Your Understanding:

  • Why can your sensor reading traverse Zigbee to Ethernet to Wi-Fi to Cellular networks seamlessly? (Answer: Because Layer 3 IP addressing is preserved throughout, while only Layers 1-2 change at each hop.)

Scenario: You’re deploying battery-powered environmental sensors in a remote forest using IEEE 802.15.4 radios (127-byte maximum frame size). Each sensor reading is only 4 bytes, but after adding UDP (8 bytes), IP (20 bytes), and 802.15.4 headers (25 bytes), you’re transmitting 57 bytes per reading.

Think about:

  1. Why is 93% of your transmission just overhead (53 bytes overhead / 57 total)?
  2. How can you extend battery life given that radio transmission dominates power consumption?

Key Insight: For tiny IoT payloads, protocol overhead is massive. Solutions: (1) Payload aggregation - buffer 10 readings locally (40 bytes payload) and send one packet. Overhead drops to 53/93 = 57% instead of 93%. (2) Header compression - 6LoWPAN compresses IPv6 headers from 40 bytes to ~6 bytes using context. (3) Application optimization - use CoAP (binary) instead of HTTP (text) for the application protocol.

Verify Your Understanding:

  • If your sensor transmits once per minute at SF10 (247ms airtime), what percentage of time is the radio active? How much longer would the battery last if you aggregate 10 readings? (Answer: Currently 0.04% duty cycle. With 10x aggregation, same data delivered with 10x fewer transmissions = ~10x battery life extension from 1 year to 10 years!)

35.4 Multiple Choice Questions

35.5 Multi-Select Questions

35.6 Matching Questions

35.7 Design Challenge

35.8 Summary

These knowledge checks tested your understanding of:

  • Layer-by-layer troubleshooting: Using ping, curl, and other tools to isolate failures
  • Encapsulation overhead: Why tiny IoT payloads have massive protocol overhead (93%+)
  • MAC vs IP addressing: Layer 2 local delivery vs Layer 3 global routing
  • ARP operation: Broadcast requests and unicast replies for IP-to-MAC mapping
  • Subnet calculations: Network address, broadcast, and usable host ranges
  • OSI/TCP-IP mapping: How 7 layers compress to 4 layers
  • IoT reference models: Why IoT needs layers beyond traditional networking

35.9 What’s Next

Continue your learning with resources and visual references:

Or apply your knowledge: