50+ Scenario-Based Akamai Interview Questions (2027)

52 scenario-based Akamai interview questions: cache misses, stale content, purge, origin failures, WAF false positives, debugging and edge compute.

Sep 30, 2025 - 16:24
Nov 10, 2026 - 11:04
 0  57
50+ Scenario-Based Akamai Interview Questions (2027)

Scenario-based Akamai interview questions describe a symptom, such as low cache offload, stale pages, origin errors or blocked users, and ask how you diagnose it. A strong answer names the likely cause, the Property Manager behavior or tool you would check, the fix, and how you prevent a repeat. These 52 scenarios are written in that order.

Akamai is a CDN and security platform, so interview scenarios mix caching, origin protection and traffic management. If you want the underlying network model first, read why the transport layer matters for DevOps engineers. Facts here were checked against Akamai TechDocs in November 2026. Where Akamai documents a behavior, the answer says so.

This post is the troubleshooting and incident view. Other cuts of the topic: the 80-question master guide, the most asked questions, real-time questions, advanced design questions and a preparation plan. For CDN and security fundamentals alongside it, see our DevSecOps course.

Symptom to first check

SymptomFirst place to look
Low offload, high origin trafficCache key, query strings, Vary, TTL and whether origin Cache-Control is honored
Stale content after a releaseTTL, purge method used, cache tags assigned
5xx from edge, origin looks healthyOrigin timeout, origin health detection, IP access control list
Works in one region onlyPer-edge-server caches, DNS or traffic management, origin geography
Unexpected block for real usersSecurity configuration events and rule tuning

Key takeaways

  • Start every scenario with the same questions: what changed, which hostnames and paths, which region, and what does the origin see?
  • Akamai caches the response to a request, identified by a cache key built from hostname, path, optional query strings, headers, cookies and variables.
  • By default only GET responses are cacheable, and edge servers do not honor origin Cache-Control and Expires until the property is set to do so.
  • Each edge server has its own cache, and a purge request goes to every edge server whether or not it holds the object.
  • Enhanced Debug replaces legacy Pragma debugging and uses a time-limited token from a secret key you define.
  • Never answer a security scenario by disabling protection. Tune in alert mode first, then enforce.

Cache hit ratio and performance (questions 1 to 14)

Know the cache key before the scenarios. The docs list these elements.

Cache key elementStatus (Akamai docs)Scenario effect
HostnameRequired, added by defaultDifferent Host headers can create separate cached objects
PathRequired, added by defaultPath rewrites can merge or split objects
Query stringOptional, added by defaultTracking parameters can fragment the cache
Request headersOptionalAdding a header splits the cache by that header value
CookiesOptionalCookies in the key usually destroy hit ratio
Variables from the configurationOptionalUsed for custom cache key design

1. Scenario: pages are slow and origin traffic is high. Where do you start?

Check cache offload for the affected paths. Confirm the content is cacheable, review the TTL, see whether the origin sends no-store or private directives, and look at the cache key for fragmentation from query strings or cookies.

2. Scenario: the origin sends Cache-Control: max-age=3600 but the edge ignores it. Why?

Akamai edge servers do not honor Cache-Control and Expires by default. The Caching behavior must be set to honor origin Cache-Control and Expires, or you must set the TTL in the property.

3. Scenario: which Cache-Control directives are honored once enabled?

The docs list s-maxage, max-age, no-store and no-cache, which behaves like a zero second max-age. If both max-age and s-maxage exist, Akamai uses s-maxage for its own caching.

4. Scenario: Cache-Control and Expires disagree. Which wins?

Cache-Control takes precedence. Also, you cannot override a no-store setting defined in the configuration with a response header.

5. Scenario: marketing adds ?utm_source=... to every link and the hit ratio drops. Fix?

Use the Cache Key Query Parameters behavior to exclude tracking parameters or include only the ones that change content. Then different tracked URLs resolve to the same cached object.

6. Scenario: the same object is cached many times. What inflates the cache key?

Cookies, request headers or unneeded query parameters added to the key, or a Vary header from the origin. Trim the key to what truly changes the response.

7. Scenario: only GET requests are cached. Why are POST responses always misses?

By default only content requested with GET is cacheable by edge servers. Design APIs so cacheable reads use GET.

8. Scenario: how do you cache an API response for a few seconds safely?

Set a short TTL on the specific path, include only the query parameters and headers that change the result in the cache key, and avoid caching responses that vary by user without a key that reflects it.

9. Scenario: popular objects cause an origin spike when the TTL expires. What mitigates it?

Prefresh. By default, a request arriving after 90 percent of the TTL is served from cache and triggers an asynchronous If-Modified-Since check to the origin, so the update happens before expiry.

10. Scenario: should you choose no-cache, short TTL or long TTL?

No-cache is simple but gives no offload. Short TTL balances freshness and offload for popular content. Long TTL maximises offload but needs a purge strategy. Akamai advises the longest TTL that does not serve stale content to users.

11. Scenario: a cached object disappears before its TTL ends. Is that a bug?

Not necessarily. Objects are evicted on a least recently used basis when an edge server cache is full, even before TTL, if they are rarely accessed.

12. Scenario: why is the cache warm in one city and cold in another?

Each edge server has its own cache, and content is cached only after a user request reaches that server. A first request from a new region is a miss.

13. Scenario: an object is never served from cache even though TTL is set. Checks?

Is the method GET, does the origin response carry Vary or no-store, does a later rule override caching, and does the Caching behavior apply to this path through its match criteria?

14. Scenario: the origin adds a Vary header to every response. What is the impact?

Akamai lists the presence of a Vary header in the origin response as a factor that can affect cacheability. Review which Vary values are really needed, and check how the property treats Vary before assuming the objects are cached.

Purge and content freshness (questions 15 to 22)

15. Scenario: a wrong price is live and cached. What is the fastest safe fix?

Purge the affected URLs with Fast Purge, verify with a debug request, and fix the source. If the cache is tagged, purge by cache tag to cover all variants at once.

16. Scenario: which purge methods exist?

The Purge Cache documentation lists purge by URL, by ARL, by CP code and by cache tag.

17. Scenario: when is purge by URL a poor choice?

When many variants exist: image sizes, product pages, paginated indexes and query parameters. Miss one URL and stale content survives. Akamai notes this cataloguing burden.

18. Scenario: how do cache tags help?

You label objects and purge a label to invalidate everything carrying it. The origin can send an Edge-Cache-Tag response header with up to 128 comma-delimited values, and only the first such header is respected.

Edge-Cache-Tag: casual, knits, fall-sale

19. Scenario: purge succeeded but users still see old content. Why?

The browser or another downstream cache may hold its own copy, a different cache key variant may exist, or the object was re-cached from a stale origin. Check headers, the URL variant and the origin.

20. Scenario: you purged and the origin now spikes. What is your plan?

Purging a large set causes a burst of misses. Prefer targeted tag purges, stagger broad purges, and make sure the origin has the capacity to absorb the misses.

21. Scenario: how do you reduce the need for purges?

Match TTL to content volatility, use versioned asset file names for static files, and tag dynamic content for precise invalidation.

22. Scenario: how do you automate purges after a release?

Call the Purge Cache API from the deployment pipeline, with credentials in the CI secret store, and purge by cache tag or CP code rather than long URL lists.

Origin, availability and connectivity (questions 23 to 32)

23. Scenario: users see 5xx from the edge but the origin dashboard looks fine. Next step?

Check the origin timeout and connect settings, origin health detection, firewall or access control lists that might block Akamai IPs, and the exact status code in the logs to separate edge generated errors from origin errors.

24. Scenario: how does Akamai avoid hammering a dead origin IP?

Origin Health Detection counts consecutive failed connection attempts per IP, marks it faulty at a threshold you set and stops sending requests until the retry interval. Wrong settings can multiply origin hits, so tune carefully.

25. Scenario: which error codes can trigger origin health updates?

The docs list 500, 502, 503 and 504, and you can treat a first byte timeout as an error.

26. Scenario: how do you fail over to a backup origin?

Use the Origin Failure Recovery Method rule and Policy behaviors. You can define a timeout or status codes that trigger a retry or switch to another origin, and blocklist a failed origin for a set time.

27. Scenario: how do you stop users bypassing the CDN and hitting the origin directly?

Use Site Shield to cloak the origin and Origin IP Access Control List behavior so only Akamai IPs may connect, plus origin authentication such as mutual TLS where required.

28. Scenario: after enabling origin ACLs, the site goes down. Cause?

The allowlist missed Akamai's current ranges or a network path. Roll back the change, update the list, and monitor with a canary hostname before enforcing broadly.

29. Scenario: certificate errors appear on the origin connection. What do you check?

The origin certificate chain and hostname match, the Forward Host or SNI settings in the property, expiry, and whether the origin uses a pinned certificate configuration.

30. Scenario: a deployment doubled origin load. What changed?

Probably a new cache key element, a short TTL, a purge-all, or removed caching on a path. Compare property versions in Property Manager and review the activation history.

31. Scenario: how do you safely roll out a property change?

Activate to staging first, test with a hosts file override, then activate to production and watch metrics. Keep the previous version ready to reactivate.

32. Scenario: media buffering for viewers in one region only. Approach?

Compare edge server regional metrics, check origin or storage latency from that path, review the delivery product configuration, and compare with player-side measurements from real user monitoring.

Security and protection (questions 33 to 42)

Keep answers defensive. Interviewers want controlled tuning, not workarounds.

33. Scenario: a legitimate customer is blocked by the WAF. What now?

Find the event in security logs, identify the rule and the request details, then tune with a narrow exception or move that rule to alert while you review. Avoid disabling the whole rule set.

34. Scenario: how do you roll out new WAF rules safely?

Deploy in alert mode, review events over a representative period, tune false positives, then switch to deny. This mirrors how security teams introduce any blocking control.

35. Scenario: which Akamai products does the Application Security API cover?

Akamai's Application Security API documents security configurations for Kona Site Defender, Web Application Protector, App & API Protector, Advanced Security Module and Client Reputation.

36. Scenario: traffic spikes look abnormal. How do you decide if it is an attack?

Compare request mix, geography, user agents and URL patterns with a normal baseline, check security events, and involve the security team before applying rate controls. Keep a rollback ready.

37. Scenario: how do you protect an API against excessive requests?

Apply rate controls keyed on client identity or IP, require authentication, validate input against the API definition, and cache safe reads to reduce origin load.

38. Scenario: a leaked staging hostname is being probed. What do you do?

Restrict it by network allowlist or authentication, remove public DNS if not needed, review logs for access, and confirm no sensitive data is exposed.

39. Scenario: security wants TLS 1.2 or later. How do you validate impact?

Review the share of clients still on older protocol versions in delivery reports, notify owners, stage the change and watch error rates after activation.

40. Scenario: how do you keep Debug features safe?

Use Enhanced Debug, which replaces legacy Pragma debugging and requires a time-limited token built from your secret key. Remove legacy Pragma debugging rules so internals are not exposed to anyone who sends a header.

41. Scenario: access to Control Center needs tightening. What controls matter?

Least privilege roles, multi-factor authentication, named users instead of shared accounts, and review of API clients and their scopes.

42. Scenario: a bot is scraping product prices. Defensive options?

Detect by behavior, apply rate limits or challenges on sensitive paths, serve less data to unauthenticated users, and monitor for evasion. Avoid blocking search engines you rely on.

Observability, edge compute and DNS (questions 43 to 52)

43. Scenario: how do you see exactly what happened to one request?

Use Enhanced Debug on that request to inspect edge behavior, together with access logs for the status, timing and cache result. Compare with a request that does work.

44. Scenario: how do you stream logs to your SIEM or data lake?

Use DataStream to deliver log data to supported destinations, and keep field selection tight to control volume and cost.

45. Scenario: how do you measure real user performance?

mPulse collects real user monitoring data, which shows page load behavior from actual sessions rather than synthetic tests.

46. Scenario: logic must run at the edge, such as a redirect by cookie. Options?

Property Manager rules handle many cases without code. For custom logic, EdgeWorkers deploys JavaScript functions at the edge. Keep functions small and test thoroughly.

47. Scenario: an EdgeWorker slows responses. What do you check?

Execution time, external calls made from the function, payload size, and whether caching could make the call unnecessary. Roll back to the previous version if needed.

48. Scenario: a rule order issue makes a redirect never fire. Why?

Property rules run in order and later rules or behaviors can override earlier ones. Check match criteria and rule order in the property tree.

49. Scenario: DNS cutover to Akamai goes wrong. How do you reduce risk?

Test with a hosts file override against the edge hostname, lower the TTL before the change, cut over a subset first and keep the old record ready.

50. Scenario: you must send users to the nearest healthy data centre. Which service helps?

Global Traffic Management distributes traffic by load and health, and Edge DNS hosts authoritative DNS on the platform.

51. Scenario: how do you explain a reduced cache hit ratio to management?

Describe the cause (a change in key, TTL or traffic), the user impact, the fix with its date, and the metric that will confirm recovery. Avoid blaming without evidence.

52. Scenario: how do you document a post-incident review?

Timeline, trigger, detection, impact, root cause, fix, and follow-up actions with owners, such as adding a cache key test to the deployment pipeline.

Frequently asked questions

What does an Akamai cache key contain?

The hostname and path are required. Query strings are optional but added by default. Request headers, cookies and variables from the configuration can be added.

Does Akamai honor Cache-Control from the origin by default?

No. Edge servers do not honor Cache-Control and Expires by default. You enable honoring them in the Caching behavior.

How can I purge content on Akamai?

Purge Cache supports purge by URL, ARL, CP code and cache tag. Cache tags are best for content with many variants.

What replaces Pragma debugging on Akamai?

Enhanced Debug. It uses a time-limited authentication token generated from a secret key you define and replaces legacy Pragma debugging.

How do I protect my origin from direct access?

Use Site Shield and the Origin IP Access Control List so only Akamai addresses can connect, and add origin authentication where needed.

What is prefresh?

By default, a request that arrives after 90 percent of an object's TTL is served from cache and triggers an asynchronous conditional refresh from the origin.

How do I stream Akamai logs for analysis?

DataStream delivers log data to supported destinations such as SIEM or analytics platforms.

How should I answer a scenario question in an interview?

State the symptom, the likely causes in order, the exact tool or behavior you would check, the fix and how you would prevent a repeat.

Official 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.