Cloudflare Interview Preparation Guide (2027)
A six-week Cloudflare interview study plan with free-plan labs for DNS, SSL/TLS modes, caching, WAF, Workers and Tunnel, plus 20 practice questions.
To prepare for a Cloudflare interview, spend about six weeks on five areas in order: DNS and HTTP basics, SSL/TLS encryption modes, caching, security (WAF and rate limiting), and the developer platform (Workers with Wrangler, plus Zero Trust and Cloudflare Tunnel). A free Cloudflare account and one cheap domain are enough to practise every lab in this plan.
This page is a study plan. It tells you what to build each week, what to check, and how to talk about it in an interview. When you want a full question bank, use our Cloudflare engineer interview questions with answers. For broader DevOps prep, start at the 200 DevOps interview questions hub.
Key takeaways
- Most Cloudflare interview questions are networking questions underneath: DNS, TLS, HTTP status codes and caching headers.
- Know the SSL/TLS encryption modes and why Flexible can cause redirect loops while Full (strict) is the safe target.
- Learn to read the
cf-cache-statusresponse header. HIT, MISS, BYPASS, EXPIRED and DYNAMIC each mean something different. - Build and deploy at least one Worker with
npx wrangler devandnpx wrangler deployso you can talk from experience. - Expose a local service with Cloudflare Tunnel and protect it with an Access policy. That one lab covers most Zero Trust questions.
- Practise explaining one change end to end: what you changed, how you tested it, how you would roll it back.
What Cloudflare-focused interviews usually test
Cloudflare comes up in interviews for DevOps, SRE, platform, security and web operations roles at companies that use it, and at Cloudflare itself. Third-party prep guides for software engineering roles at Cloudflare describe a recruiter screen, coding rounds and a systems or networking round. Cloudflare does not publish a stage-by-stage guide, so treat those reports as indicative only. Read the job description and weight your study to match it.
| Role | Weight most | Weight less |
|---|---|---|
| DevOps / platform engineer | DNS, caching, Workers, Terraform or API automation | Deep WAF tuning |
| SRE | 5xx troubleshooting, origin health, cache behaviour, incident handling | Workers internals |
| Security / DevSecOps | WAF, rate limiting, bot and DDoS concepts, Zero Trust Access | Cache tuning detail |
| Software engineer at Cloudflare | Coding, data structures, networking, distributed system design | Dashboard clicks |
The six-week study plan
Plan on one to two hours on weekdays and a longer lab at the weekend. If you already work with Cloudflare, compress weeks 1 and 2 into a few days and spend the time saved on mock interviews.
| Week | Topic | Hands-on lab (Free plan) | You are ready when you can explain |
|---|---|---|---|
| 1 | DNS and HTTP | Add a domain, change nameservers, compare proxied and DNS-only records | What the orange cloud changes |
| 2 | SSL/TLS | Switch encryption modes against a test origin, install an Origin CA certificate | Why Full (strict) is the target |
| 3 | Caching | Read cf-cache-status, write a cache rule, purge by URL | Why a page is or is not cached |
| 4 | Security | Turn on the Free Managed Ruleset, write a custom WAF rule, read Security Events | How you avoid blocking real users |
| 5 | Workers and automation | Build and deploy a Worker with Wrangler | How you test and roll back edge code |
| 6 | Zero Trust and mocks | Cloudflare Tunnel plus an Access policy; two mock interviews | How you remove a public origin IP |
Week 1: DNS and HTTP
Revise how recursive resolution works, the common record types (A, AAAA, CNAME, MX, TXT) and TTLs. Then add a test domain to a free Cloudflare account and point its nameservers at the two Cloudflare nameservers the dashboard gives you.
Create two records for the same origin: one proxied (orange cloud) and one DNS-only (grey cloud). Query both:
dig +short proxied.example.com
dig +short dnsonly.example.com
curl -sI https://proxied.example.com | grep -i -E "server|cf-ray"
The proxied record returns Cloudflare anycast addresses, and its responses carry a cf-ray header. The DNS-only record returns your origin IP, and Cloudflare never sees the HTTP traffic.
How to talk about it: "Proxied records send traffic through Cloudflare, so caching, WAF and DDoS protection apply and the origin IP stays hidden. DNS-only records are plain DNS. I keep mail hosts DNS-only because they cannot be proxied over HTTP."
Week 2: SSL/TLS encryption modes
Cloudflare's documentation lists these modes: Off, Flexible, Full, Full (strict) and Strict (SSL-Only Origin Pull), plus Automatic SSL/TLS, which picks a mode for you. Learn the one-line meaning of each.
| Mode | Visitor to Cloudflare | Cloudflare to origin |
|---|---|---|
| Off | HTTP | HTTP |
| Flexible | HTTPS | HTTP |
| Full | Matches visitor | Matches visitor; certificate not validated |
| Full (strict) | Matches visitor | HTTPS, certificate validated |
| Strict (SSL-Only Origin Pull) | HTTP or HTTPS | Always HTTPS, certificate validated |
Lab: run a small origin that redirects HTTP to HTTPS and set the zone to Flexible. You get a redirect loop, because Cloudflare keeps fetching over HTTP and the origin keeps redirecting. Fix it by installing a Cloudflare Origin CA certificate on the origin and moving to Full (strict). If you can describe this loop from memory, you can answer a large share of SSL questions.
Week 3: caching
Learn what Cloudflare caches by default (static file extensions, not HTML), how origin Cache-Control headers interact with Cloudflare, and how cache rules change that. Then check responses:
curl -sI https://proxied.example.com/style.css | grep -i cf-cache-status
curl -sI https://proxied.example.com/ | grep -i cf-cache-status
The documented values include HIT, MISS, EXPIRED, STALE, BYPASS, REVALIDATED, UPDATING, DYNAMIC and NONE/UNKNOWN. DYNAMIC on an HTML page usually means the response is not eligible for cache under your current rules.
Lab: write a cache rule that makes a test path eligible for cache, request it twice and watch MISS turn into HIT. Then purge that single URL and watch it return to MISS. Practise saying why "purge everything" is a bad first move on a busy site: every request goes back to the origin at once.
Week 4: security
Turn on the Cloudflare Free Managed Ruleset, which the WAF docs say is available on all plans. Write one custom rule, for example blocking requests to /wp-login.php on a site that does not run WordPress, and try the Managed Challenge action on a test path. Then open Security Events and find your own test request.
Learn the vocabulary even for features you cannot test on the Free plan: managed rules, custom rules, rate limiting rules, Bot Fight Mode, DDoS managed rulesets and API Shield. In interviews the skill that matters is false-positive handling: challenge or log first, check events, then block.
If security is your focus, our 90+ Cloudflare DevOps security questions go much deeper than this plan.
Week 5: Workers and automation
Create a Worker, run it locally and deploy it. These commands come from the Workers getting-started guide:
npm create cloudflare@latest -- my-first-worker
cd my-first-worker
npx wrangler dev # local server on http://localhost:8787
npx wrangler deploy
New projects use a wrangler.jsonc config file; older projects may still use wrangler.toml. Change the Worker to add a response header or redirect one path, deploy again, and write down how you would roll back. Run npx wrangler --help to see the deployment and rollback subcommands in your version instead of memorising them.
Then spend an hour on automation: create a scoped API token in the dashboard and read how the Cloudflare Terraform provider manages DNS records. Interviewers for platform roles often ask how you keep Cloudflare configuration in Git instead of clicking in the dashboard.
Week 6: Zero Trust, Tunnel and mocks
Install cloudflared and publish a local web app without opening any inbound port:
cloudflared tunnel login
cloudflared tunnel create lab-tunnel
cloudflared tunnel route dns lab-tunnel app.example.com
cloudflared tunnel run lab-tunnel
A locally managed tunnel also needs a small config.yml that maps the hostname to your local service; the tunnel guide shows the format. Then, in the Zero Trust dashboard, add an Access application for app.example.com with a policy that allows only your email address, and log in from a private window. You can now explain how Tunnel uses an outbound-only connection, why the origin no longer needs a public IP, and how Access checks identity before any request reaches the app. For background, read why Zero Trust matters in DevSecOps.
Use the rest of the week for two mock interviews. Ask a friend to pick five questions from the list below and one scenario, and answer out loud against a timer.
How to talk about your labs
A home lab counts as experience if you describe it honestly. Use a simple structure: what you set up, what went wrong, how you checked it, and what you would do in production. For example: "On my test zone I set Flexible mode and hit a redirect loop. I confirmed it with curl, installed an Origin CA certificate and moved to Full (strict). In production I would check the origin certificate before changing the mode."
Do not claim production scale you have not run. Interviewers ask follow-ups, and a clear account of a small lab beats a vague account of a big system.
Practice questions to check progress
These 20 questions are a self-check, grouped by level. Answer each aloud before reading the answer. For more, see scenario-based Cloudflare interview questions and, if you are working toward a Cloudflare learning credential, Cloudflare certification questions and prep.
Freshers
1. What does Cloudflare do for a website?
It sits in front of the origin as a reverse proxy. It answers DNS, terminates TLS, caches content at the edge, filters attacks with WAF and DDoS protection, and can run code at the edge with Workers.
2. What is the difference between a proxied and a DNS-only record?
A proxied record returns Cloudflare addresses, so HTTP traffic passes through Cloudflare and its features apply. A DNS-only record returns the origin address, and Cloudflare only answers the DNS query.
3. What is a cache hit?
The edge already holds a valid copy of the object and serves it without contacting the origin. Cloudflare marks this with cf-cache-status: HIT.
4. Why is Flexible SSL risky?
Traffic between Cloudflare and the origin is plain HTTP, so that leg is unencrypted. It can also cause redirect loops when the origin forces HTTPS.
5. What is a WAF?
A web application firewall inspects HTTP requests and blocks or challenges those that match attack patterns, such as SQL injection or known exploit paths.
6. What is the cf-ray header?
An identifier Cloudflare adds to each request it proxies. It confirms the traffic went through Cloudflare and helps you search logs or open a support ticket.
2-5 years experience
7. A page shows cf-cache-status: DYNAMIC. What does that tell you?
Cloudflare did not treat the response as eligible for cache, usually because it is HTML or another type not cached by default and no cache rule makes it eligible. Check your cache rules and the origin's Cache-Control headers.
8. How do you make HTML cacheable safely?
Use a cache rule scoped to public pages only, bypass the cache when a session cookie is present, set a sensible edge TTL, and purge by URL when content is published.
9. Full versus Full (strict)?
Full does not validate the origin certificate, so self-signed or expired certificates are accepted. Full (strict) uses HTTPS and validates the certificate, which protects against someone impersonating the origin.
10. How do you deploy a Worker and test it first?
Run npx wrangler dev to test locally, then npx wrangler deploy. In a team, run deploys from CI with a scoped API token and keep the Worker code and config in Git.
11. How do you roll out a new WAF custom rule without blocking customers?
Start with a non-blocking action such as Managed Challenge (or Log where your plan offers it), watch Security Events for matches, refine the expression, then switch to Block.
12. How would you manage Cloudflare DNS as code?
Use the Cloudflare Terraform provider or the API with a scoped token, store the config in Git, and apply it through a reviewed pipeline so changes are audited and reversible.
Senior
13. How do you stop attackers bypassing Cloudflare to hit the origin directly?
Keep the origin off the public internet. Use Cloudflare Tunnel so the origin only makes outbound connections, or restrict the origin firewall to Cloudflare IP ranges and use authenticated origin pulls. Change the origin IP if it was ever public.
14. How do you design caching for a site with logged-in users?
Separate public and personalised content. Cache public pages and static assets at the edge, bypass on session cookies, and move personalised fragments to API calls. Measure hit ratio and origin load before and after.
15. How would you replace a VPN for internal tools with Cloudflare?
Publish each tool through Cloudflare Tunnel, put an Access application in front with identity-provider login and group-based policies, and move users over app by app while logging access decisions.
16. What do you check before switching a large zone from Full to Full (strict)?
Confirm every origin presents a valid certificate for its hostname, either publicly trusted or a Cloudflare Origin CA certificate. Test a subset of hostnames first, then watch for 526 errors after the change.
Scenario questions
17. After a release, users still see old CSS. What do you do?
Purge the changed asset URLs, then fix the cause: use versioned file names so each release gets new URLs and long TTLs stay safe.
18. Visitors get a redirect loop right after onboarding to Cloudflare. Likely cause?
Flexible mode with an origin that redirects HTTP to HTTPS. Install a valid certificate on the origin and switch to Full (strict).
19. A partner's API calls are suddenly blocked. How do you investigate?
Find the request in Security Events by time, IP or ray ID, see which rule matched, then add a narrow exception for that partner's path or identity instead of disabling the rule.
20. Origin CPU spikes right after someone purged everything. What now?
Every request is a miss, so the origin carries the full load until the cache refills. Scale the origin or add rate limiting in the short term, and change the runbook to purge by URL, tag or prefix.
For error-code questions such as 521, 522, 525 and 526, use the troubleshooting section of our Cloudflare engineer questions.
Common preparation mistakes
- Memorising feature lists without opening a free account. Interviewers notice quickly.
- Skipping DNS and TLS basics to jump straight to Workers.
- Offering "purge everything" as the default fix for stale content.
- Describing WAF rules only as Block, with no plan for false positives.
- Ignoring the job description. A security role and a platform role weight topics very differently.
If you prefer guided labs, our DevSecOps training and DevOps training run in our Kharadi, Pune classroom and live online across India. To place Cloudflare among alternatives, browse 14 Zero Trust security tools for DevOps.
FAQ
How long does it take to prepare for a Cloudflare interview?
About six weeks at one to two hours a day if you are new to Cloudflare. Engineers who already use it can usually compress the first two weeks and focus on labs and mock interviews.
Can I practise Cloudflare for free?
Yes. The Free plan covers DNS, SSL/TLS modes, caching and cache rules, the Free Managed Ruleset, custom WAF rules and Workers. You need a domain you control to add a zone.
Which SSL/TLS mode should I recommend in an interview?
Full (strict), with a valid certificate on the origin such as a Cloudflare Origin CA certificate. Explain why Flexible and Full are weaker.
What Wrangler commands should I know?
npm create cloudflare@latest to scaffold a project, npx wrangler dev to run it locally and npx wrangler deploy to publish it.
Do I need Zero Trust knowledge for a DevOps role?
It helps. Being able to explain Cloudflare Tunnel and an Access policy covers most questions about protecting internal apps without a VPN.
Where can I find more Cloudflare interview questions?
Use our Cloudflare engineer questions for a full bank, the scenario-based set for troubleshooting practice, and the 90+ DevOps security set for WAF and DDoS depth.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0