Question 159 of 500

Quick Answer

The correct answer is to use Kubernetes RBAC with Role and RoleBinding objects to enforce namespace-level permissions, and to use Workload Identity to map tenant IAM roles to Kubernetes service accounts. This combination is essential because RBAC provides native, granular control over what actions a tenant can perform inside their assigned namespace—such as creating or listing pods—while Workload Identity securely bridges GCP IAM with Kubernetes, allowing tenant workloads to access Google Cloud resources without managing static keys. On the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of multi-tenant isolation on GKE using namespaces, RBAC, and Workload Identity as a layered defense, often appearing as a choose-two question where a common trap is selecting separate clusters or manual service account key management. Remember the memory tip: “Roles for inside, Identity for outside”—RBAC governs intra-cluster actions, Workload Identity governs cloud resource access.

PCSE Practice Question: Configuring access within a cloud solution environment

This PCSE practice question tests your understanding of configuring access within a cloud solution environment. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

An organization is designing a secure multi-tenant SaaS environment on GKE. They want to isolate tenant workloads using GKE namespaces and IAM. Which two steps should they take? (Choose two.)

Question 1hardmulti select
Full question →

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

Use Kubernetes RBAC to restrict access within namespaces.

Option C is correct because Kubernetes RBAC is the native mechanism for controlling access to resources within a namespace. By defining Role and RoleBinding objects, you can precisely restrict which tenant users can perform actions (e.g., get, list, create pods) inside their assigned namespace, ensuring logical isolation without requiring separate clusters.

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.

  • Enable GKE Dataplane V2 for network isolation.

    Why it's wrong here

    Network isolation is separate from IAM and RBAC.

  • Grant cluster-level IAM roles to tenant users.

    Why it's wrong here

    Too permissive; violates least privilege.

  • Use Kubernetes RBAC to restrict access within namespaces.

    Why this is correct

    RBAC provides granular namespace-level access control.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Create a separate GKE cluster per tenant.

    Why it's wrong here

    Too costly and complex; namespaces suffice.

  • Use Workload Identity to map tenant IAM roles to Kubernetes service accounts.

    Why this is correct

    This enables fine-grained GCP IAM integration.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the distinction between network isolation (Dataplane V2) and access control (RBAC/IAM), leading candidates to confuse traffic filtering with permission boundaries.

Detailed technical explanation

How to think about this question

Kubernetes RBAC uses Role and ClusterRole objects to define rules, and RoleBinding and ClusterRoleBinding to bind them to subjects (users, groups, service accounts). For multi-tenant isolation, you typically create a Role per namespace with minimal permissions (e.g., only to pods and services within that namespace) and bind it to a tenant-specific Google Group via IAM integration. Workload Identity (Option E) complements this by allowing tenant IAM roles to be mapped to Kubernetes service accounts, enabling fine-grained access to Google Cloud APIs without sharing cluster-level credentials.

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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

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 practice questions

Related PCSE practice-question pages

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

Practice this exam

Start a free PCSE practice session

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

FAQ

Questions learners often ask

What does this PCSE question test?

Configuring access within a cloud solution environment — This question tests Configuring access within a cloud solution environment — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use Kubernetes RBAC to restrict access within namespaces. — Option C is correct because Kubernetes RBAC is the native mechanism for controlling access to resources within a namespace. By defining Role and RoleBinding objects, you can precisely restrict which tenant users can perform actions (e.g., get, list, create pods) inside their assigned namespace, ensuring logical isolation without requiring separate clusters.

What should I do if I get this PCSE 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

Last reviewed: Jun 30, 2026

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…

Sign in to join the discussion.

This PCSE 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 PCSE exam.