Expand a Cloud Run payment service to Jakarta, Hong Kong, and Taiwan while meeting per-country data residency and minimizing cost. What should you do?

The correct option addresses both data residency and expansion requirements. Creating a Cloud Storage bucket in each region (Jakarta, Hong Kong, Taiwan) ensures that data for each country resides within its specified geographic boundaries, fulfilling data residency mandates. Deploying a Cloud Run service of the payment application in each of these regions allows the application to process payments locally, minimizing latency and providing a localized endpoint for users in each country. This approach also helps optimize costs by deploying resources only where needed. The incorrect options fail on data residency or efficient deployment. Deploying all Cloud Run services in Singapore would violate data residency for Jakarta, Hong Kong, and Taiwan. Using multi-region Cloud Storage buckets would not guarantee data residency within a specific country. Cloud Run revisions are for versioning within a single service, not for deploying separate instances across different regions.