Cloud Digital Leader Trust and security with Google Cloud Practice Question
A company runs a multi-tenant SaaS application on Google Cloud where each customer's data must be strictly isolated from other customers'. A security architect is evaluating approaches: (A) logical isolation using application-level tenant IDs in a shared database, (B) IAM-based separation using separate service accounts per tenant, or (C) infrastructure-level isolation with separate Google Cloud projects per tenant. Which approach provides the strongest isolation guarantee?
⚠ Common exam trap
The GCDL exam often tests the misconception that logical isolation (e.g., tenant IDs) or IAM alone is sufficient for multi-tenant data separation, when in reality only infrastructure-level isolation (separate projects) provides the strongest guarantee against cross-tenant data breaches in a shared cloud environment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Separate Google Cloud projects per tenant, which provides the strongest isolation: separate IAM boundaries, separate resource namespaces, separate audit logs, and no shared database instances with other tenants
Separate Google Cloud projects provide the strongest isolation guarantee by creating independent IAM boundaries, resource namespaces, audit logs, and network configurations. This approach ensures that no shared database instances or other resources exist between tenants, eliminating any risk of cross-tenant data leakage through application bugs or misconfigurations. In contrast, logical isolation (A) relies on application-level tenant IDs which can be bypassed by software vulnerabilities, and IAM-based separation (C) still shares the underlying project infrastructure, including the same database and network.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Logical isolation using application-level tenant IDs, because it is the most cost-efficient and sufficient for regulated workloads
Why it's wrong here
Logical isolation using tenant IDs in shared infrastructure is the weakest form of isolation. A single application bug (SQL injection, missing WHERE clause on tenant_id, improper cache key) can expose cross-tenant data. It is also not typically accepted as sufficient isolation for highly regulated data (healthcare, financial).
- ✓
Separate Google Cloud projects per tenant, which provides the strongest isolation: separate IAM boundaries, separate resource namespaces, separate audit logs, and no shared database instances with other tenants
Why this is correct
Project-level isolation is the gold standard for multi-tenant isolation. Each project is a completely independent security boundary. Separate IAM means no privilege escalation between tenants. Separate databases mean no shared infrastructure where bugs could leak data. Separate audit logs make compliance reporting per-tenant straightforward.
- ✗
IAM-based separation using separate service accounts per tenant within a shared project, because IAM provides cryptographically enforced access control
Why it's wrong here
IAM-based separation within a shared project is stronger than application-level tenant IDs but weaker than project-level isolation. Service accounts in the same project share the same VPC, same database instance, and same resource namespace. IAM controls management-plane access but doesn't isolate data-plane access between resources in the same project.
- ✗
All three approaches provide equivalent isolation because Google Cloud's hypervisor ensures complete tenant separation at the hardware level
Why it's wrong here
This is incorrect because the hypervisor isolates between virtual machines, not between tenants that share the same VM, managed database instance, or application process. In common GCP multi-tenant deployments, tenants do not each get their own VM; they share the same Cloud Run service, GKE pod, or Cloud SQL database. The three approaches place the isolation boundary at different layers—hardware/infrastructure (project), IAM/resource management (shared project), and pure application logic (tenant IDs)—so their effective security guarantees are fundamentally different.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Project
A project is a temporary endeavor with a defined beginning and end, undertaken to create a unique product, service, or result, managed through specific processes in IT environments.
Key term
IAM
Identity and Access Management (IAM) is a framework of policies and technologies that ensures the right individuals have the appropriate access to technology resources.
About these practice questions
This GCDL question is part of Courseiva's 829-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.