Tableau Server can proactively warm the cache for a workbook after its underlying data extract is refreshed on a schedule. This process, known as pre-computation, improves performance by running queries and storing results before a user requests the view. For this to occur, Tableau Server checks two primary conditions: the workbook must be part of a scheduled extract refresh, and it must be considered relevant based on recent user activity. If a workbook has not been viewed recently, the server will not expend resources to pre-compute its cache, even if its data source is refreshed. Both conditions must be met for the cache warming to be initiated.

A. The publication date of a workbook is not a criterion for cache warming. A heavily used, older workbook is a better candidate for caching than a newly published, unused one.

C. Permissions, such as those for the 'All Users' group, govern access control, not the server's internal logic for performance optimization and cache management.

1. Tableau Server Help, "Configure Workbook Performance after a Scheduled Refresh": This official documentation outlines the specific criteria for warming the cache. It states, "Tableau Server will only warm the cache for a workbook if it meets all of the following criteria:

The workbook has been viewed in the last 30 days.

The workbook is part of a scheduled extract refresh."

This directly supports answers B and D.

2. Tableau Server Help, "Tableau Server Processes": The documentation for the Cache Server process explains its role in storing and managing query caches. It notes that the Backgrounder process can trigger cache warming for recently viewed workbooks after data extract refreshes, reinforcing the link between scheduled tasks (handled by Backgrounder) and recent usage as triggers for caching.