An international logistics enterprise is establishing design standards to translate its logical architecture into a physical GCP architecture. The logical design specifies three core requirements: a stateless HTTP API ingestion tier with minimal operational complexity, a relational database tier requiring multi-region synchronous write consistency, and a network security boundary that prevents authorized users from exfiltrating data to external public storage. Which physical architecture mapping correctly aligns GCP services to these logical requirements?
- Deploy the stateless API tier on Cloud Run, use Cloud Spanner for the relational persistence layer across multiple regions, and enclose the cloud resources within a VPC Service Controls security perimeter.Answer
- BDeploy the stateless API tier on a multi-zonal Google Kubernetes Engine (GKE) cluster, use Cloud Spanner for the multi-region relational database, and enclose the cloud resources within a VPC Service Controls security perimeter.
- CDeploy the stateless API tier on Cloud Run, use Cloud Spanner for the multi-region relational database, and rely exclusively on fine-grained IAM custom roles to prevent internal users from copying sensitive data externally.
- DDeploy the stateless API tier on Cloud Run, provision Cloud SQL for PostgreSQL with cross-region read replicas for the database layer, and enclose the cloud resources within a VPC Service Controls security perimeter.
Answer
The physical architecture mapping that uses Cloud Run for the stateless API tier, Cloud Spanner for multi-region relational persistence, and VPC Service Controls for perimeter isolation correctly fulfills the logical requirements.
The solution using Cloud Run, Cloud Spanner, and VPC Service Controls accurately translates all logical requirements into physical GCP architecture. Cloud Run provides serverless compute with zero cluster management; Cloud Spanner supports multi-region synchronous relational transactions; and VPC Service Controls establishes network perimeters to prevent data exfiltration beyond IAM controls.
Step-by-Step Solution
Key Concept
Translating Logical Architecture Requirements into Physical GCP Resource Selection
Estimated Time:2m 0s