BigQuery dataset must be highly available with an RPO of 30 days while minimizing cost. How should you configure storage, backup, and recovery?

The correct answer leverages BigQuery's built-in features for high availability and recovery. Setting the dataset to multi-regional ensures high availability and disaster recovery across multiple geographic locations, which is crucial for minimizing downtime. BigQuery automatically maintains a 7-day history for point-in-time recovery, but for an RPO of 30 days, you can extend this using BigQuery's time travel feature, which allows querying data up to 30 days in the past. This approach is cost-effective because it uses BigQuery's native capabilities without requiring manual data copying or external storage, which would incur additional costs and management overhead. Incorrect options: Regional datasets do not provide the same level of availability and disaster recovery as multi-regional datasets. Creating scheduled queries to copy data is a manual and less efficient way to achieve recovery compared to BigQuery's built-in time travel, and it incurs additional storage costs for the copies.