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 organization maintains several Google Cloud projects dedicated to development, testing, and production environments, all connected to a central Cloud Billing account.
During an internal cloud governance review, an administrator needs to evaluate the relationship between billing accounts and projects, as well as what happens to running services if a project is unlinked from its billing account.
Which statement correctly describes the association between Cloud Billing accounts and projects and the operational effect of disabling billing on a project?
A strict one-to-one (1:1) billing architecture requires every single project to maintain its own independent billing account, payment instrument, and invoice stream.
Google Cloud decoupled compute execution from financial backing, allowing unpaid infrastructure to run freely while locking user access.
Requiring a 1:1 project-to-billing relationship would create massive operational overhead for enterprises managing hundreds of cloud projects.
In Google Cloud, a Cloud Billing account serves as the central payment mechanism that tracks costs accrued by Google Cloud resources. The relationship between billing accounts and projects is fundamentally one-to-many (1:N):

When a project is unlinked or billing is disabled, Google Cloud immediately limits or terminates the project's ability to consume billable cloud infrastructure:
This design guarantees financial control and accountability. By enforcing that a project can only bill to one account, billing attribution is deterministic. Furthermore, disabling billing prevents runaway cloud expenses by stopping active compute and database workloads immediately.
Automatic tier throttling is a hosting model where unpaid or unbilled systems automatically scale down to free-tier quotas and lower hardware specifications without terminating workloads.
Google Cloud automatically downsized and reconfigured arbitrary enterprise architectures into Always Free tier shapes upon billing account disconnection.
To prevent unexpected service interruption for production systems, administrators should protect billing associations and monitor budgets using alerts rather than unlinking billing accounts.
Cost splitting across multiple billing entities is an accounting concept where resource charges are partitioned across distinct financial payment instruments or cost centers.
Google Cloud supported multi-parent billing associations at the project level with built-in automatic failover and cost-splitting across multiple payment profiles.
Organizations requiring separate billing accounts for different workloads should organize their resources into separate projects, with each project linked to its respective billing account.
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