Which options does not benefit from storage offload processing?
A.
indexes that rely on B-Tree pointers
B.
column filtering
C.
joins and aggregation
D.
table scans
E.
incremental backups with block change tracking
Explanation:
https://www.pythian.com/blog/exadata-join-offloading-in-action/
Wrong. The right answer is E.
Not sure between A and E. The link pointed says:
Offloading is applicable only to full table scans and fast index scans. Index access paths that rely on following B-TREE pointers (RANGE SCAN, FULL SCAN) use block access, thus do not benefit in any way from storage offloading.
Exadata Storage Server offload capability combined with RMAN block change tracking will
efficiently perform large I/Os at the storage-tier level, returning only individual changed
blocks for incremental backups and increasing the backup performance of the system.
http://www.oracle.com/technetwork/database/availability/maa-tech-wp-sundbm-backup-11202-183503.pdf
Then A?
A –
https://blog.pythian.com/exadata-join-offloading-in-action/