Skip to content

Designing so data and workloads can move across clouds or regions

Designing for portability means choosing architectures and services that let workloads and data move across clouds or comply with regional residency laws without major re-engineering. Google Cloud supports this through open-source-based managed services, containerization, and multi-cloud data analytics tools.

1 · Learn the must-know

  • BigQuery Omni lets you run BigQuery analytics on data stored in AWS S3 or Azure Blob Storage without moving the data, addressing multi-cloud and residency needs.
  • GKE and Anthos (Google Distributed Cloud) enable running containerized workloads consistently across on-premises, Google Cloud, AWS, and Azure, avoiding vendor lock-in.
  • Dataproc and Dataflow are built on open-source (Apache Hadoop/Spark, Apache Beam) so pipelines can be ported to other environments running the same open-source frameworks.
  • Data residency requirements can be met using organization policies to restrict resource locations, regional (not multi-regional) storage buckets/datasets, and Assured Workloads for regulated industries.
  • Using open formats (Parquet, Avro) and open APIs (rather than proprietary formats) reduces lock-in risk and simplifies migration between clouds.
  • For data residency, storing data in a specific region does not automatically prevent processing outside it, compute location and network egress must also be explicitly controlled via org policies and VPC Service Controls.

2 · Check your understanding

Check this objectiveFree · always available

A retailer headquartered in Germany must guarantee that all newly provisioned Cloud Storage buckets, Compute Engine VMs, and BigQuery datasets are created only in EU regions, across every project in its Google Cloud organization, to satisfy a data residency requirement. Which control should the cloud architect configure at the organization level?

Your objective map0 tried · 0 answered correctly · 67 untouched

What you have tried across GCP PDE's objectives, not a readiness score.

Designing data processing systems~22% of the exam0 of 17 tried
Ingesting and processing the data~25% of the exam0 of 11 tried
Storing the data~20% of the exam0 of 13 tried
Preparing and using data for analysis~15% of the exam0 of 11 tried
Maintaining and automating data workloads~18% of the exam0 of 15 tried

3 · Keep going