The pathway follows a strict prerequisite chain: foundational networking (OSI, addressing, VLAN, routing) precedes every service that depends on it. DHCP is taught once subnets and VLANs are already mastered — addresses are distributed within a topology already understood. DNS precedes Active Directory, of which it is a genuine technical prerequisite. GPO is no longer taught in isolation midway through the OS block: it is grouped with Active Directory, immediately after, as the feature it actually is. Each week builds on the previous one's acquired knowledge rather than on an administrative category (OS / Middleware / Network) disconnected from the real technical logic.

At the end of this block, the trainee has installed, configured, secured and defended a complete bare-metal environment including two operating systems, virtualisation, backup and hardening. At this stage, this is already an employable skill for a junior systems technician role — the following two blocks (networking, directory and application services) add the depth needed for full autonomy.

With OSI, addressing, VLANs and routing mastered, the trainee now has the complete topology on which the following three weeks will rely: DHCP distributes addresses within subnets that are now understood, DNS resolves names on infrastructure that is now mapped, and Active Directory will be installed on a network whose segmentation is already mastered.

GPO is deliberately taught only after Active Directory, on which it technically depends, rather than earlier in the OS block. This grouping — Active Directory then GPO, across two consecutive weeks — respects the real dependency: one cannot administer group policies on a directory that does not yet exist.