CDN integration in Wordpress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Identify the correct CDN integration architecture for WordPress

You want to improve your WordPress site speed globally using a CDN. Which architecture correctly shows how the CDN fits in?

A User requests go to CDN edge servers first, which cache static assets and forward dynamic requests to the WordPress origin server.

B WordPress server sends all content to CDN servers in real-time, and users always connect directly to the origin server.

C CDN servers replace the WordPress origin server entirely, serving all content without contacting the origin.

D User requests go directly to the WordPress server, which then pushes content to the CDN on demand.

💡 Hint

Think about how CDNs cache content and reduce load on the origin server.

Option A correctly describes the common CDN integration where user requests hit the CDN edge servers first. Static content is cached at the edge, and dynamic requests are forwarded to the WordPress origin server. This reduces latency and server load.

❓ scaling

intermediate

Estimate bandwidth savings from CDN caching

Your WordPress site serves 1 million page views per day. Static assets make up 60% of the bandwidth. Your CDN caches 80% of static assets. What percentage of total bandwidth is saved by the CDN?

A 32%

B 60%

C 80%

D 48%

💡 Hint

Calculate bandwidth saved as (percentage static) × (cache hit rate).

Bandwidth saved = 60% (static) × 80% (cache hit) = 48%. So the CDN saves 48% of total bandwidth.

❓ tradeoff

advanced

Choose the best CDN cache invalidation strategy for frequent WordPress updates

Your WordPress site updates content multiple times daily. Which CDN cache invalidation strategy balances freshness and performance best?

A Disable caching entirely to always serve fresh content.

B Set a short TTL (time-to-live) for cached content and use manual purge after updates.

C Set a very long TTL and never purge cache manually.

D Use a long TTL and rely on CDN to automatically detect content changes.

💡 Hint

Consider how TTL and manual purging affect cache freshness and load.

Option B balances freshness and performance by using a short TTL to limit stale content and manual purging to immediately update cache after content changes. Other options either cause stale content or high origin load.

🧠 Conceptual

advanced

Identify the main benefit of using a CDN with WordPress for global users

What is the primary benefit of integrating a CDN with a WordPress site serving users worldwide?

A Reducing latency by serving content from servers closer to users.

B Increasing WordPress plugin compatibility.

C Automatically improving SEO rankings without changes.

D Eliminating the need for a web hosting provider.

💡 Hint

Think about how CDNs improve user experience globally.

CDNs reduce latency by caching content on edge servers near users, speeding up load times worldwide. Other options are incorrect or unrelated.

❓ component

expert

Trace the request flow in a WordPress site with CDN and WAF integration

In a WordPress setup using both a CDN and a Web Application Firewall (WAF), what is the correct order of components a user request passes through?

A 1, 3, 2, 4

B 1, 4, 2, 3

C 1, 2, 3, 4

D 1, 2, 4, 3

💡 Hint

Consider how CDNs and WAFs are typically layered to protect and accelerate traffic.

The user request first hits the CDN edge server which caches content and forwards requests. The CDN forwards requests to the WAF for security checks before reaching the WordPress origin server. So the order is User → CDN → WAF → WordPress server.