Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your enterprise has acquired a subsidiary operating under a separate Google Cloud organization. Workloads running in Project A (within Organization A) require private access to Cloud Storage buckets hosted in Project B (within Organization B).
Both organizations enforce strict data exfiltration defenses using VPC Service Controls perimeters around their respective projects. You must establish private, policy-governed communication between these disparate organizations without compromising perimeter boundaries.
What should you do?
VPC Service Controls ingress and egress rules provide secure, bidirectional data exchange pathways across distinct service perimeters and separate Google Cloud organizations without dismantling existing security perimeters.

Because a service perimeter cannot span across multiple Google Cloud organizations, configuring directional ingress and egress rules is the standard, secure mechanism to enable authorized cross-organization data exchange while preventing unauthorized data exfiltration.
Shared VPC allows an organization to connect resources from multiple projects to a common Virtual Private Cloud (VPC) network, enabling secure and private communication using internal IP addresses.
The workload required private L3/L4 IP connectivity between VMs in multiple projects belonging to the same parent organization.
When using Shared VPC inside a perimeter within one organization, both host and service projects must be explicitly added to the perimeter to avoid communication failures.
VPC Network Peering enables direct, private connectivity between two VPC networks using RFC 1918 addresses across projects or organizations without using external IP addresses or VPN gateways.
The requirement was to connect two private VM subnets directly across projects without using API-level perimeter protection.
To route Google API traffic privately within a VPC, organizations use Private Google Access or Private Service Connect, but access to perimeter-secured services is ultimately governed by VPC Service Controls ingress and egress rules.
Adding projects directly to a single service perimeter allows all resources within those member projects to communicate freely without triggering perimeter-level boundary violations.
RESOURCES_NOT_IN_SAME_SERVICE_PERIMETER error.Both Project A and Project B resided within the exact same Google Cloud organization and folder hierarchy, allowing a unified perimeter to envelop both projects.
Identity and Access Management (IAM) controls who has permission, but VPC Service Controls provides network and perimeter boundaries. Both layers must permit an operation for cross-project access to succeed.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated