Which three statements are true about the use of the query result cache? (Choose three.)

Oracle permits results from queries that were transparently rewritten by the optimizer to use a materialized view to be stored in the result cache. This allows subsequent identical queries to benefit from both the materialized view optimization and the result cache hit, reducing redundant computation.

When a session has RESULT_CACHE_MODE set to FORCE or similar settings, Oracle may serve a cached result before the underlying data change has triggered cache invalidation. This staleness window exists because invalidation is event-driven but not always instantaneous across all cache entries.

Joins involving views that contain non-deterministic functions, sequence references, or other non-cacheable constructs prevent the result from being stored in the query result cache, as Oracle cannot guarantee stable invalidation semantics.

This statement incorrectly asserts an absolute restriction - Oracle result cache behavior with distributed queries has nuances based on object types and hints used, making the blanket claim of 'never' inaccurate.

Setting query_rewrite_enabled to FALSE disables the query rewrite mechanism that the result cache relies on for certain cached plans. When this parameter is disabled, Oracle cannot retrieve matching results from the result cache for queries that would otherwise qualify.

Oracle does not store results from queries that reference remote objects via database links in the result cache because it cannot track DDL or DML changes on remote databases for reliable cache invalidation.