Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An enterprise is setting up its Google Cloud resource hierarchy for several development teams. The cloud administrator needs to group resources into logical environments (such as Development and Production), manage access permissions centrally so child projects inherit them, and allow team leads to create new projects and link them to the organization's existing Cloud Billing account.
Which configuration and role assignment should the administrator implement?
Labels are key-value pairs used as metadata on projects and resources for filtering, reporting, and cost allocation. The Billing Account Viewer (roles/billing.viewer) role allows users to view billing account costs, invoices, and payment history.
roles/billing.user permission required to attach a project to that billing account.The goal was to allow a finance auditor to examine organization-wide spending trends and filter exported cost reports using metadata tags without modifying infrastructure.
A Cloud Billing account is a financial construct linked to a Google payments profile that tracks resource costs and handles invoicing for Google Cloud projects.
roles/billing.admin) role gives full control over the billing account, including managing payment methods, closing accounts, and modifying billing permissions. This violates the principle of least privilege for development leads who only need to link projects.The objective was to delegate financial ownership, invoice approvals, and payment instrument management to independent business entities with completely isolated legal payment terms.
In Google Cloud, Folders are resource hierarchy nodes positioned between the organization node and projects. They allow administrators to group projects logically and apply Identity and Access Management (IAM) policies that are automatically inherited by all nested folders and child projects. The Project Creator (roles/resourcemanager.projectCreator) role allows users to provision new projects, while the Billing Account User (roles/billing.user) role provides the necessary permission to attach projects to an existing Cloud Billing account without exposing billing administrative control.

This architecture adheres directly to standard Google Cloud resource hierarchy practices. Folders serve as the primary grouping mechanism for environment-level access inheritance, while pairing roles/resourcemanager.projectCreator with roles/billing.user grants developers the exact least-privilege permissions required to build and fund workloads.
A Project is the base-level organizing entity for all cloud infrastructure (such as Compute Engine instances or Cloud Storage buckets). The Folder Administrator (roles/resourcemanager.folderAdmin) role is designed specifically to manage folders at the organization or folder level.
The organization was managing a very small single-purpose test scenario with no requirement for environment separation, folder hierarchies, or delegated billing access.
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