Your org stores data in GCS and AWS S3 in US regions. You want BigQuery users to query up-to-date data without giving direct access to the storage buckets. What should you do?

The correct option leverages BigQuery Omni for cross-cloud querying and BigLake tables for enhanced data management. BigQuery Omni allows BigQuery to query data directly in AWS S3 without moving it, addressing the requirement for up-to-date data and avoiding direct storage access. BigLake tables provide fine-grained access control and performance optimizations over both Cloud Storage and S3 data, making them ideal for managing and querying external data sources. The second option is incorrect because while BigQuery Omni is used, external tables lack the advanced features of BigLake tables, such as fine-grained access control and performance enhancements. The third and fourth options are incorrect because they involve using Storage Transfer Service to copy data from S3 to Cloud Storage. This introduces data staleness, as the data would not be "up-to-date" in BigQuery without continuous transfers, and it incurs additional storage and transfer costs, contrary to the goal of querying data in place.