How to Securely Isolate an Externally-Facing App in Google Cloud?
You manage multiple internal-only applications that are hosted within different Google Cloud projects. You are deploying a new application that requires external internet access. To maintain security, you want to clearly separate this new application from internal systems. Your solution must have effective security isolation for the new externally-facing application. What should you do?
Community Votes
62% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests workload isolation strategies; the common trap is confusing VPC Service Controls (data exfiltration guardrails) with project-level architectural boundaries.
This question tests how to achieve strong administrative and network isolation for a new public-facing workload in Google Cloud. The page establishes that provisioning a dedicated project combined with VPC peering provides the clearest security boundary.
Candidates often select VPC Service Controls (C) assuming perimeter services handle all isolation, but they only restrict data flow to authorized networks rather than providing administrative or network segmentation.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Creating a new project establishes a distinct administrative boundary, which is Google Cloud’s foundational method for isolating workloads and applying least-privilege IAM policies. Using VPC Network Peering then enables controlled, secure connectivity to internal resources without merging network spaces or sharing project configurations. This architecture directly satisfies the requirement for clear separation and effective security isolation.Why the Other Options Are Wrong
Options A and B retain the workload in an existing project, which violates the explicit requirement for clear separation and increases lateral movement risks. Option C misapplies VPC Service Controls, which are designed to prevent data exfiltration across service perimeters rather than isolate externally-facing compute from internal network segments.Community Comment Notes
As one contributor observed, "keeping the workload in the same project creates unnecessary exposure", reinforcing that shared environments undermine isolation goals. Several learners confirmed that VPC-SC focuses on API/data protection rather than network segregation, while others emphasized that a dedicated project inherently reduces unauthorized access risk while peering maintains necessary but bounded connectivity.Official Reference
Exam Strategy
Always prioritize Google Cloud projects as your first-line security and administrative boundary when questions emphasize workload separation or least privilege. Reserve VPC Service Controls for data loss prevention scenarios rather than general network or project isolation.
Frequently Asked Questions
Why is VPC Service Controls incorrect for network isolation?
VPC-SC enforces data exfiltration guardrails at the service perimeter level but does not segment networks or replace project boundaries for workload isolation.
Does VPC peering violate security isolation requirements?
No, peering creates a private, non-routable link between VPCs without merging CIDR blocks or granting broad project-level access, maintaining strict boundaries.