A developer makes the requested changes to a page on a live site. The developer then verifies that changes are reflected correctly on the page. The customer reports that they still set an older…

Question

Options

• ADispatcher cache refresh
• BPage reflects changes m Incognito mode
• CGroup and access
• DPrevious changes on the landing page

• A
  70% (16)
• B
  17% (4)
• C
  9% (2)
• D
  4% (1)

Explanation

When a developer updates a live AEM page but customers still see the old version, the Dispatcher cache is the most likely culprit - it serves cached HTML to users and won't reflect new content until the cache is invalidated or flushed. Option A is correct because this is a classic Dispatcher caching scenario: the change is live on the server, but the cache layer hasn't been refreshed.

Why the distractors are wrong:

• B (Incognito mode) rules out browser caching, which is the developer's own local issue - not what's causing a customer to see old content on a live site.
• C (Groups and access) is a permissions concern; if the customer lacked access, they'd see an error or login prompt, not an older version of the page.
• D (Previous changes on the landing page) is vague and not a standard verification step - it doesn't address why a published change wouldn't be visible.

Memory tip: Think of the Dispatcher as a "middleman" between the server and the user. If the developer sees the new version but the customer doesn't, the middleman is still handing out old copies - flush the Dispatcher first.

No community discussion yet for this question.