Visualization queries on BigQuery use outer joins and analytic functions and may use data up to 4 hours stale. Users find queries slow. Improve query performance while minimizing pipeline maintenance. What do you do?

The correct option leverages BigQuery materialized views to pre-compute and store the results of complex queries, significantly improving performance for visualization tools. Setting maxstaleness=4 hours aligns with the acceptable data staleness, while enablerefresh=true ensures the view is automatically updated. allownonincrementaldefinition=true is crucial for queries with outer joins and analytic functions, as these often prevent incremental updates. Standard views (incorrect option) only store the query definition, not the results, so they don't improve performance. Exporting to Cloud Storage (incorrect option) introduces a separate data pipeline that requires maintenance and management, violating the "minimizing pipeline maintenance" constraint. Materialized views with incremental updates (incorrect option) are ideal but often not supported for queries involving outer joins or analytic functions, making allownonincrementaldefinition=true necessary here.