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 company has configured Cloud Identity to verify employee identities upon sign-in. Now, the security team needs to configure resource authorization in their production environment for a new developer while strictly adhering to the principle of least privilege.
The developer's daily tasks require the following access:
Which approach should the security team implement to authorize this access and minimize security risks?
roles/editor) at the organization level so the developer automatically inherits access to both servicesBasic roles—which include Owner (roles/owner), Editor (roles/editor), and Viewer (roles/viewer)—are broad, legacy IAM roles that span across all Google Cloud services. When a role is granted at the organization level (the root node of the Google Cloud resource hierarchy), all lower-level resources—including folders, projects, storage buckets, and virtual machines—automatically inherit those permissions.
The scenario involved a small, isolated sandbox or proof-of-concept project with no sensitive data where a single developer needed rapid, unrestricted access to experiment with many different Google Cloud services simultaneously.
To maintain security in production, administrators should always eliminate basic roles first and instead select the most limited predefined roles or create custom roles granted at the lowest hierarchy level that satisfies the user's requirements.
In Google Cloud Identity and Access Management (IAM), authorization is the process of determining which resources an authenticated identity (principal) can access and what actions they are allowed to perform. Predefined roles are Google-managed collections of granular permissions tailored to specific services or job functions. Applying these roles at the lowest applicable level of the resource hierarchy enforces the principle of least privilege, ensuring users only receive the minimum permissions necessary to perform their tasks.
SERVICE.RESOURCE_TYPE.ACTION) from administrative database permissions.Unlike broad basic roles or high-level hierarchy grants that expose thousands of permissions across an entire organization or project, combining targeted predefined roles at the resource level gives the developer the exact capabilities needed for their job function while eliminating excess privileges.
serviceAgent) at the project level to bundle permissions across multiple Google Cloud servicesService agent roles (identifiable by titles ending in "Service Agent" and role IDs ending in serviceAgent) are specialized predefined IAM roles designed exclusively for service agents. A service agent is a Google-managed service account that allows a Google Cloud service to access customer resources and perform automated background tasks on the customer's behalf.
serviceAgent roles automatically when an API is enabled.A Google Cloud service itself needed automated background permissions to manage and interact with underlying project resources on behalf of the customer after an API was enabled.
When a human principal requires permissions spanning multiple services, best practices dictate selecting separate predefined roles for each individual service (or creating a custom role) rather than repurposing a serviceAgent role that contains excessive cross-service privileges.
Workforce Identity Federation and password policies are foundational authentication controls used to onboard, manage, and verify user identities. Workforce Identity Federation lets organizations use an external identity provider (IdP) to authenticate a workforce of users, while strong password policies ensure that user credentials are unique and difficult for malicious actors to guess or exploit during sign-in.
SERVICE.RESOURCE_TYPE.ACTION permissions.The organization needed to establish an identity source of truth to allow employees to sign in to Google Cloud using an existing third-party corporate identity provider and wanted to secure user accounts against weak-credential exploits.
A fundamental concept in cloud security is distinguishing between authentication (proving who you are) and authorization (determining what you are allowed to do). While Cloud Identity and Workforce Identity Federation handle authentication, IAM roles and allow policies handle authorization and enforce the principle of least privilege.
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