S6 ICT: network models and OSI encapsulation (challenge)
- 2026-11-20
S6 ICT: network models and OSI encapsulation (challenge)
Challenge: fragmentation, jumbo frames and throughput, from three fragments to round trip stacking and bandwidth conversion.
Challenge: fragments, jumbo frames, throughput The third paper pushes encapsulation to its limits. A 3000 byte datagram over an MTU of 1500 becomes 3 fragments because each carries its own 20 byte IP header, leaving 1480 bytes of data per fragment. A 9000 byte jumbo frame allows 8960 bytes and cuts the header share from 2.67 to 0.44 percent. 100 Mbps is 12.5 megabytes per second, so a 20 megabyte file needs about 1.6 seconds, while DNS, the handshake and TLS take 4 round trips of 30 milliseconds, or 120 milliseconds. It closes on end to end delivery and the claim that OSI is the real stack.
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 |
| Suggested time | 25 |
| Difficulty mix | Foundation 3 · Intermediate 3 · Challenge 3 · Error redo 1 |
| Chapter | Chapter: S6 ICT: Network Models and OSI Encapsulation |
| Level | Challenge (10 items) |
02 Questions (10 items)
- FoundationA 3000 byte IP datagram crosses a link with an MTU of 1500. How many fragments result?
- FoundationA jumbo frame has an MTU of 9000 bytes. What is the largest TCP payload?
- FoundationOf the seven OSI layers, how many count as upper layers and which are they?
- IntermediateRaising the MTU from 1500 to 9000 cuts the header share from 2.67 percent to what?
- IntermediateHow many megabytes per second can a 100 Mbps link theoretically carry?
- IntermediateOpening a secure session uses one RTT for DNS, one for the TCP handshake and two for TLS, with an RTT of 30 ms. How long is the wait?
- ChallengeOn a 12.5 megabyte per second link, how long does a 20 megabyte file take at best?
- ChallengeIf the payload grows from 1000 to 2000 bytes with the same headers, what is the new frame length?
- ChallengeWhich layer provides end to end reliable delivery, and why?
- Error redoError item: OSI is the protocol actually used while TCP/IP is only theory. What is wrong?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | 3 fragments: 1480 plus 1480 plus 20. | Each fragment carries its own 20 byte IP header, so only 1480 bytes of data fit. |
| 2 | 8960 bytes. | 9000 minus 40 gives 8960. |
| 3 | 3: session, presentation and application. | The lower four move bits to the peer host; only the upper three handle meaning. |
| 4 | 0.44 percent. | 40 over 9000 is 0.44 percent, so larger packets waste less. |
| 5 | 12.5 megabytes. | 100 divided by eight is 12.5, since bits and bytes differ by a factor of eight. |
| 6 | 120 milliseconds. | 4 round trips times 30 milliseconds is 120, before any server processing. |
| 7 | 1.6 seconds. | 20 divided by 12.5 is 1.6, ignoring delay, headers and congestion. |
| 8 | 2058 bytes. | Headers stay at 58, so 1000 more payload means 1000 more frame. |
| 9 | The transport layer, layer four. | The network layer only reaches host to host; retransmission and ordering belong to layer four. |
| 10 | It is the reverse: TCP/IP is the deployed stack and OSI is a reference model. | OSI is used for teaching and describing layers; the implementation in use is TCP/IP. |
04 What to do after marking
- After marking, redo only the wrong items and write down which step went wrong (formula, unit, or misread number).
- Repeat the same item two days later; move to the next paper only when both attempts are correct.
- Parents only need the answer and note columns; there is no need to explain every item.
Want to trace encapsulation hop by hop? Book a TutorZone tutor and unpack all ten items layer by layer in 25 minutes.Tutor Registration →
Questions and answers are written originally by the TutorZone team and are not taken from any school, publisher or examination authority paper. Every value is checked by computer.



