1. YOU query VSSYSTEM_EVENTS and filter for the event 'cell physical IO interconnect bytes returned by smart scan', associated to your table. This does not show how much data was filtered by Smart Scan, but only how much data was returned after Smart Scan12.
2. You query v$SYSTAT and filter for the statistic 'cell smart table scan', associated to your table. This does not show how much data was filtered by Smart Scan for a specific table, but only for all tables in a session12.
https://www.databasejournal.com/oracle/monitoring-smart-scans-in-oracle-exadata/

The statements that are true about the CellCLI command are:
It has command-line history . According to 1, you can use the up and down arrow keys to scroll through previous commands that you entered in CellCLI . You can also use Ctrl+R to search for a previous command by entering part of it .
It can be executed on storage servers . According to 1, you can invoke CellCLI by logging in to the Exadata cell as cellmonitor , celladmin , or root user and typing "cellcli" . Within CellCLI , you can perform various management and monitoring tasks for the cell134.
It can be executed using the DCLI utility . According to 5, DCLI (distributed CLI) is another utility that can be used to execute scripts and commands across multiple storage cells from a single interface. You can use DCLI to run CellCLI commands on multiple cells at once54.

In order to monitor all components of this multirack configuration, Enterprise Manager agents must be deployed on at least two storage servers in both racks and all database servers in both racks. This is according to the Oracle Exadata Database Machine X9M Implementation Essentials official text book [1], in which it states "To monitor all components of the multirack configuration, you must deploy agents on all database servers and at least two storage servers in each rack" (page 6-15).

According to 1, Exadata X9M-2 Database Servers are based on Intel Xeon Platinum 8368Y processors with 32 cores and 768 GB of DRAM memory per server. This memory can be expanded up to 1.5 TB per server by adding 24 x 32 GB DIMMs. The DRAM memory is used for buffer cache, PGA, and other database purposes1. Exadata X9M-2 Database Servers also have 25.6 TB of Persistent Memory Acceleration (PMEM) per server, which is used for log writes and columnar data caching1. PMEM is a new type of memory that combines the speed of DRAM with the persistence of flash2. Exadata X9M-2 Database Servers are designed to run Oracle Database workloads with high performance, scalability, and reliability2

[1] Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book [1][2], Chapter 4: Oracle Clusterware [2] Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book [1][2], Chapter 8: Oracle Exadata Storage Server Software [3] Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book [1][2], Chapter 9: Oracle Exadata Storage Server Infrastructure
https://www.oracle.com/technetwork/database/availability/exadata-backup-recovery-bp-3633870.pdf