An automotive IoT enterprise ingests streaming vehicle telemetry into Cloud Storage buckets located inside Project-Ingest. An analytics team operating out of Project-Analytics requires direct read access to this telemetry to run BigQuery Omni and Dataproc jobs. The chief information security officer (CISO) mandates that raw telemetry data must be strictly prevented from being exfiltrated to external Google Cloud resources or public internet destinations, even by identities holding legitimate read permissions. Additionally, Project-Analytics is connected via VPC Network Peering to a shared Project-Management network, but Project-Ingest has no direct VPC Network Peering connection to Project-Management. Which security architecture should a Cloud Architect implement to satisfy these security and operational requirements?
- Configure a single VPC Service Controls perimeter that includes both Project-Ingest and Project-Analytics, restricting Google Cloud Storage and BigQuery API traffic to the restricted.googleapis.com IP range.Cevap
- BGrant fine-grained IAM Storage Object Viewer roles to the analytics team's service account without establishing a VPC Service Controls perimeter.
- CRoute all API requests from Project-Ingest through Project-Analytics to reach Project-Management by relying on the transitive properties of the existing VPC Network Peering connection.
- DAssign the primitive Editor IAM role to the analytics service account across Project-Ingest and Project-Analytics to enable automatic cross-project API access.