CDN Mid
In the context of a CDN, what is the 'Last Mile' vs. the 'Middle Mile' problem?
Select the correct answer
Last mile is the edge-to-origin hop; middle mile is the user's connection to their local ISP.
Last mile is the origin's database query; middle mile is the cache lookup performed at the edge.
Last mile is the TLS handshake time; middle mile is the time spent rendering content in browser.
Last mile is the user-to-edge link; middle mile is the path from edge to the origin server.
When would you NOT want to use a CDN for a specific type of data or application?
Select the correct answer
When large media files must reach users located far from the origin server.
When serving static assets to a globally distributed audience across many regions.
When traffic is bursty and you need to absorb sudden spikes in user demand.
When content is unique per user and rarely reused, caching gives little benefit.
What are the primary tradeoffs of adding a CDN to your stack?
Select the correct answer
Better security traded against guaranteed downtime and total loss of analytics.
Faster delivery traded against added cost, complexity, and cache staleness risk.
Cheaper hosting traded against higher latency and frequent complete origin outages.
Slower delivery traded against lower cost, simpler setup, and always-fresh data.
How does a CDN reduce origin bandwidth and load, and how would you quantify the offload it provides?
Select the correct answer
Edge serves cached hits; offload is measured by the cache hit ratio of bytes served.
Edge rewrites requests; offload is measured by the number of edge POPs deployed.
Origin shards traffic; offload is measured by the total concurrent user connections.
Origin compresses responses; offload is measured by the average response time gain.
Can a CDN accelerate dynamic (non-cacheable) content? Explain 'Dynamic Site Acceleration' (DSA).
Select the correct answer
Yes; DSA optimizes the network path and connections rather than caching content.
Yes; DSA caches dynamic responses briefly at edge to serve repeat visitors fast.
No; DSA only compresses payloads at the origin before sending them across the wire.
No; dynamic content cannot be accelerated because it is never cacheable at edge.
How do CDNs perform 'Image Optimization' at the edge (e.g., WebP conversion, resizing) and why is it better than doing it on the fly at the origin?
Select the correct answer
Edge compresses files once at origin upload, requiring manual variant generation later.
Origin transforms each request live, which the edge caches but never offloads CPU from.
Edge transforms and caches variants near users, sparing origin CPU and cutting latency.
Edge stores only original files and resizes inside each user's browser on demand.
Explain how 'Signed URLs' or 'Signed Cookies' work to protect premium/private content delivered via CDN.
Select the correct answer
They redirect users to an auth server that issues a session token before any content is ever served.
They embed a cryptographic signature and expiry that the edge validates before serving the content.
They place the user credentials in the URL so the origin re-verifies each request against its store.
They encrypt the file contents end-to-end so only clients holding the decryption key can view them.
What is the role of a Web Application Firewall (WAF) when deployed at the CDN edge compared to a WAF on the application server?
Select the correct answer
An edge WAF removes the need for any origin security because traffic is already fully authenticated.
An edge WAF only inspects TLS handshakes while the origin WAF decrypts and scans the full payload.
An edge WAF filters malicious requests near users before they reach origin, cutting load and latency.
An edge WAF caches the blocked requests so that repeated attacks are served faster from edge cache.
When would you use 'Signed URLs' versus 'Signed Cookies' for content protection?
Select the correct answer
Use signed URLs for streaming video segments; use signed cookies for static image and CSS assets.
Use signed URLs for many files at once; use signed cookies only for one-time single-file downloads.
Use signed URLs for a single file; use signed cookies to grant access to many files at once.
Use signed URLs when content is public; use signed cookies when content must be encrypted at rest.
What is rate limiting at the edge, and why is enforcing it at the CDN more effective than at the origin?
Select the correct answer
It queues excess requests at the origin and replays them slowly once traffic returns to normal.
It caps request rates per client at the edge, stopping abuse before it reaches origin resources.
It caps the origin's outbound bandwidth so the server never exceeds its provisioned transfer limit.
It throttles only cached responses at the edge while sending uncached requests straight to origin.
What is bot management, and how does a CDN distinguish and mitigate malicious bots at the edge?
Select the correct answer
It inspects only the User-Agent string and trusts any request claiming to be a search engine.
It relies solely on a static IP blocklist updated nightly to drop traffic from known bad networks.
It identifies bots via fingerprinting, behavior, and challenges, blocking malicious ones at the edge.
It blocks every automated client by default, forcing all bots including crawlers to register a key.
How do you define and measure 'Cache Hit Ratio', and what are three common reasons it might be lower than expected?
Select the correct answer
Hits divided by origin requests; lowered by large objects, bandwidth caps, and DNS issues.
Misses divided by total requests; lowered by long TTLs, shared keys, and rare purges.
Hits divided by total requests; lowered by short TTLs, fragmented keys, and frequent purges.
Edge bytes over total bytes; lowered by TLS overhead, gzip cost, and slow origins.
How do you debug a 'Cache Miss' that you expected to be a 'Cache Hit'? Walk me through your diagnostic process.
Select the correct answer
Restart the origin server, clear the browser cache, and increase origin memory allocation.
Disable caching entirely, then re-enable it and monitor the origin CPU for spikes.
Upgrade the CDN plan, add more edge locations, and enable HTTP/2 on the origin server.
Inspect cache headers, then verify the cache key, TTL, and Vary configuration.
What is 'Cache Hit Ratio' (CHR) and what are three specific ways you can improve it?
Select the correct answer
Ratio of bytes to objects; improve via image compression, minification, and tiered caches.
Ratio of origin to edge hits; improve via more POPs, faster DNS, and TLS session reuse.
Ratio of misses to requests; improve via shorter TTLs, unique keys, and frequent purging.
Ratio of hits to requests; improve via longer TTLs, normalized keys, and cacheable responses.
If a user reports a slow site but the origin server has low CPU/RAM usage, how would you use CDN logs to investigate?
Select the correct answer
Analyze origin logs for slow SQL queries, thread pools, and garbage collection pauses.
Analyze DNS logs for resolution delays, TTL expiry, and recursive resolver failures.
Analyze edge logs for cache miss rates, TTFB, status codes, and per-region latency.
Analyze browser logs for render-blocking scripts, layout shifts, and paint timings.
Explain the 'Vary' header. How does it influence how a CDN stores and serves different versions of a resource?
Select the correct answer
It instructs caches how long to retain a resource before revalidating with origin.
It instructs caches to bypass storage entirely and always fetch from the origin.
It instructs caches to compress responses based on the client's bandwidth limit.
It instructs caches to store separate variants keyed by the listed request headers.
What is a 'Cache Key' and how do query strings or headers like User-Agent affect cache fragmentation?
Select the correct answer
Identifier for a cached object; including query strings or User-Agent multiplies variants.
Compression setting for a cached object; query strings and User-Agent shrink each variant.
Expiration timer for a cached object; query strings and User-Agent extend its lifetime.
Encryption token for a cached object; query strings and User-Agent secure each variant.
What is 'Negative Caching' and why is it important for a CDN?
Select the correct answer
Caching only successful responses and dropping all error codes so clients always retry against the origin
Storing stale copies of objects so they can be served whenever the origin becomes completely unreachable
Caching error responses like 404 or 500 briefly to shield the origin from repeated failing requests
Refusing to cache any content from origins that have previously returned slow or failing responses to users
Explain 'Cache Key Normalization'. Why would you want to strip certain query parameters at the edge?
Select the correct answer
Removing irrelevant params (e.g. tracking tags) so equivalent URLs map to one cache entry, raising hit ratio
Encrypting query parameters before they are stored so that the cache key cannot leak sensitive user data
Adding extra parameters to each URL so every visitor receives a uniquely personalized cached response object
Sorting query parameters alphabetically so the origin can validate request signatures more reliably at scale
Explain the difference between a 'Hard Purge' and a 'Soft Purge' (Invalidation vs. Revalidation).
Select the correct answer
Hard purge applies to static assets and soft purge applies exclusively to dynamic API responses on the edge
Hard purge removes objects after their TTL expires while soft purge removes them before the TTL has elapsed
Hard purge deletes content immediately; soft purge marks it stale so it is revalidated on next request
Hard purge clears only the origin's cache while soft purge clears every edge node's cache simultaneously fast
Explain the 'stale-while-revalidate' directive and how it improves the user experience compared to a standard TTL.
Select the correct answer
It blocks the user request at the edge until the origin confirms the content is still fresh and unchanged
It serves stale content instantly while asynchronously fetching a fresh copy, avoiding latency on expiry
It extends the original TTL by a fixed window so the object never actually expires until traffic stops
It revalidates every cached object on a background timer regardless of whether any user has requested it
What is the difference between Cache Invalidation (Purging) and Cache Expiration (TTL), and which is more expensive for a global CDN?
Select the correct answer
Both rely on the same TTL timer internally, so neither is more expensive than the other at global scale
Expiration actively pushes removals to all nodes while purging waits for the TTL, making expiration costlier
Expiration removes content passively by time; purging actively forces removal across edges and costs more
Purging only affects one edge node at a time so it is far cheaper than letting content expire globally
Explain the 'stale-if-error' directive and how a CDN uses it to keep serving content when the origin is unavailable.
Select the correct answer
It lets the CDN serve an expired cached copy when the origin returns errors or is unreachable
It forces the CDN to purge stale objects immediately whenever the origin begins returning error codes
It instructs the CDN to retry the origin repeatedly until a fresh non-error response is finally returned
It tells the browser to ignore all cache rules and always fetch content directly from the origin
How does a CDN handle a 'Flash Crowd' or a sudden viral traffic spike without crashing the origin?
Select the correct answer
Edges serve most requests from cache and collapse concurrent misses into one origin fetch via request coalescing
Edges queue all viral traffic and replay it slowly to the origin once the demand spike has fully subsided
Edges forward every incoming request straight to the origin but spread them evenly using round-robin load balancing
Edges automatically block a portion of users with rate limits so the origin only ever sees baseline traffic
How would you use a CDN to implement 'Geo-fencing' or localized content delivery?
Select the correct answer
Use edge logic on the client's geolocation to serve, redirect, or block content based on country or region
Use the browser's stored language preference exclusively, ignoring the client IP and edge location entirely
Use origin-only checks that inspect each request's location after the CDN has already returned its cached copy
Use a single shared cache key for all regions so every user worldwide receives identical localized content
How does a CDN handle 'Cold Starts' and what is 'Cache Warming'?
Select the correct answer
A cold start is a TLS handshake delay, and warming means keeping persistent connections open to every client
A cold start is an empty edge cache causing origin fetches; warming pre-loads content so early users hit cache
A cold start is an overloaded origin server, and warming means scaling up extra origin capacity in advance
A cold start is expired DNS records, and warming means refreshing those records before users begin requesting
What are the performance benefits of terminating TLS/SSL at the edge rather than at the origin?
Select the correct answer
The handshake happens close to the user, cutting round-trip latency and offloading crypto work from the origin
The certificate is validated only once globally, so individual users avoid repeating any handshake round-trips
The handshake is skipped entirely for nearby users, removing all encryption overhead between client and edge
The origin handles every handshake but the edge caches the negotiated session keys for all future visitors
How does a CDN use 'Connection Reuse' (Keep-Alive) between the edge and the origin to improve performance?
Select the correct answer
It keeps open connections in a pool so subsequent origin fetches skip repeated TCP and TLS handshakes
It opens a brand new connection per request but caches the TLS certificate so verification can be skipped
It merges many origin requests onto one connection so the origin only ever processes a single response
It holds the client browser connection open indefinitely so the origin never needs to respond more than once
What are the tradeoffs of enabling 'Edge Minification' or Brotli/Gzip compression at the CDN layer?
Select the correct answer
It cuts payload size and speeds delivery but costs edge CPU and complicates caching of variants.
It guarantees smaller payloads at zero CPU cost since edge nodes compress all content for free.
It always improves security by encrypting assets while shrinking them before reaching clients.
It removes the need for origin compression and never affects cache hit ratios or content types.
What is 'Brotli' or 'Gzip' compression at the edge, and why is it better to do it there than at the origin?
Select the correct answer
Compressing at the edge raises origin bandwidth because each request recompresses content fresh.
Compressing at the edge offloads origin CPU and reuses compressed cached objects across users.
Compressing at the edge replaces caching entirely since compressed files never need revalidation.
Compressing at the edge encrypts traffic so the origin never needs to serve TLS to clients.
What is 'Edge Compute' (e.g., Workers/Functions-at-the-Edge), and how does it change the traditional 'static' nature of a CDN?
Select the correct answer
It caches database queries at the edge so origins no longer process any dynamic requests at all.
It compresses static assets automatically at every edge so dynamic content is never required again.
It moves the entire backend server into each edge node, replicating databases globally for writes.
It runs custom code on edge nodes, letting CDNs handle dynamic logic instead of only static files.
What is 'Edge Compute' (or Edge Functions) and what logic is appropriate to move from the backend to the edge?
Select the correct answer
Stateful session management requiring strong consistency and frequent writes to shared storage.
Heavy database joins and long transactions that need consistent access to a central data store.
Large batch jobs and analytics pipelines that process gigabytes of data over many long minutes.
Lightweight stateless tasks like auth, redirects, and header rewrites that benefit from low latency.
When would you use an Edge Function to modify a request/response instead of doing it at the origin?
Select the correct answer
When changes require complex queries against the primary database before responding to the client.
When changes must run only once globally and stay strongly consistent across every region instantly.
When changes need low latency near users and don't require origin data, like redirects or headers.
When changes involve large file processing and long-running computation tied to backend resources.
When would you use an 'Edge Function' versus a traditional serverless function?
Select the correct answer
Edge functions support longer execution and larger memory; serverless is limited to short bursts only.
Edge functions are stateful and cached; serverless functions are stateless and never reused at all here.
Edge functions always access databases faster; serverless cannot connect to any persistent data store.
Edge functions run globally near users with tight limits; serverless runs regionally with more resources.