Deliver a usable support API, keep private responses private and recover a bad release. These projects put the Workers fundamentals into practice through launch, caching diagnosis and release recovery.
The course contains three independent challenges with hints and complete explanatory solutions. Two deploy disposable Workers; the cache-repair challenge runs locally.
What You Will Learn
- Connect a supplied help page to a validated API and internal catalog
- Protect maintenance with a secret and verify the public/internal boundary
- Repair cache eligibility and keys while retaining safe public caching
- Keep errors and private responses uncached
- Restore a known-good version, repair upstream failures and publish a distinct release
- Verify removal of owned resources and local test state
Who This Course Is For
Learners who have completed Workers fundamentals and want independent delivery and operational practice.
Prerequisites: Complete Cloudflare Workers for Beginners, including Wrangler, JavaScript handlers, configuration/secrets, local tests, service bindings, static assets, Cache API policies, rollback and failure diagnosis. Direct-entry learners first complete Connect LabEx to Your Cloudflare Account. Before either deployment challenge, read the Cloudflare learning account preparation guide and confirm your own prepared account.
Learning environment: Every challenge starts in a fresh LabEx VM with dependencies and unrelated fixtures supplied. Deployment exercises use small synthetic datasets and uniquely named Workers; usage counts toward normal account allowances. No shared credentials or purchased domain is required.
Frequently Asked Questions
Does every challenge require cloud deployment?
No. Support Portal Launch and Failed Release Recovery deploy Workers. Cross-Customer Cache Mix-Up runs locally and needs no cloud login; stop its local server and remove its project-local test state during cleanup.
How do the independent challenges work?
Read the scenario, scope and acceptance criteria before editing. Apply the taught concepts, inspect standard output and compare actual response fields. Hints and complete solutions are provided separately.
Can I reuse a previous lab’s deployment?
No. Each challenge creates its own state. Confirm the intended account during authorization and carry forward knowledge rather than resources or credentials.
Do I submit screenshots as proof?
No. Screenshots illustrate useful page and Dashboard states. Verify application behavior and resource state; delete only owned cloud resources while authorized, confirm removal and log out last.
