An enterprise organization is designing a multi-tier e-commerce system on Google Cloud and translating conceptual business requirements into logical and physical architecture components.
The conceptual architecture specifies four primary requirements:
1. A stateless HTTP API ingress layer to accept lightweight order payloads with minimal operational management overhead.
2. A relational data tier storing order transactions restricted strictly to a single GCP region with cost-effective, standard relational database capacity.
3. A hybrid network topology capable of delivering 10 Gbps predictable, low-latency bandwidth between on-premises systems and GCP VPCs.
4. A data security boundary that prevents authorized internal users from exfiltrating sensitive storage data to external, unauthorized Google Cloud projects.
Which TWO physical architecture decisions correctly implement these requirements while avoiding architectural anti-patterns? (Select TWO)
- Deploy Cloud Run for the stateless HTTP API ingress tier, and implement Cloud SQL for the regional transactional relational database tier.Cevap
- Establish a Dedicated Interconnect connection for hybrid connectivity, and configure VPC Service Controls perimeters around Google Cloud Storage resources.Cevap
- CProvision an Autopilot Google Kubernetes Engine (GKE) cluster to host the stateless HTTP API ingress services.
- DDeploy a multi-region Cloud Spanner instance to host the single-region transactional order database.
- EDeploy High Availability (HA) VPN tunnels with dynamic Cloud Router routing to fulfill the 10 Gbps hybrid network throughput requirement.