Most Asked Akamai Interview Questions for Freshers (2027)
82 Akamai interview questions for freshers: DNS, HTTP caching headers, TLS, CDN basics, WAF and DDoS, plus 2-5 year and scenario questions with answers.
The most asked Akamai interview questions for freshers test web fundamentals before products: how DNS sends a user to an edge server, how HTTP caching headers decide what the edge stores, how TLS and certificates work at the edge, and what WAF and DDoS protection do. Learn these well and Akamai's product questions become much easier.
This page has 82 questions with short answers for freshers and career switchers, plus a smaller set for people with a few years of experience and a scenario section. It focuses on the HTTP, DNS, TLS and security basics that campus and early-career Akamai rounds ask about. For product depth (Property Manager rule trees, EdgeWorkers, Fast Purge, App & API Protector), use our main 80+ Akamai interview questions guide after this one.
Key takeaways
- Candidate reports for Akamai fresher roles describe aptitude, data structures, DBMS and networking rounds. Networking questions centre on DNS, TCP, HTTP and HTTPS, so this page starts there.
- Know the HTTP caching rules from RFC 9111:
Cache-Controldirectives,Expires, validators (ETag,Last-Modified) and conditional requests. - Know how a CNAME to an Akamai edge hostname moves traffic onto the platform, and why TTLs matter during a cut-over.
- Know TLS 1.3 at a high level (RFC 8446), what SNI does, and why the edge needs a certificate for your hostname.
- Know the difference between a CDN, a WAF and DDoS protection, and that Akamai's current WAAP product is App & API Protector.
- Practise reading response headers with
curl -I. Many fresher questions are "what does this header mean?"
How the Akamai pages fit together
| Page | Best for |
|---|---|
| This page | Freshers: web, DNS, TLS and security basics as Akamai interviewers ask them |
| 80+ Akamai interview questions and answers | Akamai products and configuration, freshers to senior |
| Akamai engineer interview questions | Engineering and operations roles |
| Cloudflare security and CDN questions | Comparing CDN vendors |
Akamai interview questions for freshers: CDN and DNS basics
1. What is a content delivery network?
A CDN is a distributed set of servers that sit between users and an origin server. The servers cache and serve content close to users, which cuts latency and reduces load on the origin. Modern CDNs also terminate TLS, filter attacks and run code at the edge.
2. What does Akamai do?
Akamai sells content delivery, security (web application and API protection, bot management, DDoS protection) and cloud computing. Its cloud computing services come from the Linode acquisition and are now sold as Akamai Cloud. In interviews, describe the three areas rather than quoting network size figures you cannot source.
3. What is an origin server?
The origin is the server or service that holds the authoritative copy of the content, for example a web server, a load balancer or an object storage bucket. The CDN fetches from the origin when it does not have a valid cached copy.
4. What is an edge server?
An edge server is a CDN server close to users that receives their requests, serves cached content where it can and forwards the rest to the origin or to a parent cache.
5. How does DNS work when you type a URL into a browser?
The browser asks a recursive resolver for the name. The resolver walks from the root servers to the top-level domain servers to the domain's authoritative servers, caching each answer for its TTL. The final answer is an IP address (A or AAAA record) or an alias (CNAME) that must be resolved further.
6. How does a website start using Akamai?
The site owner creates a configuration on Akamai and points their hostname, for example www.example.com, to an Akamai edge hostname with a CNAME record. From then on, DNS answers for that name come from Akamai, which returns the address of a suitable edge server for each user.
7. What is the difference between an A record and a CNAME record?
An A record maps a name directly to an IPv4 address (AAAA for IPv6). A CNAME maps a name to another name. CDNs use CNAMEs because the provider must choose the edge IP per request. A CNAME cannot sit at the zone apex alongside other records, which is why apex domains need special handling.
8. What is a DNS TTL, and why does it matter during a migration to a CDN?
The TTL tells resolvers how long they may cache an answer. Before switching a hostname to a CDN, teams lower the TTL so that the change, and any rollback, spreads quickly. After the cut-over is stable they raise it again.
9. How does a CDN pick the server nearest to a user?
Two common methods are DNS-based mapping (the authoritative DNS returns different edge IPs depending on where the resolver or client is) and anycast (the same IP is announced from many locations and internet routing picks the nearest). Akamai's delivery mapping is DNS based. Say which method you are describing.
10. Why do CDN providers care about EDNS Client Subnet?
Without it, the CDN's DNS sees only the resolver's address, which may be far from the user (for example a public resolver in another city). EDNS Client Subnet (RFC 7871) passes part of the client's address so the CDN can map the user more accurately.
Freshers: networking basics
11. What is the difference between the OSI model and the TCP/IP model?
The OSI model has seven layers (physical, data link, network, transport, session, presentation, application) and is mainly a teaching reference. The TCP/IP model has four (link, internet, transport, application) and matches how the internet is built. Interviewers use either to check that you know where IP, TCP, TLS and HTTP sit: IP at the network layer, TCP and UDP at transport, HTTP at application, with TLS between transport and application.
12. What is the difference between TCP and UDP?
TCP is connection oriented: it sets up a connection, delivers bytes in order, retransmits lost packets and controls congestion. UDP sends independent datagrams with no delivery guarantee and less overhead. Web traffic used TCP for decades; HTTP/3 runs over QUIC, which is built on UDP and adds its own reliability. DNS queries normally use UDP and fall back to TCP for large responses.
13. Explain the TCP three-way handshake.
The client sends SYN, the server replies SYN-ACK, and the client sends ACK. Only then can data flow. With TLS on top, more round trips follow before the first HTTP byte, which is why the distance between user and server matters so much for page speed.
14. What is the difference between latency, bandwidth and throughput?
Latency is the time for data to travel (often measured as round-trip time). Bandwidth is the maximum capacity of a link. Throughput is the rate you actually achieve. A CDN mostly reduces latency by serving from nearby servers, which in turn raises throughput for short transfers such as web pages.
15. What is BGP, and why does it matter to a CDN?
Border Gateway Protocol is how networks on the internet announce which IP ranges they can reach. CDNs and DDoS services use BGP to receive traffic for their ranges, and network-level DDoS protection can work by announcing a customer's prefixes so traffic flows through scrubbing centres first.
16. What is the difference between a forward proxy and a reverse proxy?
A forward proxy acts for clients, for example a company proxy that users browse through. A reverse proxy acts for servers, receiving requests on their behalf. A CDN edge server is a large, distributed reverse proxy with caching.
17. What does a load balancer do, and how is it different from a CDN?
A load balancer spreads requests across several servers in one site or region and removes unhealthy ones. A CDN spreads users across edge locations worldwide and caches content. Many architectures use both: the CDN in front, sending cache misses to a load balancer in front of the origin servers.
18. Which ports should a fresher know for web delivery?
80 for HTTP, 443 for HTTPS (and HTTP/3 over UDP 443), and 53 for DNS over UDP and TCP. These are registered with IANA, and interviewers often ask them as a warm-up.
19. Which command-line tools help you debug delivery problems?
dig or nslookup to follow DNS answers and CNAME chains, curl -v or curl -I to see headers and timings, openssl s_client to inspect certificates, and traceroute or mtr to see the network path. Being able to read their output is worth more than memorising definitions.
20. What is the difference between IPv4 and IPv6 for a website?
IPv4 uses 32-bit addresses and is running out; IPv6 uses 128-bit addresses. A site reachable over IPv6 publishes AAAA records. CDNs commonly serve both, so a site can offer IPv6 to users even if its origin only speaks IPv4.
Freshers: HTTP and caching
21. What happens in an HTTP request and response?
The client sends a method (GET, POST and so on), a path, headers such as Host and Accept, and sometimes a body. The server replies with a status code, headers and usually a body. HTTP semantics are defined in RFC 9110.
22. What do the main status code classes mean?
1xx informational, 2xx success, 3xx redirection, 4xx client error and 5xx server error. For CDN roles, know 200, 206, 301, 302, 304, 403, 404, 429, 500, 502, 503 and 504 by heart.
23. What is caching, and what are a cache hit and a cache miss?
Caching stores a copy of a response so later requests can be served without going back to the origin. A hit means the edge served the stored copy. A miss means it had to fetch from the origin or a parent.
24. What does the Cache-Control header do?
It tells caches whether and how long they may store a response. Common directives are max-age (seconds a response stays fresh), s-maxage (the same, for shared caches such as CDNs), no-store (do not store), no-cache (store but revalidate before use), private (only the browser may store it) and public. RFC 9111 defines them.
25. What is the difference between no-cache and no-store?
no-store means no cache may keep the response at all. no-cache means caches may store it but must check with the origin before reusing it. Candidates mix these up often.
26. What are ETag and Last-Modified?
They are validators. When a cached copy goes stale, the cache sends a conditional request with If-None-Match (the ETag) or If-Modified-Since. If nothing changed, the origin answers 304 Not Modified with no body, which saves bandwidth.
27. What is a TTL in CDN caching?
It is how long the edge treats a cached object as fresh. It can come from the origin's headers or from CDN configuration that overrides them. In Akamai configurations the caching behavior sets this, and it can honour or override origin headers.
28. What is a cache key?
The cache key is what the CDN uses to decide whether two requests are for the same object. By default it is built mainly from the hostname and URL path, often with the query string. Adding or removing parts of the key changes the hit ratio and can cause users to see wrong content if done carelessly.
29. Why do query strings affect cache hit ratio?
If the full query string is part of the cache key, /app.js?v=1 and /app.js?utm_source=x are cached separately even if the content is the same. Ignoring irrelevant parameters (tracking tags) improves the hit ratio; keeping meaningful ones (version numbers) avoids serving stale files.
30. What does the Vary header do?
It tells caches that the response depends on certain request headers, for example Vary: Accept-Encoding. Caches then store separate copies per value. Broad Vary headers such as Vary: User-Agent can make content almost uncacheable.
31. What is cache purging?
Removing or invalidating cached objects before their TTL ends, for example after a content fix. On Akamai this is Fast Purge, which can invalidate (mark stale so the next request revalidates) or delete. Invalidate is the recommended default because it is gentler on the origin.
32. What is the difference between static and dynamic content for a CDN?
Static content (images, CSS, JavaScript, video segments) is the same for every user and caches well. Dynamic content (account pages, API responses with user data) changes per user or per request. CDNs still speed up dynamic content through connection reuse, route optimisation and TLS termination at the edge, even when they cannot cache it.
33. What does the Age header tell you?
How many seconds a response has been in a shared cache. A high Age on a page that should be fresh points to a long TTL or a missed purge. An Age of zero or no Age header usually means it came from the origin.
34. What are stale-while-revalidate and stale-if-error?
Cache-Control extensions defined in RFC 5861. stale-while-revalidate lets a cache serve a slightly stale copy while it fetches a fresh one in the background, which hides origin latency. stale-if-error lets it keep serving a stale copy when the origin returns errors, which keeps a site up during short origin outages. CDNs also have their own settings with the same effect.
35. What is a cache hierarchy or tiered cache?
Instead of every edge server going to the origin on a miss, edges first ask a parent cache. The parent collects requests from many edges, so the origin sees far fewer requests. On Akamai this is called Tiered Distribution.
36. How do compression and Accept-Encoding work with a CDN?
The browser lists the encodings it supports, such as gzip and br (Brotli), in Accept-Encoding. The server or edge picks one and says so in Content-Encoding, and sends Vary: Accept-Encoding so caches keep separate copies. Text files such as HTML, CSS, JavaScript and JSON benefit; images and video are already compressed.
37. What is a byte-range request, and why does video delivery use it?
The client asks for part of a file with a Range header and the server replies 206 Partial Content. Players use it to seek and to download large files in pieces. Streaming formats such as HLS and DASH split video into small segment files, which cache well at the edge.
38. Why should static asset file names change with each release?
If app.4f9a2c.js gets a new name every time its content changes, you can give it a very long TTL and never purge it. Only the HTML that references it needs a short TTL. This is the standard way to get high hit ratios and instant updates together.
Freshers: TLS and HTTP versions
39. What does HTTPS add to HTTP?
HTTPS runs HTTP over TLS, which encrypts traffic, protects it from tampering and lets the client verify the server's identity through its certificate. The current TLS version is 1.3, defined in RFC 8446.
40. Why does a CDN need a certificate for my domain?
Because the user's TLS connection ends at the edge server, not at your origin. The edge must present a valid certificate for www.example.com. On Akamai this is handled through certificate products and secure edge hostnames.
41. What is SNI?
Server Name Indication is a TLS extension in which the client sends the hostname it wants at the start of the handshake. It lets one IP address serve certificates for many hostnames, which CDNs depend on.
42. What is the connection between the edge and the origin called, and should it use TLS?
It is often called the forward or origin connection. It should use TLS too, with the edge verifying the origin certificate, otherwise traffic is encrypted only between the user and the edge.
43. What are HTTP/2 and HTTP/3?
HTTP/2 (RFC 9113) multiplexes many requests over one TCP connection with binary framing and header compression. HTTP/3 (RFC 9114) runs over QUIC (RFC 9000), which uses UDP and avoids head-of-line blocking at the transport layer. CDNs commonly offer both to clients while talking to origins over HTTP/1.1 or HTTP/2.
44. Why does TCP and TLS handshake time matter for CDNs?
Every new connection costs round trips before data flows. Ending connections at a nearby edge shortens those round trips, and the edge can keep warm, reused connections to the origin. That is one reason a CDN helps even uncacheable pages.
45. What are DV, OV and EV certificates?
They differ in how the certificate authority checks the requester. Domain Validated certificates prove control of the domain only. Organisation Validated and Extended Validation certificates also check the organisation. All three give the same encryption; browsers no longer show special EV indicators, so DV certificates automated through ACME (RFC 8555) are common for CDN hostnames.
46. What is HSTS?
HTTP Strict Transport Security (RFC 6797) is a response header that tells browsers to use HTTPS only for a domain for a set time. It stops downgrade to plain HTTP after the first visit. Turn it on carefully, because a mistake with includeSubDomains can break subdomains that still use HTTP.
47. What happens when a certificate expires on a CDN hostname?
Browsers show a security error and most users cannot reach the site. That is why certificates should be renewed automatically, with expiry monitored separately, and why the CDN's certificate and the origin's certificate both need tracking.
Freshers: web security basics
48. What is a DDoS attack?
A distributed denial-of-service attack floods a target with traffic from many sources so real users cannot reach it. Attacks can target the network and transport layers (floods of packets) or the application layer (floods of valid-looking HTTP requests).
49. How does a CDN help against DDoS?
Its large distributed capacity absorbs volumetric traffic at the edge, it only forwards valid HTTP requests to the origin, and the origin can be locked down to accept traffic only from the CDN. Akamai also sells Prolexic for protecting whole networks and data centres, not just websites.
50. What is a web application firewall?
A WAF inspects HTTP requests and blocks those that match attack patterns such as SQL injection or cross-site scripting. Akamai's current web application and API protection product is App & API Protector; older material that names Kona Site Defender is out of date.
51. What is the OWASP Top 10?
A regularly updated list of the most important web application security risks published by the OWASP Foundation. Interviewers use it to check you know common attack classes such as injection, broken access control and security misconfiguration. Check owasp.org for the current edition before your interview.
52. What is a bot, and why manage bots?
A bot is automated software making requests. Some are useful (search engine crawlers), others scrape prices, stuff stolen credentials or hoard inventory. Bot management tells them apart and decides whether to allow, slow, challenge or block. Akamai sells Bot Manager for this.
53. What is rate limiting?
Limiting how many requests a client can make in a time window, to protect services from abuse or overload. A response of 429 Too Many Requests is the usual signal to the client.
54. What is SQL injection, and how does a WAF help?
SQL injection happens when user input is placed into a database query without proper handling, so crafted input changes the query. The real fix is parameterised queries in the application. A WAF adds a layer that detects and blocks common injection patterns in requests, which buys time and stops automated attacks.
55. What is cross-site scripting?
XSS happens when a site includes untrusted input in a page without encoding it, so a script runs in other users' browsers. Fixes are output encoding, a Content Security Policy header and safe templating. A WAF can block common XSS payloads, but it does not replace fixing the code.
56. What is the difference between a positive and a negative security model?
A negative model blocks known bad patterns (signatures for attacks). A positive model allows only known good behaviour, such as requests that match an API schema, and blocks everything else. Positive models are stronger for APIs but need accurate definitions to avoid blocking real users.
57. What is a WAF false positive, and how do you handle one?
A legitimate request blocked by a rule. Find the rule from the security event logs, confirm the request is legitimate, then add a narrow exception for that path or parameter rather than turning the rule off. Many teams run new rules in alert-only mode first.
58. Why is it useful to run WAF rules in alert mode before blocking?
Alert mode logs what would have been blocked without affecting users, so you can measure false positives against real traffic before switching to deny. It is a standard rollout step for new rule sets.
59. What is the shared responsibility between a CDN security service and the application team?
The provider runs the edge platform, its filtering capacity and rule updates. The customer chooses and tunes the rules, protects the origin from direct access, fixes vulnerabilities in the application and handles credentials. A WAF in front does not make an insecure application safe.
Akamai interview questions for 2 to 5 years of experience
These apply the basics to Akamai configuration. Answer them with the fundamentals above, then name the Akamai feature.
60. How do you check whether a response came from Akamai's cache?
Send a request with Akamai's Pragma debug headers, for example akamai-x-cache-on and akamai-x-get-cache-key, and read the X-Cache and X-Cache-Key response headers. TCP_HIT means served from cache and TCP_MISS means fetched forward. Only use this on properties you are authorised to test.
curl -sI https://www.example.com/logo.png \
-H "Pragma: akamai-x-cache-on, akamai-x-get-cache-key, akamai-x-check-cacheable"
61. How do you test a configuration before it reaches real users?
Activate the property version on Akamai's staging network, then point your test machine at the staging edge hostname (for example through a hosts file entry) and run tests. Activate on production only when tests pass, and keep the previous version ready to reactivate.
62. The origin sends Cache-Control: no-store, but the business wants the page cached for 5 minutes. What do you do?
First ask why the origin sends no-store; it may contain personal data. If the page is the same for everyone, either fix the origin header or set a caching behavior that overrides origin headers for that path with a 5-minute TTL, and control what browsers get separately with downstream cacheability settings.
63. How do you stop attackers from bypassing Akamai and hitting the origin directly?
Restrict the origin to accept traffic only from Akamai addresses (Akamai offers Site Shield for a stable list), require a secret header or mutual TLS from the edge, and do not publish origin hostnames in DNS. This is a defensive control every CDN deployment should have.
64. Why might a site still feel slow after moving to Akamai?
Common reasons are a low cache hit ratio (wrong cache keys, short TTLs, cookies or Vary making objects uncacheable), slow origin responses for dynamic pages, large unoptimised images, or third-party scripts that the CDN does not serve. Measure with real user monitoring before tuning.
65. How do you roll out a cache key change safely?
Test on staging, check that pages differ only where they should, then activate during low traffic. Expect a temporary drop in hit ratio and a rise in origin load as the cache refills, and warn the origin team.
66. How do cookies affect caching at the edge?
A response with Set-Cookie is usually personal and should not be cached for everyone, and many CDN configurations treat such responses as uncacheable by default. Requests carrying cookies can also be excluded from caching. Strip cookies that static assets do not need, and serve assets from paths or hostnames that do not receive session cookies.
67. What is the difference between edge TTL and browser TTL?
Edge TTL controls how long Akamai keeps an object. Browser TTL, set through the Cache-Control header sent to the client (downstream cacheability in Akamai terms), controls how long the user's browser keeps it. You can purge the edge but not users' browsers, so browser TTLs for HTML should stay short.
68. Should redirects be handled at the edge or at the origin?
Simple, stable redirects such as HTTP to HTTPS or old paths to new ones are cheaper at the edge, because the request never reaches the origin. Redirects that depend on application data belong at the origin. Keep edge redirect rules documented and tested, because they are easy to forget.
69. When would you move logic from the origin to EdgeWorkers?
When it is small, latency sensitive and does not need the origin's data: header changes, A/B test bucketing, geolocation-based routing or simple request validation. Keep heavy business logic and anything needing a database at the origin. EdgeWorkers run JavaScript at Akamai's edge with resource limits per tier.
70. How do you calculate cache hit ratio, and what is origin offload?
Hit ratio is hits divided by total requests at the edge. Offload is the share of requests or bytes that the CDN served without going to the origin. They differ because a request can miss at the edge but hit a parent tier. Origin teams care most about offload, because it decides how much traffic their servers see.
71. What is the difference between real user monitoring and synthetic monitoring?
Real user monitoring collects timings from actual browsers, so it shows what users experience across devices and networks; Akamai's product for this is mPulse. Synthetic monitoring runs scripted checks from fixed locations on a schedule, which is better for alerting on outages and comparing releases. Teams use both.
72. What would you check before moving a site onto a CDN?
Which hostnames move, current DNS TTLs, which paths can be cached and for how long, cookies and headers the application depends on, how the origin will be protected, certificate coverage for every hostname, logging and monitoring, and a rollback plan (point DNS back at the origin). Test on the staging network with real pages before switching DNS.
73. Can you cache API responses on a CDN?
Yes, when the response is the same for many callers and can tolerate being a few seconds or minutes old, such as product catalogues or public reference data. Personalised or authenticated responses usually must not be shared. Use short TTLs, include only the query parameters that change the result in the cache key, and never cache responses that carry personal data.
74. How do geolocation and device detection at the edge work?
The CDN maps the client IP to an approximate location and can inspect the User-Agent to guess the device type. Configurations can then redirect, choose an origin or add headers for the application. IP-based location is approximate, so do not use it alone for legal or security decisions without a fallback.
Senior-level questions
75. How would you explain the trade-off between long TTLs and fast content updates?
Long TTLs raise hit ratio and cut origin cost, but changes take longer to appear. The usual answer is long TTLs for versioned assets (file names that change with each release), short TTLs or revalidation for HTML, and purge by tag or URL for urgent fixes. Purge should not replace a sensible TTL design.
76. How do you manage Akamai configuration as code?
Store property rules as JSON, manage them with the Akamai Terraform provider or the Property Manager API through a pipeline, test on staging automatically and promote the same version to production. Keep API credentials in the pipeline's secret store. Our post on CDN integrations in DevOps deployments covers where this fits in a release pipeline.
Scenario-based questions
77. Users in one region see an old version of the home page after a release. Others see the new one.
Check the TTL and cache key for the HTML, whether the release changed file names for assets, and whether a purge ran and completed. Compare X-Cache and Age headers from different regions. Invalidate the HTML with Fast Purge, then fix the release process so HTML uses short TTLs or revalidation and assets use versioned names.
78. During a traffic spike, the origin's CPU goes to 100% even though Akamai is in front.
Look at the hit ratio and which paths miss. Typical causes are a purge of a large set of objects, cache-busting query strings from a campaign link, or an API path that was never cacheable. Short-term, cache the hot path briefly or enable features that collapse duplicate requests to the origin; long-term, fix the cache key and TTL design and rate-limit abusive clients.
79. The site shows certificate errors for all users this morning.
Check the certificate the edge presents with openssl s_client -connect www.example.com:443 -servername www.example.com: expiry date, hostname coverage and chain. If it expired, renew or redeploy it on the CDN as the priority, then check the origin certificate too. Afterwards, add expiry monitoring from outside the platform and confirm auto-renewal works.
80. After switching DNS to Akamai, some users still reach the old servers.
Resolvers cache the old answer until its TTL expires, and some ignore TTLs. Check the TTL that was set before the change. Keep the old servers running and correct until traffic drains, and do not remove them on the same day. Next time, lower the TTL a day or two before the switch.
81. After a WAF rule update, the mobile app's login fails for many users.
Check security event logs for blocks on the login path and identify the rule. Add a narrow exception or roll back the rule change, confirm logins recover, then work with the app team to see what in the request looks suspicious. Prevention: test rule updates in alert mode against real traffic first.
82. Video playback stalls for users in one country only.
Compare cache hit ratio and error rates for that region, check whether segments are being cached or fetched from the origin every time, and look at origin capacity and route. Test from that region with a remote testing service. Typical fixes are caching segments correctly, using tiered caching and making sure manifests have short TTLs while segments have long ones.
How fresher rounds are usually structured
Public candidate reports for Akamai early-career roles describe a mix of an aptitude or coding test, one or two technical interviews and a managerial or HR conversation. Reports differ by year, role and location, so treat this as a guide rather than a fixed process.
| Round | What candidates report being asked | How this page helps |
|---|---|---|
| Online test | Aptitude, data structures and algorithms, sometimes SQL | Not covered here; practise DSA separately |
| Technical interview | DNS, TCP, HTTP and HTTPS, operating systems, projects | Questions 1 to 59 |
| Role-specific interview | Caching, security or operations depending on the team | Questions 60 to 82 |
| Managerial or HR | Projects, teamwork, why the company | Prepare two project stories with numbers you can defend |
Common mistakes in Akamai fresher interviews
- Saying "the CDN caches everything". Explain what decides cacheability: headers, configuration, cookies and the cache key.
- Mixing up no-cache and no-store, or 502 and 504.
- Claiming HTTPS hides the hostname. With classic TLS, the SNI field and DNS lookups reveal it; newer mechanisms such as Encrypted Client Hello aim to change that but are not yet universal.
- Describing DDoS protection and a WAF as the same thing.
- Quoting Akamai network size or customer numbers from memory. If you cannot cite it, describe what the platform does instead.
What to practise before the interview
- Run
dig www.example.comon a few large sites and follow the CNAME chain to the CDN. - Use
curl -Ito readCache-Control,Age,ETagandVaryheaders on real pages. - Use
openssl s_client -connect host:443 -servername hostto see a certificate chain and the effect of SNI. - Read RFC 9111 sections on freshness and validation once; it answers half the caching questions.
If you want structured practice with web security, WAF rules and pipeline security, our DevSecOps training in Pune runs in the Kharadi classroom and live online. For broader networking basics, read our explainer on how S3 works with a CDN.
FAQ
What do Akamai interviews ask freshers?
Candidate reports mention aptitude tests, data structures, DBMS and networking. The networking part usually covers DNS, TCP, HTTP and HTTPS, which is why this page starts with those before Akamai products.
Do I need to know Akamai products as a fresher?
Know what a CDN, WAF and DDoS protection do and the names of the main products, such as App & API Protector, Bot Manager and Prolexic. Deep product configuration is expected for experienced hires.
What is the difference between no-cache and no-store?
no-store means no cache may keep the response. no-cache means caches may keep it but must revalidate with the origin before each reuse.
How does a website start using Akamai?
The owner creates an Akamai configuration and points the hostname to an Akamai edge hostname with a DNS CNAME record, usually after lowering the record's TTL so the switch spreads quickly.
Which RFCs are worth reading for CDN interviews?
RFC 9110 (HTTP semantics), RFC 9111 (HTTP caching), RFC 8446 (TLS 1.3) and, for newer protocols, RFC 9113 (HTTP/2) and RFC 9114 (HTTP/3).
Is Kona Site Defender still Akamai's WAF?
No. Akamai now sells App & API Protector as its web application and API protection product, and the Kona Site Defender product page redirects to it.
How can I check if a page is served from Akamai's cache?
Send Akamai Pragma debug headers with curl and read the X-Cache response header. TCP_HIT means a cache hit; TCP_MISS means the edge fetched it forward.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0