Which of the following statement(s) is (are) true?
-
a. COMPRESS FOR QUERY HIGH should be used where load performance is critical
-
b. COMPRESS FOR QUERY LOW should be used where load performance is critical
-
c. COMPRESS FOR ARCHIVE HIGH should be used for rarely accessed application
-
d. COMPRESS FOR ARCHIVE HIGH should be used for heavily accessed application
COMPRESS FOR QUERY LOW is designed for load performance, using lower compression overhead for faster data loading while still providing query performance benefits. COMPRESS FOR QUERY HIGH provides better compression but slower load times. COMPRESS FOR ARCHIVE HIGH is for rarely accessed data requiring maximum compression, not for frequently accessed applications. Archive compression levels add significant overhead during data loading and modification, making them unsuitable for active workloads.
Oracle's Advanced Compression offers tiers trading compression ratio for CPU/load overhead. COMPRESS FOR QUERY LOW uses a lighter compression algorithm with minimal load-time CPU cost, so it's appropriate where load performance matters (frequent bulk loads) — correct. COMPRESS FOR ARCHIVE HIGH achieves the highest compression ratio but at high CPU cost during compression, making it suitable only for rarely-accessed, cold archival data — correct. Conversely, COMPRESS FOR QUERY HIGH is not ideal where load performance is critical since it costs more CPU to compress at load time (wrong to pick for that use case), and COMPRESS FOR ARCHIVE HIGH is unsuitable for heavily-accessed data because decompression overhead on frequent reads would hurt query performance. The marked answers correctly match compression tier to workload pattern.