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 is configuring a production environment in Google Cloud. A newly hired data analyst has already authenticated using their corporate Google Account and now requires authorization to perform their daily tasks. The cloud administrator must configure access based on the following requirements:
How should the administrator configure Identity and Access Management (IAM) to meet these requirements?
In Google Cloud, Identity and Access Management (IAM) manages fine-grained authorization by controlling who (the principal) can do what (the role) on which target (the resource). An allow policy is a configuration object attached directly to a Google Cloud resource that contains role bindings, which link authenticated principals to specific IAM roles. Predefined roles are managed by Google Cloud services and bundle the specific permissions required to perform common, targeted business tasks.

Applying a narrowly scoped predefined role on the lowest-level resource is the industry standard for enforcing the principle of least privilege. It avoids the security risks of overly broad basic roles and prevents unintended policy inheritance across the wider Google Cloud resource hierarchy.
Basic roles—which include Owner (roles/owner), Editor (roles/editor), and Viewer (roles/viewer)—are highly permissive roles that provide broad access across all Google Cloud services. When a role is granted on a container resource such as a project, policy inheritance causes all child resources within that project to automatically inherit the allow policy of their parent container.
This approach violates the principle of least privilege in two critical ways:
The scenario involved a small, isolated testing or sandbox environment where a developer needed broad, unrestricted permissions to rapidly prototype across multiple services within a project without production security constraints.
The organization resource is the root node at the very top of the Google Cloud resource hierarchy, sitting above all folders, projects, and service-specific resources. When an administrator attaches an allow policy with a role binding at the organization level, policy inheritance ensures that those permissions cascade down to every folder, project, and individual resource across the entire company.
Although this option uses a predefined storage role, granting it on the organization resource violates the requirement to restrict the analyst to a single Cloud Storage bucket. Because descendant resources inherit the allow policies of their ancestors, the analyst would be authorized to upload files to every Cloud Storage bucket in every project throughout the entire organization.
The user was a centralized storage administrator or automated auditing workload that required uniform access to manage or inspect all Cloud Storage buckets across every folder and project in the enterprise.
In Google Cloud IAM, permissions are the foundational units of authorization that determine which specific operations are allowed on a resource. Permissions are typically formatted as service.resource.verb (for example, resourcemanager.projects.list) and usually correspond one-to-one with specific REST API methods.
In Google Cloud, administrators cannot directly grant individual permissions to a principal. IAM architecture requires permissions to be bundled into roles. An allow policy only accepts role bindings that associate a principal with a role (such as a predefined role or a custom role), never raw, standalone permissions.
The administrator was first creating a custom role by selecting individual permissions to include in that role definition, and then binding that newly created custom role to the analyst's principal on the bucket's allow policy.
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