What benefit does result set caching provide in watsonx.data query workloads?

Result set caching stores the output of expensive queries temporarily; when the same query is submitted again within the cache validity window; the cached result is returned immediately without re-executing against the data. The incorrect options ("It permanently stores query results as new Iceberg tables in object storage", "It compresses query results using Parquet encoding before transmission to clients", "It synchronizes query results between multiple Presto engines in the cluster") are distractors that don't fully capture the concept described.