- A
IAM conditions can restrict access based on the current date and time.
DateTime conditions are supported.
- B
IAM conditions are supported for all Google Cloud resources.
Why wrong: Conditions are not supported on all resources; e.g., Compute Engine has mixed support.
- C
IAM conditions can be applied to a role binding that supports all resources.
Why wrong: Conditions are not supported on roles that apply to all resources.
- D
IAM conditions can restrict access based on resource tags.
Resource tags can be used in conditions.
- E
IAM conditions can restrict access based on the user's email domain.
Why wrong: Conditions use attributes like resource tags, date/time, but not user principal directly.
Question 149 of 1,000
hardMultiple SelectObjective-mapped
IAM Conditions: Time and Resource Tags
This PCSE practice question tests your understanding of pcse exam topics. 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.
Which TWO of the following are true regarding Cloud Identity and Access Management (IAM) conditions?
Quick Answer
The correct answer is that IAM conditions can restrict access based on resource tags, and they also support time-based restrictions using the `request.time` attribute. This is because Cloud IAM conditions, written in Common Expression Language (CEL), allow you to create fine-grained, attribute-based access control by evaluating temporal attributes like date and time, as well as resource metadata such as tags. On the Google Professional Cloud Security Engineer exam, this concept tests your understanding of how to implement just-in-time access and resource-scoped policies, often appearing in scenarios where you must limit access to specific business hours or to resources labeled with certain project or environment tags. A common trap is confusing resource tags with resource names—tags are key-value pairs applied to resources, not the resource ID itself. Memory tip: think “Time and Tags” as the two T’s of IAM conditions—temporal controls for when, and tag-based controls for which resources.
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
✓
IAM conditions can restrict access based on the current date and time.
Option A is correct because IAM conditions support temporal attributes, including date/time restrictions, using the `request.time` attribute. This allows policies to grant access only during specific hours or days, such as allowing access only during business hours. The condition is expressed using the Common Expression Language (CEL) syntax, e.g., `request.time.getHours("America/New_York") >= 9 && request.time.getHours("America/New_York") <= 17`.
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.
- ✓
IAM conditions can restrict access based on the current date and time.
Why this is correct
DateTime conditions are supported.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
IAM conditions are supported for all Google Cloud resources.
Why it's wrong here
Conditions are not supported on all resources; e.g., Compute Engine has mixed support.
- ✗
IAM conditions can be applied to a role binding that supports all resources.
Why it's wrong here
Conditions are not supported on roles that apply to all resources.
- ✓
IAM conditions can restrict access based on resource tags.
Why this is correct
Resource tags can be used in conditions.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
IAM conditions can restrict access based on the user's email domain.
Why it's wrong here
Conditions use attributes like resource tags, date/time, but not user principal directly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that IAM conditions can restrict access based on user attributes like email domain or group membership, but in reality, conditions only support resource and request attributes, not principal attributes.
Detailed technical explanation
How to think about this question
IAM conditions use the Common Expression Language (CEL) to evaluate attributes like `resource.name`, `resource.service`, `resource.type`, `request.time`, and `resource.matchTag()`. The `resource.matchTag()` function allows restricting access based on resource tags, which are key-value pairs attached to resources, enabling fine-grained access control without modifying IAM roles. A subtle behavior is that conditions are evaluated at request time, and if the condition fails, the entire request is denied, even if the principal has the role via another binding without conditions.
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.
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?
Read the scenario before looking for a memorised answer.
What is the correct answer to this question?
The correct answer is: IAM conditions can restrict access based on the current date and time. — Option A is correct because IAM conditions support temporal attributes, including date/time restrictions, using the `request.time` attribute. This allows policies to grant access only during specific hours or days, such as allowing access only during business hours. The condition is expressed using the Common Expression Language (CEL) syntax, e.g., `request.time.getHours("America/New_York") >= 9 && request.time.getHours("America/New_York") <= 17`.
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 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: 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.