About this interactive
What you are doing: deciding whether each hardware or operating system trait belongs to a server or to a desktop.
The lesson looks at a server as three layers: the application that delivers the service, the operating system, and the hardware. The application matters most, and you could install a web server such as Apache on any machine. So why separate server hardware and a server operating system? Because they are tuned to deliver services, and to keep delivering them.
Server hardware is often rack-mounted: a thin, long chassis that sits in a rack with many other servers. It duplicates the parts that fail, such as power supplies, fans and drives, and many of them are hot-swappable, so you can pull a failed one while the server keeps running. Its parts are built more robustly to run all the time, it performs at a higher level (RAID controllers striping across many disks, several processors handling many threads, room for huge amounts of memory), and a management interface such as Dell's iDRAC lets an administrator control it over the network, even turning it on when it is off. A server operating system leaves out many of the end-user services a client operating system runs, so it is streamlined for the client-server relationship.
A desktop is built for one person at a desk: parts mixed and matched from many vendors to keep the cost down, room to expand, and an operating system whose services aim to give the user a good experience.
How to use it: ask who the machine is built for, many clients that need the service to stay up, or one person at a desk. A wrong answer resets your streak and shows the right bin; land five in a row to finish.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →