- A
Users must use a VPN to be assigned a corporate IP, but some are not connected.
Why wrong: If they are not using corporate IP, they should be denied; this behavior is expected, not a cause of unexpected denial.
- B
The condition uses the attribute 'request.network' instead of 'source.ip'.
Why wrong: Both can be used, but the correct attribute is 'source.ip'; however, the issue is more fundamental.
- C
The bucket ACL is set to deny all access by default.
Why wrong: IAM conditions take precedence over ACLs; the issue is with the IAM condition, not ACL.
- D
The IAM condition evaluates after authentication, and users are already authenticated; the condition is not restricting based on source IP correctly because the condition is on the user's identity, not the request's source IP.
IAM conditions can restrict by source IP, but if misconfigured (e.g., using wrong attribute or not applying to the correct principal), they may not work; the most likely cause is that the condition is not properly written to check the source IP.
IAM Condition source.ip for Cloud Storage Access
This PCSE practice question tests your understanding of iam condition attributes. 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. A key principle to apply: iAM condition attributes. 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 needs to enforce that only requests originating from a corporate IP range (203.0.113.0/24) can access a Cloud Storage bucket containing sensitive data. They have created a custom IAM role with storage.objects.get permission and attached a condition that requires the request to have a specific IP address. However, some legitimate users outside the IP range are unable to access the data. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Quick Answer
The answer is that the IAM condition is likely misconfigured to evaluate the user's identity attributes rather than the request's source IP, because IAM conditions using the `source.ip` attribute are evaluated after authentication and apply to the request's originating IP, not the user's stored IP. When a condition is attached to a custom role, it filters access based on the network context of the API call itself, but if the condition inadvertently checks the user's identity (e.g., their last login IP), it fails to restrict the actual request source, allowing authenticated users from any IP while blocking legitimate users outside the corporate range. On the Google Professional Cloud Security Engineer exam, this tests your understanding that IAM conditions are request-level, not user-level—a common trap is confusing `source.ip` with a user attribute like `gcp.resource_location`. Remember the key distinction: IAM conditions evaluate the *request's* source IP at the moment of access, not the user's stored IP address. Memory tip: "Request, not requester" — the condition checks where the request comes from, not who the user is.
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
The IAM condition evaluates after authentication, and users are already authenticated; the condition is not restricting based on source IP correctly because the condition is on the user's identity, not the request's source IP.
Option D is correct because IAM conditions on a custom role binding are evaluated after the user is authenticated and are based on the user's identity attributes (such as the user's email or group membership). To restrict access based on the request's originating IP address, the condition must reference the attribute `request.source.ip`. If the condition instead checks an identity attribute (e.g., `resource.name` or `request.auth`), it will not enforce the IP restriction. As a result, legitimate users outside the corporate IP range are blocked because the condition evaluates something about their identity that they do not satisfy, rather than checking their IP address.
Key principle: IAM condition attributes
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Users must use a VPN to be assigned a corporate IP, but some are not connected.
Why it's wrong here
If they are not using corporate IP, they should be denied; this behavior is expected, not a cause of unexpected denial.
- ✗
The condition uses the attribute 'request.network' instead of 'source.ip'.
Why it's wrong here
Both can be used, but the correct attribute is 'source.ip'; however, the issue is more fundamental.
- ✗
The bucket ACL is set to deny all access by default.
Why it's wrong here
IAM conditions take precedence over ACLs; the issue is with the IAM condition, not ACL.
- ✓
The IAM condition evaluates after authentication, and users are already authenticated; the condition is not restricting based on source IP correctly because the condition is on the user's identity, not the request's source IP.
Why this is correct
IAM conditions can restrict by source IP, but if misconfigured (e.g., using wrong attribute or not applying to the correct principal), they may not work; the most likely cause is that the condition is not properly written to check the source IP.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
IAM condition attributes
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between IAM condition attributes for request (e.g., source.ip) and identity (e.g., user.ip). Candidates may overlook that using an identity attribute like user.ip does not enforce the request's originating IP, leading to incorrect access control.
Detailed technical explanation
How to think about this question
IAM conditions in Google Cloud use the Common Expression Language (CEL) to evaluate attributes like 'source.ip' at request time. The condition is applied to the principal's binding, meaning it filters access after the user is authenticated and authorized by IAM. If the condition uses an incorrect attribute (e.g., 'request.network' instead of 'source.ip'), the condition may not match any requests, effectively allowing all authenticated users or blocking all, depending on the logic. In real-world scenarios, misconfiguring IAM conditions is a common cause of unexpected access denials, especially when using custom roles with conditions that are not thoroughly tested.
KKey Concepts to Remember
- IAM condition attributes
- source.ip
- user.ip
- Condition evaluation after authentication
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
IAM condition attributes
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.
Review iAM condition attributes, then practise related PCSE questions on the same topic to reinforce the concept.
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?
IAM condition attributes
What is the correct answer to this question?
The correct answer is: The IAM condition evaluates after authentication, and users are already authenticated; the condition is not restricting based on source IP correctly because the condition is on the user's identity, not the request's source IP. — Option D is correct because IAM conditions on a custom role binding are evaluated after the user is authenticated and are based on the user's identity attributes (such as the user's email or group membership). To restrict access based on the request's originating IP address, the condition must reference the attribute `request.source.ip`. If the condition instead checks an identity attribute (e.g., `resource.name` or `request.auth`), it will not enforce the IP restriction. As a result, legitimate users outside the corporate IP range are blocked because the condition evaluates something about their identity that they do not satisfy, rather than checking their IP address.
What should I do if I get this PCSE question wrong?
Review iAM condition attributes, then practise related PCSE questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
IAM condition attributes
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 company is deploying a multi-tier application on Google Cloud. The web tier must be accessible from the internet, whil…
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.