A Presto query filters on WHERE event_date = '2025-01-15' on an Iceberg table partitioned by event_date. What performance optimization occurs?

Partition pruning allows Presto to skip file listing and reading for all partitions that don't match the filter predicate; for a date-partitioned table; only the matching date partition's files are scanned. The incorrect options ("Presto reads all partitions in parallel and filters results client-side", "Presto converts the filter to a full-table scan to ensure no rows are missed", "Presto rewrites the query to use a BETWEEN clause for better index usage") are distractors that don't fully capture the concept described.