- A
Use a deny policy at the project level to deny the 'iam.serviceAccountKeys.create' permission.
Why wrong: Deny policies can deny permissions, but applying at each project separately is less efficient than a single organization policy at the folder level.
- B
Configure a script that runs daily to delete any service account keys found in projects.
Why wrong: This is reactive, not preventive. It does not prevent key creation and can lead to gaps.
- C
Create a custom IAM role that denies the permission to create keys and assign it to all users.
Why wrong: IAM roles grant or deny permissions, but managing this at scale across users is inefficient and error-prone. Organization policy is the correct tool.
- D
Apply an organization policy with the constraint 'constraints/iam.disableServiceAccountKeyCreation' at the folder level.
Organization policies enforce restrictions across the resource hierarchy. This constraint disables key creation for all service accounts in the folder's projects.
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. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 has multiple GCP projects managed through folders in the resource hierarchy. They want to enforce a policy that prohibits the creation of service account keys across all projects. Which approach should be used?
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
Apply an organization policy with the constraint 'constraints/iam.disableServiceAccountKeyCreation' at the folder level.
Organization policies can be applied at the folder or organization level to enforce constraints across all projects. The constraint 'constraints/iam.disableServiceAccountKeyCreation' specifically disables service account key creation. Applying it at a folder level is the most efficient way to enforce the policy across all projects in that folder.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a deny policy at the project level to deny the 'iam.serviceAccountKeys.create' permission.
Why it's wrong here
Deny policies can deny permissions, but applying at each project separately is less efficient than a single organization policy at the folder level.
- ✗
Configure a script that runs daily to delete any service account keys found in projects.
Why it's wrong here
This is reactive, not preventive. It does not prevent key creation and can lead to gaps.
- ✗
Create a custom IAM role that denies the permission to create keys and assign it to all users.
Why it's wrong here
IAM roles grant or deny permissions, but managing this at scale across users is inefficient and error-prone. Organization policy is the correct tool.
- ✓
Apply an organization policy with the constraint 'constraints/iam.disableServiceAccountKeyCreation' at the folder level.
Why this is correct
Organization policies enforce restrictions across the resource hierarchy. This constraint disables key creation for all service accounts in the folder's projects.
Related concept
Standard ACLs match source addresses.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
- Standard ACLs match source addresses.
- Extended ACLs can match source, destination, protocol and ports.
- The first matching ACL entry is used.
- There is usually an implicit deny at the end.
TExam Day Tips
- Check inbound versus outbound direction.
- Read the ACL from top to bottom.
- Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
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.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related PCSE ACL questions on filtering logic and placement.
- →
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
1,000 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 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.
Configuring Network Security practice questions
Practise PCSE questions linked to Configuring Network Security.
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 — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Apply an organization policy with the constraint 'constraints/iam.disableServiceAccountKeyCreation' at the folder level. — Organization policies can be applied at the folder or organization level to enforce constraints across all projects. The constraint 'constraints/iam.disableServiceAccountKeyCreation' specifically disables service account key creation. Applying it at a folder level is the most efficient way to enforce the policy across all projects in that folder.
What should I do if I get this PCSE question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related PCSE ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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 encryption scope to its description.
- Drag and drop the steps to set up a Private Google Access for on-premises hosts using Private Service Connect in the cor…
- A company is designing a CI/CD pipeline using Cloud Build. Security requirements mandate that the pipeline deploy only t…
- A company must implement data residency requirements that prohibit storing data outside the European Union. They are usi…
- A company wants to allow employees to access a web application running on Google Kubernetes Engine (GKE) using their cor…
- A security engineer is investigating an incident where an attacker gained access to a Compute Engine instance's serial c…
Last reviewed: Jul 4, 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.