45+ Akamai CDN Interview Questions on Caching (2027)

46 Akamai CDN interview questions on caching options, cache keys, TTLs, purge, tiered distribution, edge hostnames and Pragma debug headers, with scenarios.

Sep 30, 2025 - 16:36
Nov 5, 2026 - 05:03
 0  78
45+ Akamai CDN Interview Questions on Caching (2027)

Akamai CDN interview questions test how content actually moves through the edge: which caching option a rule sets, what goes into the cache key, how TTLs flow to browsers, how purge differs from expiry, how tiered distribution cuts origin load, and how you prove all of it with Pragma debug headers and a staging test before activation.

This guide is the delivery-mechanics companion to our main 80+ Akamai interview questions post. That post covers the whole product line, including security. Here we stay inside one property and go deep on caching, cache keys, purge, origin settings, onboarding and debugging, with option names checked against Akamai TechDocs.

Key takeaways

  • By default Akamai caches GET responses and does not honor origin Cache-Control or Expires unless the Caching behavior tells it to.
  • The hostname and path are always in the cache key. Query strings, headers, cookies and variables are added or removed with Cache Key Query Parameters and Cache ID Modification.
  • Edge TTL and browser TTL are separate. Downstream Cacheability decides what the client receives.
  • Invalidate is the default purge method and revalidates with the origin. Delete forces a full fetch.
  • Tiered Distribution only helps cacheable content. SureRoute is the tool for non-cacheable traffic.
  • X-Cache, X-Cache-Key, X-Check-Cacheable and X-Akamai-Staging answer most "is it cached, and where am I?" questions.

Where each mechanic lives in Property Manager

Question you are askedBehavior or toolWhat to say first
How long does the edge keep it?CachingCache with a max-age, honor origin headers, no store, or bypass cache
How long does the browser keep it?Downstream CacheabilityDefault sends the smaller of origin header or remaining edge TTL
Which requests share an object?Cache Key Query Parameters, Cache ID Modification, Origin Server (Cache Key Hostname)Host and path always count; the rest is configurable
What about 404s and 5xx?Cache HTTP Error ResponsesSome errors cache for 10 seconds by default; 5xx keep stale objects
How do we clear it?Fast Purge (URL, CP code, cache tag), Enhanced purge (ECCU)Invalidate by default, delete for compliance removals
How do we protect the origin?Tiered DistributionParent tier collapses edge misses
How is dynamic traffic sped up?SureRouteRaces routes to the origin for non-cacheable content
How do we prove it works?Pragma headers or Enhanced Debug, staging networkCheck X-Cache and X-Akamai-Staging

Freshers: caching and delivery basics (Q1 to Q12)

1. What does Akamai cache by default?

Only responses to GET requests are cacheable by default. TechDocs also notes that Property Manager assigns a cache setting automatically, origin Cache-Control and Expires are not honored unless you configure it, permanent redirects (301, 308) are cached, and temporary redirects (302, 307) are not cached except on Adaptive Media Delivery, Download Delivery or Object Delivery, or when you add the Cache HTTP Temporary Redirects behavior. Redirects that Akamai itself generates are never cached.

2. What options does the Caching behavior offer?

Six: Cache (use the Maxage you set), No store, Bypass cache, Honor origin Cache-Control and Expires, Honor origin Cache-Control, and Honor origin Expires. The honor options let you pick which directives count, such as no-store, private, no-cache, max-age, s-maxage, must-revalidate and proxy-revalidate, plus a Default maxage used when the origin header is missing or invalid.

3. What is the difference between No store and Bypass cache?

No store serves from origin and clears the cached copy at the edge. Bypass cache serves from origin without clearing what is cached, and it also disables downstream caching. Interviewers like this one because the names sound alike but the side effects differ.

4. What is a TTL in Akamai terms?

The time an edge server treats an object as fresh. After it expires, the edge revalidates with the origin instead of serving the copy blindly. TechDocs also describes a zero TTL option where objects are stored but revalidated on every request, which is useful for content that must be current but is expensive to transfer.

5. What is cache prefresh?

Prefresh lets the edge revalidate a popular object asynchronously before its TTL expires, so users keep getting hits. The default prefresh point is 90% of the TTL.

6. What is a cache key?

The identity the edge uses to decide whether two requests can share one stored object. On Akamai the hostname and path are always included and cannot be removed. Query strings, selected headers, cookies and user-defined variables can be added or dropped.

7. What does Cache Key Hostname control?

It is a field in the Origin Server behavior. With Origin Hostname, requests with the same origin hostname, path and query string share one object, even across different property hostnames. With Incoming Host Header (Virtual Server Option), each digital property gets its own cache entry, which you need when one origin serves different sites by Host header.

8. What is an edge hostname, and what suffixes do you see?

The Akamai hostname your own domain points to with a CNAME. The suffix follows the certificate type: edgesuite.net for Standard TLS, edgekey.net for Enhanced TLS (which also needs a certificate enrollment), and akamaized.net for the shared certificate.

9. How does a site start receiving traffic through Akamai?

You create a property, add the hostname, map it to an edge hostname, activate on staging, test, activate on production, and then change the DNS record for www.example.com to a CNAME pointing at the edge hostname. Until that DNS change, real users still go straight to the origin. Lower the DNS TTL a day before so the cutover and any rollback propagate quickly.

10. What does the X-Cache header tell you?

How the edge served the request. Common values: TCP_HIT (fresh, from disk), TCP_MEM_HIT (from memory), TCP_MISS (fetched from origin), TCP_REFRESH_HIT (stale copy revalidated and still valid), TCP_REFRESH_MISS (revalidated and the origin sent a new object), TCP_REFRESH_FAIL_HIT (stale served because the origin could not be reached), TCP_IMS_HIT and TCP_NEGATIVE_HIT (a cached error such as Not Found).

11. How do you request debug headers?

Send a Pragma request header with the values you want. Akamai also offers Enhanced Debug as the newer equivalent with short option names such as cache.

curl -sI https://www.example.com/css/site.css \
  -H "Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-true-cache-key, akamai-x-get-request-id"

12. Why should purge not replace TTLs?

Akamai's own purge documentation says purge mechanisms should not stand in for TTL settings. A purge is for unplanned changes. If you purge on every deploy because TTLs are wrong, you send avoidable load to the origin and depend on a manual step.

2 to 5 years: rules, keys and purge (Q13 to Q28)

13. How do you decide between a fixed max-age and honoring origin headers?

Use a fixed max-age when the CDN team owns freshness, for example versioned static assets that can sit for a long time. Honor origin headers when the application team knows best per response, such as an API that sets s-maxage. Many properties mix both: a fixed long TTL on /static/* and Honor origin Cache-Control on /api/*, with a sensible Default maxage as a fallback.

14. What does Downstream Cacheability do, and what is its default?

It controls what Akamai tells browsers and other downstream caches. Caching options are Allow caching; Allow caching, require validation (no-cache); Don't allow caching (bust); Pass cacheability headers from origin; and Don't send cacheability headers. Lifetime defaults to "Smaller value: origin header or remaining edge TTL". Other choices include Greater value, Remaining edge TTL, Full edge TTL (max-age), Fixed value, and Calculate Expires from origin Cache-Control.

15. Why would you give the edge a long TTL and the browser a short one?

Because you can purge the edge, but you cannot purge a user's browser. An HTML page might sit at the edge for an hour and be purged on publish, while browsers get a short or no-cache lifetime so they come back and pick up the purge.

16. Which Cache Key Query Parameters options exist?

Include all parameters (preserve order from request), include all parameters reordered alphabetically, Include only specified parameters, and Exclude only specified parameters. The last two have an Exact Match setting for how names are compared. Reordering alphabetically stops ?a=1&b=2 and ?b=2&a=1 from becoming two objects.

17. Marketing adds utm_* parameters to every link and the hit ratio drops. What do you change?

Exclude the tracking parameters from the cache key, or include only the parameters that change the response. The origin still receives the full URL if it needs it for analytics; only the key changes. Confirm with akamai-x-get-cache-key that two URLs differing only by utm_source now return the same key.

18. What can Cache ID Modification add to the key?

Its actions are Include the following headers, Include the following cookies, Include all query parameters, Include the following query parameters, Exclude the following query parameters, Include a user-defined variable, and Include the URL. Include Values decides whether the name alone or name and value count. Require Included Elements set to required means a request without that element is not cached.

19. What are the traps with Cache ID Modification?

From TechDocs: it overrides cache-key settings from parent and earlier sibling rules; only headers sent by the client can be used, so a header set by Modify Incoming Request Header or an EdgeWorker cannot define the key; variables must be set before the request goes forward, not from origin response headers; and you need one instance per element type if you want both headers and cookies.

20. How would you cache a page that differs by language?

Add the language signal to the cache key, ideally a single normalized value. Putting the raw Accept-Language header in the key creates many variants because browsers send long, ordered lists. A cleaner approach is a language cookie or path prefix (/en/, /de/) and a key that includes only that.

21. Why can an origin Vary header hurt caching?

Akamai TechDocs notes that origin Vary headers can stop edge servers caching content, which is why a Remove Vary Header behavior exists. Remove it only when you have handled the variation another way, such as putting the relevant value into the cache key, or you risk serving the wrong variant.

22. How are error responses cached?

Cache HTTP Error Responses covers 204, 305, 404, 405, 414, 500, 501, 502, 503 and 504. By default 204, 305, 404, 405, 414 and 501 are cached for 10 seconds, while 500, 502, 503 and 504 are not cached unless you enable the behavior. Its Preserve Stale Objects option, on by default, keeps serving a stale copy when the origin returns those 5xx codes.

23. What is the difference between invalidate and delete?

Invalidate, the default, marks objects invalid; the next request sends an If-Modified-Since conditional request and the origin returns a full copy only if the content changed. Delete removes the object, so the next request always fetches the full object, which costs more origin bandwidth. Akamai recommends delete for compliance or copyright removals.

24. What can you purge by?

Fast Purge works by URL, ARL, CP code, or cache tag. Enhanced purge, through ECCU requests, handles directory and file extension matches across a digital property and is slower, suited to broad, planned refreshes.

25. How do cache tags work?

The origin labels responses with tags, for example every page that shows product 1234 gets a product-1234 tag, and you purge the tag when that product changes. Limits from TechDocs: each tag up to 128 characters, up to 128 tags per object, tags are case-sensitive, and spaces, commas, colons and quotes are not allowed. akamai-x-get-cache-tags returns an Edge-Cache-Tag header so you can check what an object carries.

26. How do you purge from a pipeline?

Call the Fast Purge API with EdgeGrid credentials, or use the Akamai CLI purge package, whose documented pattern is akamai purge [global flags] command [--cpcode --tag] [URLs/CPCodes/Cache Tags...] with invalidate and delete as commands. Purge only the URLs or tags the release touched.

akamai purge invalidate https://www.example.com/index.html https://www.example.com/pricing
akamai purge invalidate --tag product-1234

27. What is a CP code, and why does it matter for delivery?

A content provider code is the reporting and billing identifier attached to traffic by the Content Provider Code behavior. Splitting CP codes by content type (images, HTML, API) lets you see hit ratio and offload per type, and lets you purge a whole class of content by CP code when needed.

28. How is the rule tree evaluated?

Every rule whose match criteria apply contributes its behaviors, top to bottom, and a later matching rule overrides an earlier one for the same behavior. That is why a broad "cache everything for 1 day" rule placed below an "/api/* no store" rule will quietly cache your API. Put general rules first and exceptions after them.

Senior: origin offload and performance (Q29 to Q38)

29. How does Tiered Distribution reduce origin load?

Edge servers that miss ask a parent tier of Akamai servers before going to origin, so many edge misses collapse into a few origin requests. A Global map spreads parents worldwide for lower latency but fewer hits per parent. A Local map picks a region near your origin, such as Europe or United States West Coast, which concentrates requests and raises the parent hit ratio.

30. What are the limits of Tiered Distribution?

Only cacheable content uses it. On Enhanced TLS properties you can only turn it on or off, while Standard TLS lets you choose a map. It is enabled automatically in the default rule for Adaptive Media Delivery, Download Delivery and Object Delivery using the Origin Characteristics location. API Acceleration is not compatible with Tiered Distribution maps.

31. How do you read X-Cache-Remote?

Request akamai-x-cache-remote-on. It shows how the parent served the edge. X-Cache: TCP_MISS with X-Cache-Remote: TCP_HIT means the edge missed but the parent tier had it, so the origin was not touched. Two misses mean a true origin fetch.

32. How do you speed up content you cannot cache?

SureRoute. After a user request for non-cacheable content, it sends a test object request over three routes at once and uses the fastest as the primary route, caching the result for 30 minutes by default. The test object must live on the same origin hostname, return 200 without authentication, be a static file of roughly 8 KB to 56 KB, and not hit a database.

33. What does Forward Host Header do and when does it break things?

It sets the Host header sent to the origin: Incoming Host Header (default), Origin Hostname, or Custom Value. If the origin is a load balancer or bucket that only answers to its own name, sending the incoming host produces 404s or the wrong site. With origin TLS, SNI uses the Forward Host Header value, so it also affects certificate matching.

34. How do you check origin certificates are verified?

The Origin Server behavior's Origin TLS Certificate Verification has Platform Settings, Choose Your Own and Third Party Settings. Under Choose Your Own you can trust the Akamai-managed CA set, a custom CA set or a pinned certificate, and set Match CN/SAN To, which defaults to the origin hostname and forward host header. A mismatch here is a common cause of 502s after an origin move.

35. Which performance behaviors would you mention for front-end delivery?

HTTP/2 support, Brotli support, Last Mile Acceleration (gzip compression), and Prefetch Objects. Name only what you have used or can explain, and tie each to a metric: compression to bytes transferred, HTTP/2 to connection reuse, prefetching to fewer round trips for embedded objects.

36. How do you measure origin offload properly?

Compare edge hits to origin requests, or bytes served to bytes fetched from origin, per CP code. A site-wide hit ratio hides problems: images at 98% can mask HTML at 20%. Watch the trend after each release, since a new query parameter or cookie in the key shows up as a sudden drop.

37. How do you design caching for an e-commerce catalog?

Versioned static assets: long fixed TTL and long browser lifetime. Category and product pages: moderate edge TTL, cache tags per product, purge tags from the product service on change, and a short downstream lifetime. Cart, checkout and account: no store or bypass, keyed off path. Keep stock and price fragments out of cached HTML, or fetch them client-side from an uncached API.

38. How do you protect against a cache stampede when a hot object expires?

Prefresh the object before expiry so the edge revalidates in the background, keep Tiered Distribution on so parent servers absorb the burst, use invalidate rather than delete so most refreshes are cheap 304s, and keep Preserve Stale Objects so a struggling origin does not turn into user-facing 5xx errors.

Scenario questions (Q39 to Q46)

39. X-Check-Cacheable says YES but X-Cache shows TCP_MISS on every request. Why?

Cacheable only means the configuration allows caching. Persistent misses usually mean the key differs each time (a cache-busting query parameter, a cookie or header in the key), you are hitting different edge servers (check X-Serial), or the TTL is zero. Compare X-True-Cache-Key across two requests.

40. After a deploy, some users get old JavaScript and others new. What happened?

The file name stayed the same, so browsers still hold the old copy for its downstream lifetime, and edge servers that were not purged still serve it. Fix the process with content-hashed file names and a long TTL; for the current incident, purge the URL and shorten the browser lifetime on HTML that references assets.

41. You set Honor origin Cache-Control, and now nothing caches. Why?

The origin is probably sending private, no-store or no-cache, or no Cache-Control at all with no Default maxage. Check the raw origin response with curl directly against the origin, then either fix the application headers or switch the rule to a fixed max-age for that path.

42. A 404 page is being served for a file that now exists. Why?

A negative cache entry. The edge cached the 404 (TCP_NEGATIVE_HIT), by default for 10 seconds, or longer if Cache HTTP Error Responses sets a larger Max-age. Purge the URL and review whether a long negative TTL makes sense for paths where files appear after publishing.

43. A purge completed but users still see the old page. What do you check?

Whether you purged the exact cache key (scheme, host and query string matter; check X-Cache-Key), whether the old copy is in browsers because Downstream Cacheability allowed it, whether another layer such as an application cache at origin served stale content back on revalidation, and whether you purged the production network rather than staging.

44. A staging test looks perfect but you are not sure it hit staging. How do you confirm?

Take the edge hostname, insert -staging before the final .net (for example www.example.com.edgekey-staging.net), resolve it, put that IP in your hosts file for www.example.com, flush DNS, and request with debug headers. A staging server returns X-Akamai-Staging: ESSL for Enhanced TLS or EdgeSuite for Standard TLS. No X-Cache at all means you reached the origin.

dig +short www.example.com.edgekey-staging.net
# add "203.0.113.10 www.example.com" to /etc/hosts, then:
curl -sI https://www.example.com/ -H "Pragma: akamai-x-cache-on" | grep -i -E "x-akamai-staging|x-cache"

45. Origin traffic doubled after adding a second hostname to the property. Why?

Cache Key Hostname is likely set to Incoming Host Header, so www.example.com and shop.example.com keep separate copies of identical assets. If both hostnames serve the same content from the same origin, Origin Hostname lets them share objects. If they serve different content, the doubling is expected and Tiered Distribution is the lever.

46. Logged-in users see each other's account pages. What do you do first?

Stop caching the affected path immediately with a no store rule and activate it, purge the path with delete, then find the cause: usually a broad cache rule covering /account/*, or an origin that sent cacheable headers on personalised responses while the property honored them. Add a rule that bypasses cache when a session cookie is present, and test it on staging with two different sessions.

How to prepare in a week

Read the Caching, Cache ID Modification and Downstream Cacheability pages on TechDocs, then practise reading debug headers against any public site behind Akamai. Our Akamai interview preparation study plan sets out a longer schedule. For incident-style practice, use real-time Akamai interview questions; for engineer-level pipeline and Terraform topics, see Akamai engineer interview questions; and if HTTP caching itself is new, start with Akamai questions for freshers. Comparing vendors helps too: read how CloudFront invalidation works and the Fastly CDN interview questions.

CDN work sits inside a wider DevOps toolchain of pipelines, infrastructure as code and monitoring. The DevOps training in Pune covers that toolchain in the Kharadi classroom and live online across India.

FAQ

What do Akamai CDN interviews focus on?

Caching options, cache keys, TTLs for edge and browser, purge methods, tiered distribution, origin settings, DNS onboarding through edge hostnames, and debugging with Pragma headers on staging and production.

Does Akamai honor Cache-Control from my origin?

Not by default. You choose an Honor origin option in the Caching behavior to use Cache-Control, Expires or both.

How do I check if Akamai served a file from cache?

Send the Pragma value akamai-x-cache-on and read X-Cache. TCP_HIT or TCP_MEM_HIT means it came from the edge cache.

Should I use invalidate or delete?

Use invalidate for routine updates because it revalidates cheaply. Use delete when content must be removed, such as compliance or copyright cases.

What is the difference between edgekey.net and edgesuite.net?

edgekey.net edge hostnames are Enhanced TLS and need a certificate enrollment. edgesuite.net edge hostnames are Standard TLS.

When does Tiered Distribution not help?

For non-cacheable content and with API Acceleration. Use SureRoute to speed up non-cacheable requests.

Which Akamai post on this blog should I read next?

The 80+ Akamai interview questions post for breadth, then the real-time questions post for incident scenarios.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.