**Why this matters**: Presto/Trino is an MPP query engine—designed for ad-hoc queries over *stored* data. **Native streaming**: No—Presto does not consume Kafka/Kinesis directly. **Near real-time options**: (1) Query frequently updated tables (e.g., Delta with 1-min micro-batches); (2) Kafka connector for *bounded* reads ( snapshot queries); (3) Materialized views refreshed on schedule. Latency = refresh interval + query time....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Walmart. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.