Week 11 · Lesson 6

Justifying and Planning Server Selection

A good engineering choice is only half the job. Someone has to approve it, fund it, and live with it for years. This lesson turns a server decision into a case you can defend — with requirements, capacity numbers, cost, lifecycle, and documentation — and then closes the whole course.

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

Needs assessment

Before any specification, write down what the business actually needs. A needs assessment is a structured conversation that produces requirements you can test against. Capture three groups:

Definition — requirement vs wish. A requirement is a measurable need the solution must meet (“host a 10 TB file share for 150 users”). A wish is a preference without a number (“make it fast”). A defensible case is built on requirements; wishes get folded in only where they are cheap.
Requirement or wish? · pick a statement

The reason the distinction matters is accountability. A requirement can be tested — somebody can measure the delivered system against it and say yes or no. A wish cannot be, so it turns into an argument in the budget meeting. When you write a wish down, the useful next step is to convert it into a number: “make it fast” becomes “file opens must return under 200 ms at peak load.”

Part 2

Capacity planning

Capacity planning is the exercise of turning requirements into sized resources. Two ideas do most of the work:

100% 50% 0 Average typical day Peak busiest hour Sized capacity what you buy Target ceiling (50–70%) Peak must sit below it, never at full capacity. Full capacity is a trap: no room for the loss of a node or a demand spike.
Average load hides the problem; peak load reveals it. Plan the peak to sit under a deliberate ceiling so unexpected demand or a failed component does not cause an outage.
Capacity planner · size the platform
target

Watch the compound effect. Growth is not a one-off: a platform sized for today’s peak will be over-subscribed before the refresh date unless the projection is folded into the purchase. That is exactly why the planning horizon in most organisations is the 3–5 year lifecycle of the hardware.
Part 3

Performance metrics

Capacity planning is not a one-off. To know whether a server is still right-sized, watch the same metrics in production:

MetricWhat it tells youWarning sign
CPU utilisationCompute pressure; sustained highs mean the workload outgrew the CPUSustained > 80% at peak
Memory utilisationWhether the working set fits in RAMHigh use plus disk paging
Storage I/O (IOPS, queue depth)Whether storage can keep up with reads/writesGrowing queues and rising latency
LatencyResponse time users actually feelSteadily climbing under the same load
Network utilisationWhether the NIC or uplink is saturatedLinks pinned near 100% at peak
Find the bottleneck · select the symptom

Find the bottleneck, then fix it. A server is only as fast as its slowest subsystem. If CPU is at 30% while storage queues explode, buying a bigger CPU changes nothing. Measure first, then spend where the metric points.
Part 4

TCO and ROI

Hardware is not the whole cost. Total Cost of Ownership (TCO) sums everything it takes to own and run the solution over its life:

Return on Investment (ROI) asks a different question: does the money spent deliver a benefit worth more than the cost? ROI can be hard savings (fewer servers after consolidation, less power) or value such as reduced downtime, faster delivery, or a capability the business did not have. A sound case states both, honestly labelled.

TCO builder · fill in the cost lines

Exam tip. TCO is the total cost of owning; ROI is the benefit relative to that cost. Cloud is often cheaper on CAPEX but can be more expensive on OPEX if usage grows unmanaged — the reason a comparison needs the whole life of the solution on both sides, not the sticker price.
Part 5

Lifecycle, refresh, documentation and change management

Servers are not permanent. A typical lifecycle is three to five years: the period the vendor supports the hardware with firmware updates and spare parts under warranty. Plan the refresh before it arrives, not after:

A server decision that is not documented cannot be defended, audited, or repeated. Two practices protect the investment:

Security link. Documentation and change control are security controls too. Unpatched, undocumented, or unapproved changes are exactly what attackers and auditors find. This connects directly back to Week 10.
Part 6

The consolidation decision tree

Three questions, asked in order, resolve most server decisions:

1. Virtualize or physical? Virtualize — most workloads Physical — appliances, latency, licences 2. On-premises or cloud? On-prem — control, low latency Cloud / hybrid — elasticity, OPEX 3. Build or buy? Build — full control, more staff Buy / SaaS — speed, less to run Ask in order: how the workload should run, where it should run, and who should supply it. Each answer narrows the field before you spend any money.
Ask in order: how the workload should run, where it should run, and who should supply it. Each answer narrows the field before you spend any money.

Used in order, the tree keeps you from jumping to the answer you like. Most workloads virtualize first, because one physical host running several virtual servers lowers the hardware count and makes snapshots and recovery easy. Only appliances, hard real-time latency, or licences tied to physical hardware justify staying physical. The second question separates the deployment models from Lesson 5, and the third separates building a platform from buying one.

Part 7

Worked mini-case: 150 employees

The situation. A 150-employee company has outgrown shared folders and a consumer mail service. It needs a proper email platform and a central file platform. About 60 staff use email heavily; the file share will hold roughly 10 TB of documents and grow about 10% a year. Leadership wants a recommendation it can approve this quarter.

  1. Step 1 — needs assessment. Users: 150, with 60 heavy email users. Apps: email plus file sharing, plus room to grow. Constraints: sensitive internal documents, a modest IT team (one or two people), and a preference for predictable cost.
  2. Step 2 — capacity. Email for 150 users is a well-understood, largely outbound workload; the file share needs ~10 TB now and about 15 TB of headroom by year five. Peak concurrency is modest, so neither service is compute-heavy.
  3. Step 3 — apply the decision tree.

Step 4 — TCO. Email as SaaS turns a hardware-plus-license-plus-staffing project into a known recurring subscription. The file platform carries CAPEX for storage, plus power, cooling, and backup — but stays a modest, local cost. Both sides are compared over five years, not on purchase price alone.

Step 5 — lifecycle and documentation. Put both services on a five-year review. Document the file server’s spec, addresses, backup schedule, and the change process; document the SaaS tenancy, admin accounts, and data-location and contract terms. Revisit at refresh.

Recommendation. Email to a hosted SaaS platform; file platform as a virtualized on-prem (or hybrid) file server sized for 15 TB with RAID 5 or RAID 10 and a tested backup. The recommendation is defensible because every choice traces to a stated requirement and a TCO line, not to a vendor preference.
Why this earns approval. The case names the requirements, sizes the platform, compares whole-life costs, respects the small team, and plans the refresh. That is the difference between “we want a server” and a budget request a manager can sign.

Capstone recap

Week 11 completes the infrastructure picture. Tick each capability:

Define a serverits roles and its place in a network
Describe the softwareOS, services, and applications
Compare server OSsWindows Server vs Linux
Select hardwareCPU, memory, storage, RAID, network, form factor
On-prem vs cloudIaaS / PaaS / SaaS, public / private / hybrid
Justify the choicerequirements, capacity, TCO, lifecycle, documentation

You’ve completed the course

You started at Week 1 not knowing a PDU from a port. You have since learned how devices are addressed, how the layers fit together, how data is encapsulated, how IP and subnetting work, how the transport and application layers behave, and how to secure a network — and now, how servers are chosen, hosted, and justified. That is the full arc of CCNA 200-301, with the security fundamentals of CyberOps 200-201 woven through.

Two habits carry the knowledge forward: read the sources at the end of every lesson rather than trusting a summary, and practise in a lab or Packet Tracer until the commands and the reasoning are automatic. Theory that is never run is half-learned.

From here, keep a copy of the roadmap as your index, retake the quiz until the foundations are solid, and treat Week 11 as the template for every infrastructure decision you will make next. Congratulations — the course is complete, and you are exam-ready to keep building on it.

Part 8 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Mell, P. & Grance, T. NIST SP 800-145: The NIST Definition of Cloud Computing (2011). csrc.nist.gov.
  2. Microsoft Learn. Cloud economics and Total Cost of Ownership. learn.microsoft.com.
  3. Amazon Web Services. Total Cost of Ownership guidance. aws.amazon.com.
  4. Cisco Networking Academy. CCNA: Introduction to Networks (ITN), module resources on change management and infrastructure planning. netacad.com.
  5. Cisco. CCNA (200-301) Exam Topics. cisco.com.

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