Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise uses automated CI/CD pipelines to dynamically provision ephemeral test environments for pull requests. Multiple engineering teams deploy dozens of short-lived Google Cloud projects daily. You must implement a governance, lifecycle, and cost control strategy that satisfies the following requirements:
What should you do?
This option grants the deployment pipeline full administrative control over the billing account and uses manual file exports and uptime checks to determine project lifecycles.
roles/billing.admin gives the automation pipeline permission to manage billing accounts, alter payment methods, and modify IAM policies on the billing account itself, directly contradicting the requirement to avoid broad billing admin privileges.A single standalone virtual machine needed basic self-healing restarts based on internal application health and the pipeline administrator held exclusive responsibility for billing account management.
This option gives individual engineers full control over the organizational resource hierarchy, leaves resources unlabeled, and relies on billing budget limits to disable APIs when spend thresholds are hit.
roles/resourcemanager.organizationAdmin gives developers unrestricted power across the entire organization, including modifying organization policies, IAM bindings, and root folder structures.An organization had no central platform team, operated completely manually without automated pipelines, and required hard emergency caps on non-production billing accounts.
This approach segments financial reporting by establishing discrete billing accounts for every development team, assigns read-only billing roles, and attempts to trigger project destruction from inside individual virtual machines.
roles/billing.viewer role only permits read access to billing account metadata; it does not grant the pipeline the ability to associate the billing account with newly created projects.Different teams were legally distinct corporate subsidiaries requiring completely separate currency payments, contracts, and distinct legal invoices.
This solution implements a complete automated lifecycle and governance framework for dynamic, short-lived environments. It combines principle-of-least-privilege Identity and Access Management (IAM), structured resource tagging, granular analytical billing exports, and serverless automation to manage ephemeral infrastructure safely at scale.
roles/billing.user) at the organization or billing account level allows the automation service account to attach the billing account to newly created projects without granting permissions to view invoices, modify billing admins, or adjust payment profiles.environment: ephemeral, team: core-platform, and ttl: 24h) ensures every dollar spent is tracked. Exporting billing data directly into BigQuery provides a robust, real-time analytics warehouse to slice and dice costs across teams, environments, and specific pipeline runs.This architecture establishes a secure, hands-off operational model. It avoids administrative bottlenecks and enforces resource disposal at the project root level, guaranteeing that all child cloud resources (disks, IPs, services) are destroyed together.
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 Validated