Web Hosting, Publishing and Security Basics
What the exam tests
Hosting models, domain and DNS setup, publishing workflow, HTTPS, and basic web security controls.
Core rules
- Shared hosting shares server resources; VPS and dedicated servers give more control; cloud hosting scales on demand.
- The registrar manages the domain name; the host stores files. DNS records direct traffic: A (IPv4), AAAA (IPv6), CNAME (alias), MX (mail), TXT (verification/policy).
- Upload via SFTP or SSH, not plain FTP. Keep directory permissions minimal.
- HTTPS uses TLS certificates; Let's Encrypt is a free automated option.
- Validate and sanitise input; use parameterised queries; escape output; hash passwords.
- Back up files and databases; monitor uptime and errors.
Worked example
A site is hosted at 203.0.113.10 and must also answer at www.example.com. Create an A record for @ (example.com) pointing to 203.0.113.10, and a CNAME for www pointing to example.com. Add an MX record for mail. Do not point www to the IP with a CNAME and also an A record - conflicting records cause unpredictable resolution. Reasoning: A maps a name to IPv4; CNAME maps a name to another name.
Traps
Do not say a domain purchase includes hosting. Do not use MX for a website. Do not call HTTP secure. Do not store passwords in plain text. Do not leave directory listing enabled by default.