CDN configuration in Remix - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Identify the correct CDN architecture for Remix app static assets

You have a Remix app serving dynamic pages and static assets. Which CDN architecture best improves static asset delivery without affecting dynamic content?

A Use a CDN only for static assets like images, CSS, and JS, while dynamic pages are served directly from the origin server.

B Route all requests, including dynamic pages, through the CDN to cache everything aggressively.

C Do not use a CDN; serve all content directly from the origin server to avoid caching issues.

D Use the CDN only for dynamic pages and serve static assets directly from the origin.

💡 Hint

Think about which content benefits most from caching and which should remain fresh.

Static assets benefit from CDN caching to reduce latency and load on the origin. Dynamic pages often require fresh data and should be served directly or with careful caching.

❓ scaling

intermediate

Estimate CDN bandwidth savings for a Remix app

Your Remix app serves 1 million static asset requests daily, each averaging 500 KB. If a CDN caches 80% of these requests, how much bandwidth is saved on the origin server per day?

A 200 GB

B 800 GB

C 500 GB

D 400 GB

💡 Hint

Calculate total data served, then multiply by cache hit ratio.

Total data = 1,000,000 * 500 KB = 500,000,000 KB = 500 GB. CDN caches 80%, so origin saves 80% of 500 GB = 400 GB.

❓ tradeoff

advanced

Choose the best cache invalidation strategy for Remix app updates

Your Remix app updates static assets frequently. Which cache invalidation strategy balances freshness and performance best?

A Set a very short TTL (time-to-live) so CDN caches expire quickly, ensuring fresh content but increasing origin load.

B Manually purge CDN cache after every deployment, keeping TTL long for performance.

C Use versioned URLs for static assets so new versions bypass CDN cache automatically.

D Disable CDN caching entirely to avoid stale content.

💡 Hint

Consider how to avoid stale content without hurting performance.

Versioned URLs let CDNs cache assets indefinitely while ensuring new versions load fresh content without manual purging or short TTLs.

🧠 Conceptual

advanced

Understand CDN edge server behavior for dynamic Remix routes

How do CDN edge servers typically handle dynamic routes in a Remix app that require user-specific data?

A Bypass cache for dynamic routes, forwarding requests to origin for fresh user-specific content.

B Cache dynamic routes aggressively to reduce origin load, serving same content to all users.

C Cache dynamic routes but vary cache by user cookies automatically without configuration.

D Serve dynamic routes from CDN edge servers without contacting origin or cache.

💡 Hint

Think about user-specific content and caching risks.

Dynamic routes with user data should bypass cache to avoid serving wrong content. CDNs forward these requests to origin.

❓ component

expert

Design a CDN configuration for global Remix app with multi-region origin failover

You must design a CDN setup for a Remix app deployed in multiple regions with automatic failover if one origin region fails. Which component setup ensures high availability and low latency?

A Use a single origin endpoint and rely on CDN caching to handle failover without origin switching.

B Configure CDN with multiple origin endpoints and health checks to route traffic to the nearest healthy origin region automatically.

C Deploy CDN only in one region and manually switch origin endpoints on failure.

D Disable CDN caching and use DNS round-robin to distribute traffic across origin regions.

💡 Hint

Consider automatic failover and latency optimization.

CDNs with multi-origin support and health checks can route requests to the nearest healthy origin, ensuring availability and performance.