What is the primary design goal of the Presto distributed SQL query engine?

Presto (and its Trino fork) is designed for interactive; low-latency SQL analytics across heterogeneous data sources without requiring data movement; making it ideal for ad-hoc and BI query workloads. The incorrect options ("To replace Hadoop MapReduce for batch ETL processing", "To manage schema definitions and table metadata for the entire lakehouse", "To provide machine learning model training pipelines on structured data") are distractors that don't fully capture the concept described.