Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A financial services organization is architecting its Google Cloud environment to support automated data pipelines and analytics workloads. The company has distinct compliance requirements across its environments and needs to design a resource hierarchy that enforces strict data governance.
The architecture must satisfy the following requirements:
How should the organization structure its resource hierarchy and security boundaries?
This design maintains a flat resource hierarchy with all projects residing immediately under the root Organization node. It configures the Service Usage API ConsumerPolicy at the project level to enable specific APIs and attempts to use Hierarchical Firewall Policies to govern access to BigQuery.
ConsumerPolicy individually per project fails to leverage folder inheritance, resulting in redundant administrative effort.bigquery.googleapis.com), which requires VPC Service Controls.The workload consisted exclusively of Compute Engine virtual machines in a single environment requiring uniform IP-based firewall filtering without multi-tenant Google Cloud storage or analytics services.
This architecture establishes a multi-tiered resource hierarchy structured around application environments (Development, Production) directly under the Organization node. It leverages folder-level inheritance to enforce Organization Policy constraints and aggregated Cloud Logging sinks, while isolating production data services within a VPC Service Controls (VPC SC) perimeter.
Production folder level. These policies are inherited across all child projects hosting production workloads, while the Development folder can maintain more permissive configurations.Designing the top-level folders by application environment aligns directly with centralized security governance needs where production requirements strictly diverge from non-production requirements. Combining folder inheritance with VPC Service Controls delivers defense-in-depth against both internal misconfigurations and external exfiltration.
This strategy splits development and production into entirely separate Google Cloud organization resources (tied to separate Cloud Identity or Google Workspace domains), configures logging within each, and deploys Google Cloud Armor to defend storage resources.
The organization acquired a completely independent subsidiary with separate legal identity structures and non-overlapping identity directories requiring total domain isolation.
This approach organizes resources into top-level folders corresponding to distinct business departments (such as Finance and Marketing), configures Cloud Logging sinks manually inside each project, and relies on IAM Deny policies to manage access permissions on analytical datasets.
The primary organizational driver was autonomous departmental ownership with completely independent security policies, and no cross-environment consistency or network perimeter protection was needed.
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