← GCDL·Google Cloud

Question 383 of 507

Trust and security with Google Cloud →hardMultiple ChoiceObjective-mapped

Quick Answer

The answer is separate Google Cloud projects per tenant, which provides the strongest tenant isolation in a multi-tenant SaaS environment. This approach guarantees infrastructure-level isolation by creating independent IAM boundaries, separate resource namespaces, distinct audit logs, and no shared database instances, eliminating any risk of cross-tenant data leakage through application bugs or misconfigurations. On the Google Cloud Digital Leader exam, this question tests your understanding that logical isolation via tenant IDs or IAM-based separation still shares underlying project infrastructure, making them vulnerable to software flaws. A common trap is assuming IAM alone suffices, but remember: IAM controls access, not infrastructure boundaries. For the strongest isolation guarantee, think "project per tenant" — it’s the only option that physically separates compute, storage, and networking. Memory tip: "Project walls are concrete; IAM walls are paper."

Cloud Digital Leader Trust and security with Google Cloud Practice Question

This GCDL practice question tests your understanding of trust and security with google cloud. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

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?

Question 1hardmultiple choice

Full question →

A
Logical isolation using application-level tenant IDs, because it is the most cost-efficient and sufficient for regulated workloads
Why wrong: 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).
B
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
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.
C
IAM-based separation using separate service accounts per tenant within a shared project, because IAM provides cryptographically enforced access control
Why wrong: 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.
D
All three approaches provide equivalent isolation because Google Cloud's hypervisor ensures complete tenant separation at the hardware level
Why wrong: Hypervisor isolation protects between VMs, not between tenants sharing the same VM or same database. Application-level logical isolation provides no protection from application bugs. The three approaches have fundamentally different isolation strengths.

Full breakdown with real-world context →

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

Option B is correct because 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.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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.
Related concept
Read the scenario before looking for a memorised answer.
✗
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
Hypervisor isolation protects between VMs, not between tenants sharing the same VM or same database. Application-level logical isolation provides no protection from application bugs. The three approaches have fundamentally different isolation strengths.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco 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.

Detailed technical explanation

How to think about this question

Under the hood, Google Cloud projects act as trust boundaries with separate resource hierarchies, IAM policies, and VPC networks, allowing fine-grained network segmentation via VPC Service Controls and Private Google Access. For example, in a real-world scenario, a healthcare SaaS provider handling PHI would use separate projects per customer to meet HIPAA requirements, ensuring that audit logs from one tenant cannot be accessed by another and that data encryption keys (via CMEK) are unique per project. This approach also enables per-tenant VPC peering and firewall rules, preventing lateral movement even if a tenant's application is compromised.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related GCDL practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Why cloud technology is transforming business practice questions

Practise GCDL questions linked to Why cloud technology is transforming business.

Fundamental cloud concepts practice questions

Practise GCDL questions linked to Fundamental cloud concepts.

Google Cloud products, services, and solutions practice questions

Practise GCDL questions linked to Google Cloud products, services, and solutions.

Scaling with Google Cloud operations practice questions

Practise GCDL questions linked to Scaling with Google Cloud operations.

Trust and security with Google Cloud practice questions

Practise GCDL questions linked to Trust and security with Google Cloud.

GCDL fundamentals practice questions

Practise GCDL questions linked to GCDL fundamentals.

GCDL scenario practice questions

Practise GCDL questions linked to GCDL scenario.

GCDL troubleshooting practice questions

Practise GCDL questions linked to GCDL troubleshooting.

Practice this exam

Start a free GCDL practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

GCDL practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this GCDL question test?

Trust and security with Google Cloud — This question tests Trust and security with Google Cloud — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: 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 — Option B is correct because 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.

What should I do if I get this GCDL question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

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.