3.4.1. Common Server Roles
💡 First Principle: Server roles exist because different workloads have different resource profiles and security requirements. A database server needs fast storage and abundant RAM; a web server needs fast network throughput and CPU; a domain controller needs high availability and strong security. Collocating incompatible roles degrades both.
Common Server Role Reference
| Role | Primary Function | Key Resource Need | Critical Dependency |
|---|---|---|---|
| File server | Centralized file storage and sharing | Storage capacity, network throughput | Backup, access control |
| Print server | Centralized print queue management | Network, disk (spool) | Driver management |
| Web server | Hosts web applications and content | CPU, network throughput | Application server, database |
| Application server | Hosts business applications | CPU, RAM | Database, network |
| Database server | Stores and queries structured data | Fast storage (IOPS), RAM, CPU | Backup, replication |
| Messaging server | Email (SMTP/IMAP/POP3) | Storage, network | DNS (MX records), spam filtering |
| Domain controller | Authentication, Group Policy (Active Directory) | High availability | DNS (critical dependency), replication partner |
Directory Connectivity
Many server roles require integration with a directory service (typically Active Directory in Windows environments):
- LDAP (Lightweight Directory Access Protocol): The protocol used to query and modify directory services
- Active Directory (AD): Microsoft's directory service; domain controllers host it and provide authentication for the domain
- Domain Controller (DC): A server running Active Directory Domain Services. Should always have at least two DCs per domain for redundancy—a single DC is a critical single point of failure for the entire domain
⚠️ Exam Trap: DNS is a prerequisite for Active Directory, not an optional add-on. If DNS fails in an AD environment, domain authentication fails, Group Policy fails, and DFS (if deployed) fails. Always place DNS on reliable, highly available infrastructure when running Active Directory.
Reflection Question: An organization wants to deploy a new server that will run both SQL Server (database role) and Active Directory Domain Services. What are the risks of running these roles on the same server?
