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 structuring its Google Cloud resource hierarchy across multiple departments and business units. The IT administrator needs to configure permissions so that developers can create projects and attach them to their specific department's Cloud Billing account without granting them broad administrative privileges over billing settings.
Which statement accurately describes the relationship between Cloud Billing accounts and projects, and the role required to link them?
This option claims that a single project can link to multiple Cloud Billing accounts at the same time to distribute costs across departments, and refers to a Project Owner role applied directly to a billing account.
roles/owner) role is a basic project-level role and cannot be assigned at the billing account level to govern billing associations.roles/billing.projectManager or project creation privileges).roles/billing.user, roles/billing.viewer, and roles/billing.admin, keeping them distinct from project-level primitive roles.Google Cloud supported multi-parent billing attachments per project and used primitive project roles directly on billing resource objects.
In Google Cloud, a Cloud Billing account is an administrative entity linked to a Google payments profile that defines who pays for resource usage. Projects sit within the resource hierarchy (under folders and an organization) and contain the actual infrastructure resources that incur costs. A project has a many-to-one relationship with a Cloud Billing account: each project can link to exactly one billing account at any given time, whereas a single billing account can fund multiple projects.

roles/billing.user) role on the billing account, combined with project creation capabilities (roles/resourcemanager.projectCreator).This model preserves security and operational boundaries by separating financial ownership from resource management. It prevents permission leakage across projects while enabling centralized or distributed procurement workflows according to organizational policies.
This option suggests that a Cloud Billing account sits above projects as their direct IAM parent node and that read-only access via the Billing Account Viewer (roles/billing.viewer) role is sufficient to link projects.
billing.accounts.redeemPromotion or billing.resourceAssociations.create permissions necessary to bind a project to a billing account.The objective was solely to let financial planning or accounts payable teams review invoices and cost data without granting any ability to spin up or link billable workloads.
This option asserts that IAM policies set on a Cloud Billing account cascade down to all linked projects through inheritance, and that only a Billing Account Administrator (roles/billing.admin) can perform project association.
Organization -> Folder -> Project -> Resource.Google Cloud structured billing accounts as direct parent containers of projects in the resource management tree and required complete administrative control over payment instruments to initiate project billing.
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