Developing a network (internal)
Internal 4 credits IP addressing Subnets DHCP Security TestingAS 91895, 4 credits. Build and document a network using advanced techniques — addressing, segmentation and security — INVESTIGATING the parts and components used, then prove it works and meets the end users' requirements, on the shared develop → informed → refined ladder.
1 Reading the notation
Diagnosis and troubleshooting are named explicitly — not just proving things work.📖 Terms the schedule grades you on
4 terms- Develop (Achieved)
- Install/configure; test/diagnose/troubleshoot errors; INVESTIGATE parts/components; explain implications.
- Informed (Merit)
- Use testing info to improve quality; EXPLAIN purpose/function of parts; address implications.
- Refined (Excellence)
- Accurately meet end-user requirements; JUSTIFY the parts/components chosen.
- Network
- A set of computing devices connected to share resources and/or exchange data.
2 What each grade requires
The develop → informed → refined ladder shared across the "advanced techniques" family.| Grade | What it takes | The half people drop |
|---|---|---|
| Achieved | Advanced techniques for the purpose/end users; data integrity and testing; EXPLAIN implications | Explaining an implication in the abstract, unconnected to this outcome |
| Merit ("informed") | Use information FROM TESTING to improve quality; ADDRESS implications with a visible decision | Testing that never feeds back into an actual change |
| Excellence ("refined") | ITERATIVE improvement across design/development/testing; JUSTIFY the choices made | One single round of testing, not a genuine iteration loop |
The verb escalates every time: explain → address → justify. Each is a distinct, checkable action, not just "more effort".
3 Addressing, subnets, and name resolution
The local-or-remote decision the subnet mask exists to make.What the evidence must show
- Requirements: who needs to reach what, and what must be separated.
- A topology diagram with devices, links and subnets labelled.
- An addressing plan: subnets, masks, gateway, static reservations.
4 Security, testing, and documentation
Proving forbidden traffic fails is the half that actually evidences the security design. ✕Testing only what should work
Confirming permitted traffic flows correctly is only half the evidence. A security design must also prove blocked traffic actually FAILS — attempt the forbidden connection and show it does not succeed, rather than only showing the allowed paths.5 Devices, and explaining their purpose
Switch vs router, and the standard's own named hardware categories.What "explaining purpose and function" needs
- Every device type actually used, named.
- What job each one does in THIS network.
- Why it was needed, not just that it is present.
Practice
Recall it first, then use it — testing yourself builds the memory, where rereading the notes above only feels easier.
Recall and application shuffled together — you have to work out what each item wants before you can answer it, which is the part the exam actually tests. Both kinds feed the same spacing schedule, so anything you miss comes back sooner.
Say the answer out loud before flipping — that attempt is where the learning happens, even when you get it wrong.
Exam-style only. Instant feedback, shuffled each attempt, best score saved on this device.