Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial enterprise is establishing a cloud governance framework and decision-making model for its migration to Google Cloud. The initiative must satisfy distinct requirements across multiple stakeholder groups:
Which governance strategy should the enterprise implement to align these stakeholders across the decision-making lifecycle?
This model concentrates all provisioning, configuration, and governance tasks entirely within a central security team, restricting all engineering personnel to read-only (roles/viewer) permissions across development and production environments, while using basic Cloud Billing reports without a structured tagging or labeling schema.
The cloud environment were an immutable, highly restricted archive requiring zero developer interaction and no internal department billing attribution.
This option implements a completely decentralized, unconstrained operating model where individual application teams make independent decisions regarding architecture, regulatory controls, and cloud spending without centralized standards or automated organization policies.
The organization were a loose incubator of disconnected prototype projects where compliance, data residency, and central financial auditing were not required.
A cross-functional cloud governance framework integrates technical, financial, and compliance controls into the organizational decision-making lifecycle. By pairing a central FinOps practice with automated cloud-native governance tools like the Google Cloud resource hierarchy, Organization Policy Service, and Assured Workloads, enterprises establish clear guardrails that align enterprise objectives with decentralized operational execution.
gcp.resourceLocations) alongside Assured Workloads automatically restricts workloads and data at rest to compliant geographic regions, satisfying strict compliance mandates systematically.
This strategy balances centralized oversight with decentralized operational agility. Instead of creating administrative bottlenecks, it embeds automated technical guardrails and standardized financial tooling, satisfying all regulatory, financial, and operational criteria simultaneously.
This option relies on traditional IT service management (ITSM) patterns characterized by a centralized Change Advisory Board (CAB) reviewing every infrastructure request, placing all enterprise workloads into a single shared Google Cloud project, and relying on manual spreadsheets for quarterly financial reconciliations.
The organization were operating a single, monolithic legacy application with minimal change frequency and no requirement for multi-department cost attribution or agility.
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