Embedded Files
Learn how to build, configure, test, troubleshoot, and improve a working network that meets a real user need.
This page supports the development of a more complex network for a specific purpose and end user. At Level 3, you are expected to move beyond a simple LAN and show a stronger understanding of how networks are structured, how traffic moves, how services operate, and how testing information is used to improve quality. You will work through the development process in stages: planning the network structure, building the core architecture, applying complex techniques such as routing and network services, and then using testing and troubleshooting to refine the final outcome.
Welcome to Network Development. In this standard, you will learn how to build, configure, test, troubleshoot, and improve a working network. Rather than just learning networking theory, you will work through practical tasks that help you understand how networks function, how devices communicate, and how to make decisions that lead to a network that works reliably for its intended users. AS91905 is a Level 3, 4-credit internal standard focused on using advanced techniques to develop a network.
In this learning area, you will move step by step through the key parts of network development. You will learn how to configure devices and services, use suitable protocols, test connectivity, identify faults, troubleshoot problems, and improve your network using the results of your testing. As you move through the modules, you will also build the evidence needed for assessment.
~~~ OVERVIEW ~~~
~~~ OVERVIEW ~~~
In this learning area, you will design, build, and refine a more complex network. You will begin by investigating the context and planning the network structure, including the devices, services, and routed connections required. You will then build the core network, apply complex techniques such as routing and network services, and use testing and troubleshooting to improve the quality of the final outcome. As you move through each stage, you should collect evidence showing what you built, how you tested it, what problems you found, what changes you made, and why those changes improved the network.
What counts as evidence
What counts as evidence
Evidence for this standard does not need to be one long written report. It can include topology diagrams, screenshots, configuration records, routing tables, ping and tracert results, ICMP-based diagnostic evidence, service configuration, photos, short videos, screencasts, development logs, and brief notes explaining problems found, changes made, and why those changes improved the network. At Level 3, your evidence should also show how your network is structured, how different components behave, and how testing informed your decisions.
If hardware is a barrier, Cisco Packet Tracer can be used as a software-based alternative to simulate networks and practise key networking techniques. It allows students to build, configure, test, and troubleshoot virtual networks, making it a useful way to develop understanding and trial ideas when access to physical equipment is limited.
~~~ Networking Working Documents ~~~
~~~ Networking Working Documents ~~~
AS91895 – Use advanced techniques to develop a network
AS91895 – Use advanced techniques to develop a network
This standard focuses on developing a working network for a specific purpose and end user. Students use advanced techniques to configure, test, troubleshoot, and improve a network so it functions reliably and meets clearly defined requirements. Evidence should show purposeful development, practical implementation, testing, diagnosis, troubleshooting, and refinement.
AS91895 & AS91897 – Network Development with Process Evidence
AS91895 & AS91897 – Network Development with Process Evidence
When 91897 is used alongside 91895, students are not just building the network. They are also showing the process used to develop it. This includes planning, managing development, collecting evidence across stages, recording changes, testing decisions, and refining the outcome over time. The final work should show both a functional network and a clear development process supported by evidence.
Design a networked system
Design a networked system
Purpose, end user, devices, resources, layout, success criteria.
Before you begin building, you need to design the overall structure of your network. In this phase, you should identify who the network is for, what devices and services are required, how the network will be divided or structured, and how communication will occur between different parts of the network. At Level 3, this should include considering routed connections, the role of key devices, the protocols and services needed, and how the design supports reliability, manageability, and end-user needs.
By the end of the design phase, you should have:
a clear end user or context
the devices and services required
a topology showing the major parts of the network
at least two network segments or subnets if routing is part of the design
the role of key components such as switches, routers, servers, or shared devices
a small set of clear, testable success criteria
notes on relevant implications such as security, reliability, accessibility, sustainability, or future growth
Design Phase: Plan Your Network
Design Phase: Plan Your Network
Who is the network for? What devices need to connect? What resources or services need to be shared? What does the network need to allow users to do? What will count as success?
Key Level 3 concepts
Key Level 3 concepts
Why These Concepts Matter
Why These Concepts Matter
Before building your network, you need to understand a small set of key Level 3 networking concepts because they help explain how the network behaves during configuration, testing, troubleshooting, and refinement. In AS91905, NZQA explicitly identifies the OSI model, ICMP, and transmission modes such as unicast, broadcast, and multicast as networking concepts students are expected to explain, so these should be treated as core learning rather than as an optional side note.
the role of the OSI model in explaining how communication happens
how IP addressing, subnetting, and default gateways affect traffic flow
the difference between communication within a network and communication between networks
how protocols such as ICMP, DHCP, DNS, and SMB support network operation
the difference between unicast, broadcast, and multicast traffic
OSI Model and ICMP
OSI Model and ICMP
The OSI model helps you understand where communication is happening and where problems may be occurring, such as whether an issue is physical, addressing-related, or application-based. ICMP then becomes important during testing and troubleshooting because it helps you check connectivity and see how devices respond across the network, especially when using tools such as ping and traceroute. Together, these concepts give students a practical framework for explaining not just what they configured, but why the network behaves the way it does.
Unicast, Broadcast, and Multicast
Unicast, Broadcast, and Multicast
Transmission modes help students understand how data is sent across a network and why different traffic behaves differently. Unicast explains one-to-one communication, broadcast helps explain traffic sent to all devices on a local network, and multicast introduces more efficient one-to-many communication for specific groups. Making these concepts central helps students connect theory to what they actually observe while configuring devices, testing communication, and refining the network to better meet end-user requirements.
Purpose, Requirements, and Constraints
Purpose, Requirements, and Constraints
The first part of your project is to clearly define the purpose of your network and then turn that purpose into practical requirements and realistic constraints. You should explain who the end user is, what devices need to connect, what resources or services need to be shared, and what the network must allow the user to do. A strong project starts with a clear and specific purpose, such as a teacher workspace with shared printing and storage, a classroom LAN, or a small home office network. This gives the rest of the project direction and helps you decide what hardware, software, and services are actually needed.
At this stage, keep the purpose practical and specific. Rather than saying “my network is for connecting devices,” explain what those devices are and what they need to do. For example, the network might need to provide reliable internet access, shared file access, a printer available from multiple devices, or automatic IP configuration for clients joining the network. These details should then be turned into clear requirements. Requirements are the things your final network must do to be considered successful, and they should be specific enough to test. Statements such as “all client devices can access the shared folder,” “devices receive valid IP settings automatically,” “clients can reach the default gateway,” or “the printer can be reached from all users on the LAN” are much stronger than simply saying “the network works.”
You should also identify the constraints that affect your project. These might include the hardware available, the number of devices involved, whether the network is wired or wireless, the level of security needed, and any reliability or usability expectations. These do not need to be overly complex, but they should be real enough to influence your decisions as you build the network.
By the end of this stage, you should have a short project statement that identifies the end user, the devices involved, the resources or services to be provided, the main purpose of the network, the key requirements the network must meet, and the constraints that shape your design. This gives you a clear foundation for later testing, troubleshooting, and evaluation.
Before you move on...
Before you move on...
You should know what network you are building, who it is for, and what success will look like. You should have a basic plan that shows the main devices, the structure of the network, and the services it needs.
Sprint 1: Build the Core Routed Architecture
Sprint 1: Build the Core Routed Architecture
Use the Basics task to establish the core structure and verify that the foundation of the network works before adding more complex services and routing
In this sprint, you will build the core structure of your network. Your goal is to move from design into implementation by setting up the major devices, applying valid addressing, creating the required network segments, and confirming that the network foundation works as intended. At this stage, focus on establishing a stable core network that can later be extended with services and refinements.
Practical Network Task – LAN Setup and Configuration
Practical Network Task – LAN Setup and Configuration
In this task, you will build, configure, and test the core structure of your network. You will apply valid addressing, confirm physical and logical connectivity, check communication within and between parts of the network where appropriate, and verify that the network foundation is stable enough to build on. The aim is to establish a reliable starting point and collect evidence that shows the core network behaves as intended.
This sprint should be treated as the starting point of the overall network design. The core network built here should have a clear purpose in the wider project and should be structured so it can support later development. Rather than being a separate isolated task, it should act as the foundation the wider network is built on as more complex features, services, and routing are added in later stages. If the design of the basic network needs to be adjusted slightly to better support the future direction of the project, that is acceptable, provided the updated network is shown with a correct network diagram and justified clearly in relation to the overall design.
This first network acts as your starting point. Once it is working, you can improve it further in the next sprint by applying complex techniques.
Click on Image on the Right for the Tutorial
This activity supports Sprint 1 by helping you build and test the first working version of your network.
Before you move on...
Before you move on...
Make sure your core network is built and working at a basic level. The main devices should be connected correctly, addressing should be valid, and you should be able to show that communication is working where expected. You should have evidence of the network layout, configuration, and early testing. By this point, you should be able to explain how the core structure of the network works and identify the role of the main components.
Sprint 2: Add Complex Services and Routing
Sprint 2: Add Complex Services and Routing
Choose and apply suitable services/protocols/features to improve the network.
Once your core network is working, the next step is to improve it by applying complex techniques in a purposeful way. These may include routing between networks, server or service configuration, shared access to files or printers, DNS, DHCP, NTP, firewall or port configuration, or other suitable techniques depending on the project. These techniques should be selected because they improve the capability, usability, or reliability of the network for the end user.
At Level 3, complexity should be visible in the network itself, not just in the write-up.
At Level 3, complexity should be visible in the network itself, not just in the write-up.
The final network should show a more deliberate structure and stronger functionality than a simple flat LAN.
Protocols and Services
Protocols and Services
As you apply complex techniques, you will need to understand the protocols and services that make your network work. Focus on the ones that are relevant to your project. These may include TCP/IP, DHCP, DNS, SMB, NTP, and other suitable services depending on the network you are developing. You should understand what each selected protocol or service does, configure it where appropriate, and show through testing that it supports the intended network outcome.
Breaking down Wifi
VLAN's
VPN's
Wireshark
Basics of Routing
NAT
TCP vs UDP
Port Forwarding
Ports
For many Level 3 projects, the network should move beyond a single flat LAN and include communication between separate network segments or subnets.
Testing and Troubleshooting
Testing and Troubleshooting
Testing and troubleshooting should be an ongoing part of developing the network, not something left until the end. As the network is built and extended, students should check connectivity, configuration, routing, services, and access to shared resources to confirm the network is working as intended. When problems are found, troubleshooting should be used to identify the source of the issue, apply suitable changes, and improve the quality and reliability of the network. This process should help students refine the final outcome and explain why particular changes were needed.
Before you move on...
Before you move on...
Make sure you have added meaningful complexity to the network rather than just extra features. The new services, routing, or protocols should be working as part of the overall network and should improve its capability, usability, or reliability. You should have evidence showing what was added, how it was configured, and how you tested that it worked properly. By this point, you should be able to explain how these additions affect the behaviour of the network and why they were appropriate for the context.
Sprint 3: Test, Diagnose, Explain, Refine, Justify
Sprint 3: Test, Diagnose, Explain, Refine, Justify
Test, diagnose, fix, refine, and judge against the original requirements.
In this sprint, you will test how well the completed network works, identify faults or weak points, and refine the network based on the evidence gathered. You should use testing and diagnostic procedures to check addressing, routing, service operation, access to shared resources, and communication between different parts of the network. At this level, you should use the results of testing to improve the quality of the network, explain why your changes made it better, and justify the selection of important hardware and software components.
What makes this Level 3
What makes this Level 3
At Level 3, a stronger network is not just one that works. It is one that shows a more deliberate structure, uses more complex techniques appropriately, is supported by stronger conceptual explanation, and is refined using testing and troubleshooting evidence.
Final Evaluation
Final Evaluation
At the end of the project, you should evaluate how well the completed network meets the original purpose and end-user requirements. This should include reference to your testing results, any remaining limitations, the improvements made during development, and a clear judgement about whether the final network is fit for purpose.
Before you move on...
Before you move on...
Make sure you have tested the completed network thoroughly and used the results to improve it. You should have clear evidence of the tests you carried out, the faults or weak points you identified, the changes you made, and how those changes improved the final outcome. By this point, you should be able to justify important design choices, explain how the network behaves, and make a clear judgement about how well it meets the original purpose and requirements.
Page updated
Google Sites
Report abuse