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.
A financial services company is reviewing the Identity and Access Management (IAM) configuration of its Google Cloud production environment. During the audit, the security team discovers the following configurations:
roles/editor) role at the project level.The team decides to enforce the principle of least privilege by transitioning users and service accounts to granular, predefined IAM roles tailored to their specific tasks.
How does this change benefit the organization's security posture?
Phishing-resistant multi-factor authentication (MFA)—implemented in Google Cloud as Two-Step Verification (2SV) using hardware security keys—is an authentication control that requires users to present a physical cryptographic token in addition to their password when signing in. Its primary purpose is to verify a user's identity and prevent account takeover from stolen or phished passwords.
While enforcing 2SV with hardware security keys is a vital security practice, it does not describe the benefit of implementing the principle of least privilege:
roles/editor role, they retain overly broad permissions that can lead to accidental project alterations or internal misuse.The scenario asked how the organization could protect its Super Administrators from sophisticated credential-phishing attacks during the sign-in process by enforcing a physical second factor.
In Google Cloud's security model, 2SV and IAM least privilege serve as complementary layers of defense. 2SV secures the front door by ensuring only legitimate users can log in, while the principle of least privilege ensures that once authenticated, users and service accounts can only access the specific resources required for their tasks.
Allowing external applications to authenticate to Google Cloud without downloadable service account keys is the primary function of Workload Identity Federation. This capability lets workloads running on-premises, in other public clouds, or in external CI/CD systems exchange trusted credentials from an external identity provider for short-lived Google Cloud access tokens.
This option describes a mechanism for secure credential management and external workload authentication rather than the benefit of scoping down permissions through the principle of least privilege:
serviceAccountKey), addressing how an application authenticates rather than what resources it is authorized to touch.roles/editor role, that workload still has excessive access across the entire project.The scenario described an organization trying to eliminate the security risk of storing long-lived, downloadable service account keys in an external CI/CD pipeline or multi-cloud environment.
While Workload Identity Federation is a recommended best practice for authenticating external workloads, administrators must still apply the principle of least privilege to the service accounts those workloads use so that a compromised workload cannot access unrelated project resources.
Creating redundant administrator accounts is an identity governance best practice where an organization provisions one or more backup Super Admin or Organization Administrator accounts (up to 20) rather than relying on a single administrator. Its actual purpose is to ensure administrative continuity, provide oversight, and prevent complete organizational lockout.
This option focuses on administrative availability and account recovery rather than the security benefits of enforcing the principle of least privilege:
roles/editor) from everyday identities rather than adding backup administrative accounts.The scenario described a company that relied on a single Organization Administrator or Super Admin and wanted to mitigate the operational risk of losing access to its entire Google Cloud organization.
Maintaining redundant administrator accounts and enforcing the principle of least privilege address two different aspects of cloud governance. While an organization needs a small, carefully protected set of backup admin accounts for emergency recovery, routine developer accounts and application service accounts should be strictly limited to granular, task-specific roles.
The principle of least privilege (PoLP) is a foundational security practice in Identity and Access Management (IAM) that ensures human users and automated service accounts are granted only the minimum permissions necessary to perform their designated tasks. Instead of assigning overly broad basic roles like Editor (roles/editor) or Owner (roles/owner) at the project level, administrators assign narrow predefined roles or custom roles aligned with specific job functions and workload requirements.
Transitioning from broad project-level access to granular roles directly addresses the vulnerabilities found during the security audit:
roles/editor, the organization eliminates unintended pathways that an attacker or malicious insider could exploit.Relying on basic roles or a single shared service account creates a high-value target where a single compromised credential puts the entire project at risk. Enforcing the principle of least privilege at the authorization layer is the most effective way to contain potential breaches and shrink the organization's attack surface.
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