Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise uses Cloud Identity to govern administrative access to Google Cloud projects hosting mission-critical workloads. A recent internal red-team assessment demonstrated that threat actors could execute adversary-in-the-middle (AitM) reverse-proxy phishing attacks to intercept session cookies and bypass standard multi-factor authentication methods, such as SMS codes and mobile authenticator push prompts.
The security architect must enforce an authentication policy for all privileged administrators that eliminates credential harvesting and AitM relay attacks.
Which 2-Step Verification (2SV) configuration should the architect implement?
Time-based One-Time Password (TOTP) authenticators (such as Google Authenticator) generate dynamic 6-digit verification codes every 30 seconds based on a shared secret key and the current Unix timestamp according to RFC 6238. In Cloud Identity, selecting Any allows users to fulfill 2-Step Verification using TOTP apps, Google prompts, SMS, or hardware keys.
accounts.google.com or a malicious proxy domain.The organization required a cost-effective, device-agnostic MFA solution to protect standard, non-privileged business users against basic automated credential stuffing attacks, where hardware key deployment was not operationally feasible.
SMS-based 2-Step Verification transmits numeric one-time passcodes over telecommunication cellular networks via Short Message Service. Combining this with Context-Aware Access (CAA) evaluates context attributes, such as whether the incoming authentication request originates from trusted corporate public IP subnets, before granting access to Google Cloud resources.
The objective was to establish contextual zero-trust perimeter gates to restrict login attempts to corporate branch offices, rather than preventing protocol-level AitM credential interception on privileged accounts.
FIDO2/WebAuthn hardware security keys represent a cryptographically bound authentication standard designed by the FIDO Alliance and W3C. In Cloud Identity and Google Workspace, administrators can create targeted security policies applied to specific Organizational Units (OUs) or access groups, configuring the 2-Step Verification (2SV) enforcement setting specifically to Only security key. This policy restricts the acceptable second-factor method exclusively to physical, hardware-based cryptographic keys (such as Google Titan Security Keys or YubiKeys) or platform authenticators supporting FIDO2/WebAuthn protocols.
accounts.google.com) to the security key. The security key signs a challenge using the private key registered specifically for that domain. If an adversary proxies the traffic through a spoofed domain (such as login.attacker-domain.com), the origin signature fails, and the authentication request is instantly rejected.Enforcing Only security key at the OU level provides absolute phishing resistance against sophisticated AitM proxies and reverse-proxy credential harvesting kits. It represents the highest assurance level of multi-factor authentication supported in Google Cloud and Cloud Identity.
Google Prompts send an out-of-band push notification to a trusted Android or iOS mobile device associated with the user account. Number matching requires the user to select or enter the specific two-digit number displayed on the login screen into their mobile device to confirm that the login attempt corresponds to their immediate browser session.
The primary goal was to prevent MFA fatigue attacks (where adversaries repeatedly spam push approvals until a user inadvertently accepts) for standard general workforce accounts without distributing hardware tokens.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated