Which is a common scenario when the Confluence cache is not correctly updated?

Which is a common scenario when the Confluence cache is not correctly updated?

• A. When you delete a page.
• B. When you import a site
• C. During routine backup
• D. When a user logs out

Answer: (B)

Caching speeds up Confluence by storing rendered pages, but it relies on proper invalidation when content changes to stay in sync. Importing a site can introduce a large amount of content and relationships in a way that doesn’t always trigger the usual cache invalidation, so the cache may keep old versions until it’s refreshed. That makes this scenario a common cause of the cache not being correctly updated. Deleting a page, routine backups, or a user logging out don’t typically leave the system with stale rendered content in the same way, because their effects on the cache are different (deletions usually invalidate the related cached content, backups don’t alter rendered pages, and logging out doesn’t change page data).

Caching speeds up Confluence by storing rendered pages, but it relies on proper invalidation when content changes to stay in sync. Importing a site can introduce a large amount of content and relationships in a way that doesn’t always trigger the usual cache invalidation, so the cache may keep old versions until it’s refreshed. That makes this scenario a common cause of the cache not being correctly updated. Deleting a page, routine backups, or a user logging out don’t typically leave the system with stale rendered content in the same way, because their effects on the cache are different (deletions usually invalidate the related cached content, backups don’t alter rendered pages, and logging out doesn’t change page data).