Explanation/Reference:
In a standard OBIEE implementation, we generally want to purge and re-build the cache after every ETL (extract, transform, and load) run.
Incorrect answers:
A: A cache item might be out of date.
B: Cache reduces traffic to the back end database. At worst it does not change the amount traffic.
D: The cache disk should be at faster than the disk of the database.
E: OBIEE Caching and Cache Seeding
Cache is a component that improves performance by transparently storing data such that future requests for the same criteria can be served much faster. Like other application cache is not virtual memory in OBIEE. In OBIEE cache will be stored as files on the Hard Disk of the OBIEE Server in the form of files. By Default caching is enabled in the OBIEE server configuration.
For time-consuming Dashboard Pages, we can use the concept of cache seeding in OBIEE, this can be configured as a scheduled job that will ensure that the data is cached and readily available as and when the user runs the dashboard.