Inspect
Review the problem, diagram, and evidence.
The subnet looked large enough from the address range. The usable host count said otherwise.
Inspect, commit, prove, fix, and sign off.
Follow the investigation process used in the field β in five guided steps.
Review the problem, diagram, and evidence.
Choose your hypothesis.
Run calculations and test your idea.
Select and validate a safe correction.
See the full debrief and key takeaways.
A lab needs addresses for 40 IPv4 devices on one subnet. The proposed network is 192.168.10.0/27. The planner sees 32 addresses in the block and assumes the subnet is close enough. During deployment, addresses run out. Calculate the usable host capacity, identify the design error, and choose the smallest larger prefix that can support at least 40 hosts.
Find the root cause, confirm the fix, and see how this connects to the exam.
The /27 subnet could not support 40 host devices.
All addresses in the block were treated as usable hosts.
Calculate total addresses from host bits, then subtract network and broadcast addresses for conventional IPv4 host capacity.
An IPv4 /27 prefix leaves 5 host bits, so the block contains 2^5=32 total addresses. Reserving the network and broadcast addresses leaves 30 usable host addresses. A /26 provides 62 usable hosts and can support 40 devices.
For a conventional IPv4 subnet, total addresses are 2^(32-prefix), and usable host addresses are total minus 2.
30 usable hosts in a conventional IPv4 subnet.
A /26 provides 62 usable host addresses.
Each case is designed to build the judgment, analysis, and confidence you need for engineering exams β and beyond.
Basic subject familiarity helps, but every case is designed to teach through the investigation itself.
Most cases are designed for a focused 5β10 minute investigation.
Each case is mapped to a verified exam, subject, topic, and misconception before publication.
The sealed debrief unlocks with the root cause, corrected reasoning, fix, and takeaway.