Question

A European financial services company is building a new customer-facing platform on Google Cloud. Under GDPR and their national banking regulator's rules, all personally identifiable customer data must remain physically stored within the European Union, and the company must be able to demonstrate this to auditors. The application also requires low-latency access for users concentrated in Germany and France. As the cloud architect, which design approach best satisfies these business and compliance requirements while minimizing latency?

Accepted Answer

Deploy compute and use Cloud Storage in EU regions (e.g., europe-west3, europe-west9) with regional or dual-region resource locations, and enable Organization Policy constraints to restrict resource creation to approved EU regions.

Answer

Use a multi-region bucket set to the 'us' location for durability, and encrypt all PII with customer-managed encryption keys stored in an EU-based Cloud KMS key ring.

Answer

Deploy all resources in a single global load-balanced footprint and rely on Cloud CDN edge caching in Europe to keep data close to users.

Answer

Store PII in Firestore in Native mode using the default 'nam5' multi-region location and apply IAM conditions to limit access to EU-based employees only.