A client's site does not show the latest page content for some site visitors. The client has two data centers with each configured with a Dispatcher connected to two Publish machines. The site load…

Question

Options

• ADisable caching on all impacted data centers Dispatchers to force the Publish machines to serve
• BCheck the Publish instance(s) attached to the Dispatcher associated to the impacted data center
• CCheck the SSL certificate on the impacted data center's load balance.
• DReview the log files on the Author instances to determine if there are any template errors

• A
  27% (9)
• B
  6% (2)
• C
  58% (19)
• D
  9% (3)

Explanation

Option C points to the SSL certificate on the load balancer of the impacted data center because an expired or misconfigured SSL certificate can cause intermittent failures in routing and backend communication - preventing cache invalidation signals from properly reaching the Dispatcher, which results in stale content being served to some visitors. The intermittent, single-data-center pattern is the key diagnostic clue: infrastructure-layer issues like SSL problems surface this way, while application-layer issues typically affect all traffic equally.

Why the distractors are wrong:

• A is counterproductive - disabling caching entirely would devastate performance and doesn't fix the root cause.
• B is tempting but incorrect; a replication failure on the Publish instances would cause consistent stale content for that data center, not intermittent issues.
• D is irrelevant - Author instance template errors would affect content creation globally, not delivery from a specific data center.

Memory tip: Match the symptom pattern to the layer - intermittent + geographically isolated points to network/infrastructure (SSL, load balancer), not application code or caching configuration.

No community discussion yet for this question.