Query caching is specifically designed to improve response time for repeated analytical queries. Oracle Analytics Cloud stores previously computed query results in a local query cache. When a later request can be satisfied from an existing cache entry, Oracle Analytics can return the precomputed result rather than execute another request against the underlying database.

This scenario is particularly suitable for caching because the underlying data changes only once per day. The administrator can therefore maintain a cache lifecycle aligned with the daily refresh process. After source data changes, relevant cache entries should be purged or refreshed to prevent stale results. Between refreshes, frequently repeated analyses can achieve significant performance improvements while reducing database processing, network traffic, and Oracle Analytics processing overhead.

Disabling caching would increase repeated source-system workload. Adding dashboard prompts doesn't inherently reduce query execution cost. Moving analyses into Personal Folders changes catalog organization and access, not query-processing efficiency.

Oracle explicitly states that query caching can dramatically improve query performance by satisfying subsequent requests without accessing back-end data sources. Therefore, D is correct.

Reference Topic: Managing Administration, Security, and Performance — Query Cache Management

===============