Which caching mechanisms should be considered when designing a caching strategy? (Choose two)

Question

Options

• ADispatcher-level caching
• BBrowser-based caching
• CManual cache invalidation
• DContent delivery network (CDN) caching

• A
  88% (28)
• B
  6% (2)
• C
  6% (2)

Explanation

Dispatcher-level caching (A) and CDN caching (D) are architectural caching layers built into the delivery infrastructure - they operate transparently at scale, reducing load on origin servers and improving performance for all users without requiring application code changes. Dispatcher caching (common in AEM/CMS architectures) caches rendered pages at the web server tier, while CDN caching distributes cached content globally at edge nodes closest to users.

Browser-based caching (B) is a real mechanism, but it's client-side and outside your architectural control - you can influence it via cache headers, but it's not a design decision for a caching strategy in the same infrastructure sense. Manual cache invalidation (C) is a maintenance operation, not a caching mechanism - it's something you do to a cache, not a layer you design into your strategy.

Memory tip: Think "layers you build in" vs. "things you do to a cache." Dispatcher and CDN are where caching happens; invalidation is when you clear it - the question asks for mechanisms (the where), not operations (the when).

No community discussion yet for this question.