- A
Password complexity requirements — enforcing long, complex passwords.
Why wrong: Strong passwords improve security but are still a single factor. Multi-factor authentication adds a second independent factor (something you have or are) that is much more resistant to compromise.
- B
Multi-factor authentication (MFA) / Two-step verification (2SV).
MFA requires a second factor beyond the password — physical security keys, TOTP apps, or other verifiers. Even if a password is stolen, the second factor prevents unauthorized access.
- C
IP allowlisting — only allowing access from office IP addresses.
Why wrong: IP allowlisting restricts access by network location. It doesn't verify user identity beyond the network they're on, and blocks legitimate remote access from trusted employees.
- D
Session timeout — automatically logging out users after 30 minutes of inactivity.
Why wrong: Session timeout limits exposure from unattended sessions but doesn't verify identity at login. MFA is an authentication mechanism, not a session management policy.
Quick Answer
The answer is multi-factor authentication (MFA), also known as two-step verification (2SV). This security feature enforces the requirement to verify identity beyond a password by demanding two or more distinct factors—typically something you know (a password), something you have (a time-based one-time password from an authenticator app or a hardware security key like FIDO2), or something you are (a biometric). On the Google Cloud Digital Leader exam, this concept tests your understanding of how Identity Platform policies, such as security key enforcement and 2SV, directly mitigate credential theft. A common trap is confusing MFA with single sign-on (SSO); remember that SSO simplifies login but does not inherently add a second factor. The exam emphasizes that password compromise alone must be insufficient for access, which is exactly what MFA ensures. Memory tip: think “MFA = More Factors Always” to recall that it requires at least two distinct verification methods to enforce multi-factor authentication for Google Cloud access.
Cloud Digital Leader Trust and security with Google Cloud Practice Question
This GCDL practice question tests your understanding of trust and security with google cloud. 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.
A company's security policy requires all employees to verify their identity using more than just a password when accessing Google Cloud resources. What security feature enforces this requirement?
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
Multi-factor authentication (MFA) / Two-step verification (2SV).
Multi-factor authentication (MFA) / Two-step verification (2SV) is the correct answer because it explicitly requires users to provide two or more verification factors (e.g., something you know, something you have, something you are) to access Google Cloud resources. This directly enforces the policy of verifying identity beyond just a password, as MFA/2SV adds an additional layer of security by requiring a second factor such as a time-based one-time password (TOTP) from an authenticator app, a hardware security key (e.g., FIDO2), or a push notification. Google Cloud Identity Platform supports this via security key enforcement and 2SV policies, ensuring that password compromise alone is insufficient for access.
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.
- ✗
Password complexity requirements — enforcing long, complex passwords.
Why it's wrong here
Strong passwords improve security but are still a single factor. Multi-factor authentication adds a second independent factor (something you have or are) that is much more resistant to compromise.
- ✓
Multi-factor authentication (MFA) / Two-step verification (2SV).
Why this is correct
MFA requires a second factor beyond the password — physical security keys, TOTP apps, or other verifiers. Even if a password is stolen, the second factor prevents unauthorized access.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
IP allowlisting — only allowing access from office IP addresses.
Why it's wrong here
IP allowlisting restricts access by network location. It doesn't verify user identity beyond the network they're on, and blocks legitimate remote access from trusted employees.
- ✗
Session timeout — automatically logging out users after 30 minutes of inactivity.
Why it's wrong here
Session timeout limits exposure from unattended sessions but doesn't verify identity at login. MFA is an authentication mechanism, not a session management policy.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'stronger authentication' with 'stronger passwords' (Option A) or 'access restrictions' (Option C), failing to recognize that the core requirement is adding an independent second factor, not just hardening the single password factor.
Detailed technical explanation
How to think about this question
Under the hood, Google Cloud's MFA/2SV leverages the Time-based One-Time Password (TOTP) algorithm (RFC 6238) or FIDO2/WebAuthn standards for hardware security keys, which generate cryptographically bound credentials that cannot be reused or phished. A subtle behavior is that when MFA is enforced via Google Workspace or Cloud Identity, it can be applied at the organization level or per OAuth client, and users must enroll at least one second factor before accessing resources. In a real-world scenario, an attacker who steals a user's password via phishing cannot authenticate without the second factor (e.g., a YubiKey or Google Authenticator code), even if they have the password and the user's IP address.
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.
- →
Trust and security with Google Cloud — study guide chapter
Learn the concepts, then practise the questions
- →
Trust and security with Google Cloud practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL 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 GCDL question test?
Trust and security with Google Cloud — This question tests Trust and security with Google Cloud — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Multi-factor authentication (MFA) / Two-step verification (2SV). — Multi-factor authentication (MFA) / Two-step verification (2SV) is the correct answer because it explicitly requires users to provide two or more verification factors (e.g., something you know, something you have, something you are) to access Google Cloud resources. This directly enforces the policy of verifying identity beyond just a password, as MFA/2SV adds an additional layer of security by requiring a second factor such as a time-based one-time password (TOTP) from an authenticator app, a hardware security key (e.g., FIDO2), or a push notification. Google Cloud Identity Platform supports this via security key enforcement and 2SV policies, ensuring that password compromise alone is insufficient for access.
What should I do if I get this GCDL 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 GCDL practice questions
- What is virtualization in the context of cloud computing, and why is it fundamental to how cloud providers deliver servi…
- A company stores its data in Google Cloud. The security team asks: can Google employees access our customer data without…
- A company is evaluating whether to use a content delivery network (CDN) for its e-commerce website. Which scenario would…
- A company's SRE team is debating whether to automate a frequently performed manual operational task. The automation woul…
- A DevOps team wants to adopt GitOps practices for managing their Google Cloud infrastructure. Which combination of tools…
- A startup is building an application that sends daily promotional push notifications to millions of mobile users on both…
Last reviewed: Jun 11, 2026
This GCDL 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 GCDL 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.