Week 11 · Lesson 4

Selecting the Right Server

A server is not a single product — it is a set of choices. The same budget can buy a machine that flies or one that chokes, depending on whether the CPU, memory, storage, RAID, and network match the workload. This lesson turns “get a server” into a specification you can defend.

CCNA 200-301 Infrastructure Verified 2026-10-11
Part 1

Start with the workload

Every server decision flows from what the machine will actually do. Before you look at a part list, collect four inputs:

Users and devices

How many clients depend on this server, and what each one asks of it. A file open and a database query are worlds apart.

Peak concurrent connections

Not the average. A server that is idle at 10 a.m. and saturated at 9 a.m. must be sized for 9 a.m.

Storage needs

Usable capacity today, plus how fast data must be read and written — input/output operations per second, or IOPS.

Growth

The expected yearly increase. A good rule for infrastructure is 3–5 years of headroom, because servers are usually refreshed on that cycle.

Definition — right-sizing. Right-sizing means matching each subsystem to the measured or expected workload, with a deliberate margin for peak load and growth — not buying the biggest of everything, and not buying the cheapest that fits today.

The classic mistake is over-buying CPU while under-buying storage or memory. Most real servers stall on I/O or run out of RAM long before the processor is the bottleneck.

Workload to specification · choose the job

Part 2

CPU: cores versus clock speed

A processor has cores (independent execution units) and a clock speed in gigahertz (GHz). More cores let the CPU run many tasks at once; a higher clock lets each task run faster. A server may hold one or two sockets, each holding one CPU package, and most modern cores support simultaneous multithreading (Intel Hyper-Threading), presenting two logical processors per core.

WorkloadWhat it stressesCPU profile
Web / file serverMany small, mostly independent requestsMore cores, moderate clock
DatabaseFew complex queries, heavy on cache and single-thread speedFewer, faster cores + large cache
Virtualization hostRuns many virtual machines at onceVery high core count + lots of RAM
Batch / analyticsLong CPU-bound jobs that parallelise wellMaximum cores
CPU profile · select the workload

Exam tip. Core count and clock speed are a trade-off, not a ranking. A database server often performs better on a high-clock, moderate-core CPU than on a many-core chip with a low clock. Virtualization is the opposite: it wants maximum cores and memory because every VM competes for them. If a question mentions “many virtual machines,” think cores and RAM, not GHz.

Also watch core-based software licensing. Database and virtualization platforms are often licensed per physical core, so adding cores can raise the software bill as fast as the hardware one. That is a justification input, not a specification detail, but it changes the answer more often than students expect.

Part 3

Memory: capacity and ECC

RAM holds the working data and the operating system. On a server, memory is rarely just “how many gigabytes” — it is also what kind.

Remember. You cannot mix UDIMM and RDIMM, and most server boards demand ECC. Confirm the motherboard and CPU memory-controller support the exact DIMM type, rank, and speed before ordering.
Part 4

Storage: HDD, SSD and NVMe

Storage is where most servers feel slow or fast, so learn the three canonical media and what each is for:

Storage media · compare the three options

Three metrics, not one. Storage performance is IOPS (operations per second), throughput (megabytes per second), and latency (delay per operation). A database is usually IOPS- and latency-bound; a video archive is throughput-bound. Match the media to the metric that actually limits the workload.

RAID by workload

RAID (Redundant Array of Independent Disks) combines several physical disks into one logical volume for speed, protection, or both. Learn the four levels by their purpose:

RAID levelTechniqueGives youCost
RAID 0Striping across disksSpeed; no redundancy — one disk loss loses all data100% capacity
RAID 1Mirroring (identical copies)Safety: survives one disk failure50% capacity
RAID 5Striping + distributed parity (min 3 disks)Safety + capacity: survives one disk failureOne disk’s worth lost
RAID 10Mirror + stripe (min 4 disks)Speed + safety: survives a failed disk per mirror50% capacity

Guidance by workload: RAID 0 only for scratch or caches that can be rebuilt; RAID 1 for operating systems and small critical volumes; RAID 5 for general file and application data where capacity plus single-disk protection matters; RAID 10 for databases and virtual machines where both speed and safety are required.

RAID is not backup. RAID protects against a disk failing, not against deletion, ransomware, fire, or a controller fault. A backup is a separate copy on separate media, ideally off-site. Never treat RAID as a substitute for one.
Part 5

Networking and form factor

How the server joins the network is part of the specification.

Exam tip. Memory hook: iLO = HPE, iDRAC = Dell, IPMI = the vendor-neutral standard. Out-of-band management is “out-of-band” because it does not use the normal data network path — it is reachable when everything else is broken.

Form factor: rack versus tower

The physical shape follows the room it will live in:

Don’t forget the room. Rack servers assume cool air at the front and exhaust at the rear. Choosing a rack server for a hot, dusty back office without proper airflow causes thermal throttling and early failures — a sizing mistake that no part list will show.
Part 6

Worked example: a 200-user file server

The situation. A 200-employee office needs a central file server. Users store office documents, spreadsheets, and images. Peak load is around 80 concurrent users at 9 a.m. Usable data is about 20 TB and grows roughly 15% a year. The server will live in a small rack in the server room.

Walk the four subsystems:

  1. CPU. File serving is I/O-bound, not CPU-bound. A single mid-range processor with around 16 cores is ample and leaves room to add a virtual machine later. No need for a top-tier database chip.
  2. Memory. Fit 64 GB ECC. The file service benefits from a large read cache, and 64 GB comfortably covers the OS, the caching, and one or two future VMs without paging.
  3. Storage. Put the OS on a RAID 1 pair of SSDs so the system volume is fast and survives a disk failure. Put the bulk data on a RAID 5 array of high-capacity HDDs sized for roughly 20 TB usable plus the parity disk and growth — for example, four 8 TB drives give about 24 TB usable. Add an SSD read cache (or a small NVMe tier) so frequently opened files feel snappy despite the spinning bulk tier. If budgets were tighter on performance instead of capacity, RAID 10 on SSDs would be the alternative.
  4. Networking. Two 10 GbE ports, teamed, so throughput scales and a single link failure does not take the server offline. Enable iDRAC or iLO out-of-band management for headless administration.

Form factor: a 2U rack server, which holds the drive bays and offers better cooling than a cramped 1U chassis. The result is a spec that is defensible because every choice maps to a stated requirement — not to a brand or a budget number.

RAID capacity calculator · check the arithmetic

Selection table

Use this as a starting point, then adjust with the four inputs from Part 1:

WorkloadCPURAMStorageRAID
Web / app serverMany cores, moderate clock32–64 GB ECCSSD (OS + app)1 (OS), 5 or 10 (data)
Database serverFew fast cores, big cacheLarge, ECCNVMe + fast SSD10
File serverModerate cores64 GB ECCSSD OS + HDD bulk + cache1 (OS), 5 (data)
Virtualization hostMax coresVery large, ECCSSD/NVMe shared store10
Backup / archiveLow16–32 GB ECCHigh-capacity HDD5 or 6

Scenario drills

A start-up runs a public website on one server and expects traffic to triple. Which subsystem should they upgrade first, and why?
Scale the application and database tiers with CPU/RAM and move data storage to fast SSDs or NVMe, then ensure the NIC is at least 10 GbE. Web capacity is usually limited by the application/database and I/O, not by raw disk capacity.
A client wants the cheapest possible storage for a backup archive that is written once and rarely read. What do you recommend?
High-capacity HDDs in a redundant array such as RAID 5 or RAID 6. Sequential throughput and low cost matter; latency does not, so flash would be wasted money.
A database server must survive a disk failure and still deliver high IOPS. Which RAID level and media fit best?
RAID 10 on SSDs or NVMe. RAID 10 gives both mirroring (safety) and striping (speed); flash supplies the IOPS a database demands.
Why do servers use ECC memory when desktops often do not?
Servers hold critical, long-lived data. ECC detects and corrects single-bit memory errors, preventing silent corruption or crashes that would be unacceptable in production.
A rack server will run headless in a data centre. What feature lets you access it when the OS is unreachable?
Out-of-band management — iDRAC (Dell), iLO (HPE), or the standard IPMI — providing a remote console and power control.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco Networking Academy. CCNA: Introduction to Networks (ITN), module resources on network devices and infrastructure. netacad.com.
  2. Cisco. CCNA (200-301) Exam Topics — Network Fundamentals and IP Services. cisco.com.
  3. Microsoft Learn. Windows Server storage and hardware guidance (storage spaces, RAID alternatives, and memory requirements). learn.microsoft.com.
  4. Dell Technologies. iDRAC documentation. dell.com.
  5. HPE. iLO documentation. hpe.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.