A digital media enterprise is architecting an event ingestion microservice on Google Cloud to handle HTTP webhooks triggered by external partners. The workload is stateless, highly bursty, and experiences prolonged idle periods. The architecture must automatically scale to zero during periods of inactivity to eliminate baseline compute costs, sustain high availability across zonal failures, and enforce strict security boundaries that prevent compromised internal service accounts from copying sensitive data to external Cloud Storage buckets outside the enterprise environment. Which architectural strategy best satisfies these technical, availability, and security requirements?
- Deploy the microservice on Cloud Run fully managed, connect it to a Virtual Private Cloud (VPC) network using a Serverless VPC Access connector, and enclose the project resources within a VPC Service Controls perimeter.Cevap
- BDeploy the microservice on a multi-zonal Google Kubernetes Engine (GKE) cluster configured with Cluster Autoscaler and horizontal pod autoscaling, relying on IAM custom roles to restrict bucket destination permissions.
- CDeploy the microservice on Cloud Run fully managed with direct public egress, configuring IAM Least Privilege principles and Cloud KMS encryption on all storage buckets without perimeter security controls.
- DDeploy the microservice on Compute Engine virtual machines across multiple zones using an unpeered spoke VPC, relying on a central transit VPC peered to a target data VPC to route egress storage traffic transitively.
Cevap
Deploying the stateless microservice on Cloud Run attached to the VPC via Serverless VPC Access inside a VPC Service Controls perimeter satisfies scale-to-zero operational efficiency, high availability, and exfiltration prevention.
Cloud Run satisfies the technical requirement for a stateless HTTP workload that must scale down to zero instances during idle periods while providing native regional high availability across zones. Pairing Cloud Run with Serverless VPC Access and placing resources inside a VPC Service Controls perimeter guarantees that internal services cannot exfiltrate data to external storage destinations, fulfilling all stated security and availability criteria.
Adım Adım Çözüm
Anahtar Kavram
Designing highly available serverless compute architectures paired with VPC Service Controls for exfiltration protection