Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An enterprise is deploying a new application on Google Cloud and needs to establish a secure sign-in process. The security team has established the following requirements:
Which authentication approach should the enterprise implement to meet these requirements?
Workload Identity Federation is a Google Cloud security capability that enables external, non-human workloads—such as applications running in on-premises data centers or other cloud providers—to authenticate to Google Cloud resources without requiring downloadable service account keys. It exchanges credentials from external OIDC-compatible or SAML 2.0-compatible identity providers for short-lived Google Cloud access tokens.
This option would be the right choice if the enterprise needed to allow automated applications running in an on-premises data center or another public cloud to access Google Cloud storage or databases securely without managing service account keys.
While both Workload Identity Federation and Identity Platform support SAML and OIDC federation, they serve entirely different principals. Workload Identity Federation authenticates external software services and server workloads, whereas Identity Platform and Cloud Identity authenticate human users through passwords, federated single sign-on (SSO), and multi-factor authentication (MFA).
Identity and Access Management (IAM) roles and three-legged OAuth (3LO) are mechanisms primarily used for authorization—the process of determining what resources a user or application is permitted to access after their identity has already been verified. In a three-legged OAuth flow, an application obtains explicit permission from an end user via an authorization server to access resources owned by that user.
This approach would be appropriate if the enterprise had already established user authentication and needed to configure authorization policies to control which Google Cloud resources an authenticated principal can access, or needed an application to request permission to read data owned by an end user.
In cloud security, distinguishing between authentication (verifying identity via passwords, MFA, or federated identity providers), authorization (controlling resource access via IAM roles), and auditing (recording access logs) is essential. Services like Identity-Aware Proxy (IAP) rely on authentication tokens first before evaluating IAM roles for authorization.
Anonymous authentication is a feature within Identity Platform and Firebase Authentication that creates temporary, unverified accounts for end users. This mechanism allows users to interact with application features that technically require an authentication token without forcing the user to sign in or provide personal credentials upfront.
This approach would be correct if the company were building a consumer mobile game or e-commerce app where guests needed to try out features or build a shopping cart before registering for a permanent account.
Establishing true identity trust requires collecting verifiable credentials—such as a password, a cryptographic assertion from a trusted Identity Provider (IdP), and a second verification factor (MFA). Anonymous authentication is strictly a convenience mechanism for guest sessions until full authentication is performed.
Authentication is the foundational security process of verifying a user's identity to confirm that they are who they claim to be. Unlike authorization (which determines which resources an authenticated user can access) and auditing (which logs and tracks user activity), authentication focuses strictly on establishing initial trust at sign-in. Identity Platform is a customer identity and access management (CIAM) service in Google Cloud that provides customizable backend authentication services, SDKs, and UI libraries to verify user identities across web and mobile applications.

/__auth/handler), reducing custom backend overhead.Combining password authentication, federated identity services, and MFA within Identity Platform directly addresses every layer of modern user identity verification. It establishes strong cryptographic trust without forcing administrators to build custom credential verification workflows from scratch.
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