- A
A RoleBinding in namespace 'tenant-alpha' that binds the ClusterRole to the DevOps team.
This binds the ClusterRole to the DevOps team in the specific namespace.
- B
A ClusterRole that grants permissions to manage secrets across all namespaces.
Why wrong: This would grant secret access across all namespaces, which is too broad.
- C
A RoleBinding in namespace 'tenant-alpha' that binds a Role granting secret modification to the DevOps team.
Why wrong: This would grant secret access, which is not desired.
- D
A ClusterRole that grants permissions to manage deployments, services, and ingresses across all namespaces, but does not include secrets.
This ClusterRole provides the necessary permissions except secrets.
- E
A Role in namespace 'tenant-alpha' that grants permissions to modify secrets, bound to a separate group of tenant administrators.
This allows tenant admins to manage secrets, not the DevOps team.
Quick Answer
The answer is to create a ClusterRole that grants deployment permissions but explicitly excludes secrets, a RoleBinding in the 'tenant-alpha' namespace binding that ClusterRole to the DevOps team, and a separate Role in 'tenant-alpha' granting secret modification permissions bound to tenant administrators. This works because a ClusterRole is a cluster-scoped resource, but when bound via a RoleBinding, its permissions apply only within that specific namespace, allowing you to selectively deny secret access in 'tenant-alpha' while a ClusterRoleBinding grants the same ClusterRole across all other namespaces. On the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of how Kubernetes RBAC for multi-tenant GKE namespaces combines RoleBindings and ClusterRoles to enforce namespace-level restrictions—a common trap is assuming a ClusterRoleBinding is always needed for cluster-scoped resources. Remember the key distinction: RoleBindings scope ClusterRoles to a namespace, while ClusterRoleBindings apply cluster-wide. Memory tip: "Bind the Role, not the Cluster" to recall that namespace-scoped bindings override cluster-wide permissions.
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. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 security team is designing access controls for a multi-tenant SaaS application on Google Kubernetes Engine (GKE). Each tenant has a separate namespace. They want to ensure that a DevOps team can manage deployments across all namespaces, but cannot modify secrets in the 'tenant-alpha' namespace. Which THREE Kubernetes RBAC resources should be created? (Choose THREE)
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
A RoleBinding in namespace 'tenant-alpha' that binds the ClusterRole to the DevOps team.
Option A is correct because a RoleBinding in the 'tenant-alpha' namespace can bind a ClusterRole (which is a cluster-scoped resource) to the DevOps team, granting them the permissions defined in that ClusterRole within that specific namespace. Since the ClusterRole in option D explicitly excludes secrets, this RoleBinding ensures the DevOps team can manage deployments across all namespaces (via a ClusterRoleBinding) but cannot modify secrets in 'tenant-alpha'.
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.
- ✓
A RoleBinding in namespace 'tenant-alpha' that binds the ClusterRole to the DevOps team.
Why this is correct
This binds the ClusterRole to the DevOps team in the specific namespace.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A ClusterRole that grants permissions to manage secrets across all namespaces.
Why it's wrong here
This would grant secret access across all namespaces, which is too broad.
- ✗
A RoleBinding in namespace 'tenant-alpha' that binds a Role granting secret modification to the DevOps team.
Why it's wrong here
This would grant secret access, which is not desired.
- ✓
A ClusterRole that grants permissions to manage deployments, services, and ingresses across all namespaces, but does not include secrets.
Why this is correct
This ClusterRole provides the necessary permissions except secrets.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
A Role in namespace 'tenant-alpha' that grants permissions to modify secrets, bound to a separate group of tenant administrators.
Why this is correct
This allows tenant admins to manage secrets, not the DevOps team.
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 RoleBindings and ClusterRoleBindings, and the trap here is that candidates may think a ClusterRole can only be bound via a ClusterRoleBinding, but a RoleBinding can bind a ClusterRole to grant its permissions within a single namespace.
Detailed technical explanation
How to think about this question
In Kubernetes RBAC, a ClusterRole can be bound to subjects in a specific namespace via a RoleBinding, which scopes the permissions to that namespace only. This allows reuse of a single ClusterRole (e.g., one that grants deployment management but excludes secrets) across multiple namespaces without creating duplicate Role objects. The 'resources' and 'verbs' fields in a ClusterRole are defined using the RBAC API (v1), and the absence of 'secrets' in the resources list ensures no secret-related operations are permitted, even if the ClusterRole is bound via a RoleBinding.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
- →
Configuring access within a cloud solution environment — study guide chapter
Learn the concepts, then practise the questions
- →
Configuring access within a cloud solution environment practice questions
Targeted practice on this topic area only
- →
All PCSE questions
500 questions across all exam domains
- →
Google Professional Cloud Security Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCSE practice test guide
How to use practice tests most effectively before exam day
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.
Configuring network security practice questions
Practise PCSE questions linked to Configuring network security.
Configuring access within a cloud solution environment practice questions
Practise PCSE questions linked to Configuring access within a cloud solution environment.
Ensuring data protection practice questions
Practise PCSE questions linked to Ensuring data protection.
Managing operations in a cloud solution environment practice questions
Practise PCSE questions linked to Managing operations in a cloud solution environment.
Supporting compliance requirements practice questions
Practise PCSE questions linked to Supporting compliance requirements.
PCSE fundamentals practice questions
Practise PCSE questions linked to PCSE fundamentals.
PCSE scenario practice questions
Practise PCSE questions linked to PCSE scenario.
PCSE troubleshooting practice questions
Practise PCSE questions linked to PCSE troubleshooting.
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: A RoleBinding in namespace 'tenant-alpha' that binds the ClusterRole to the DevOps team. — Option A is correct because a RoleBinding in the 'tenant-alpha' namespace can bind a ClusterRole (which is a cluster-scoped resource) to the DevOps team, granting them the permissions defined in that ClusterRole within that specific namespace. Since the ClusterRole in option D explicitly excludes secrets, this RoleBinding ensures the DevOps team can manage deployments across all namespaces (via a ClusterRoleBinding) but cannot modify secrets in 'tenant-alpha'.
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 →
Keep practising
More PCSE practice questions
- Match each IAM role to its typical use case.
- Match each encryption scope to its description.
- Match each CVE or security concept to its description.
- Match each Google Cloud logging/monitoring term to its definition.
- Drag and drop the steps to rotate a customer-managed encryption key (CMEK) in Cloud KMS in the correct order.
- Drag and drop the steps to configure a Cloud NAT for private VM instances in the correct order.
Last reviewed: Jun 30, 2026
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.
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.
Sign in to join the discussion.