Photograph: Shane Rounce on UnsplashLEARN COURSES
Compare the outcomes, teaching sequence and practical projects for each course. Enrolment opens as teaching materials become available.
13 course plans
Inventory database, media, source, configuration and acceptable recovery times. Build a backup schedule with access boundaries and explicit deletion dependencies.
Group a synthetic billing export by account, service, region and resource ownership. Trace disabled services, storage, snapshots and CPU credit or throughput constraints.
Inventory disk, logs, memory, services and access on a disposable Linux host. Use measured CPU, I/O and memory evidence to separate bottlenecks.
Trace vhosts, includes, PHP-FPM pools and CLI versus web PHP versions. Compare nginx and Apache requirements without a universal winner.
Map DNS, TLS, proxy and origin boundaries including mail records. Apply a disposable allowlist setup and preserve an authorised recovery route.
Trace origin, Redis, Varnish and edge responses with measurable hit and miss evidence. Include block assets, headers and variants alongside cached markup.
Inventory source, generated assets, runtime configuration and persistent uploads. Create an isolated release tree and atomic switch with explicit health checks.
Count public and private content, drafts, uploads, dependencies and background jobs. Restore a permitted synthetic copy and compare records, media and redirects.
Describe runtime, database, public media, private files and background work before choosing services. Design site-scoped credentials and isolation without putting shared keys in websites.
Define ownership, URL compatibility and access boundaries for a sample library. Copy objects, compare checksums and plan redirects before switching references.
Separate source age, last successful check, request failure and service state. Capture queue completion, response times and error context without personal records.
Record supported runtimes, installed components and authorised maintainers. Use a public advisory to identify affected versions and preserve relevant logs.
Separate page, object and transient storage and identify tenant boundaries. Set time budgets and test unavailable and slow cache services without holding requests hostage.