Operations for Cloudflares
Cloudflare operations covers monitoring and managing an account at scale. Analytics, logs and Workers observability show traffic, errors and performance, while infrastructure as code tools like Terraform and the API define zones, rules and Workers in version control so changes are reviewed and repeatable.
Stage: AI and Operations · Part of the Cloudflare roadmap · Last reviewed 19 November 2026
What to learn in Operations
- Read analytics to find traffic spikes, cache hit ratio and error rates
- Stream Worker logs with wrangler tail while testing a deploy
- Define DNS records and rulesets with the Cloudflare Terraform provider
- Create a scoped API token instead of using the global API key
- Roll back a faulty Worker deployment to a previous version
Operations interview questions
Why use a scoped API token instead of the global API key?
A scoped token grants specific permissions on chosen zones or accounts and can be revoked or expire. The global key has full account access, so a leak is far more damaging. Least privilege applies to automation credentials too.
Why manage Cloudflare settings with Terraform?
Describing rules, DNS and Workers as code gives version history, peer review and repeatable setups across environments. It also detects drift, where settings changed in the dashboard no longer match the declared configuration.
Where Operations fits in the Cloudflare roadmap
Operations belongs to the AI and Operations stage (advanced level). Modern edge.
Other units in this stage
Back to the full Cloudflare roadmap