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.
An enterprise organizes its Google Cloud resource hierarchy into distinct folders for network infrastructure and business workloads. The Shared VPC host project resides in the Core-Networking folder, while multiple service projects containing Compute Engine virtual machines (VMs) reside in the App-Workloads folder.
The central security team applies a hierarchical firewall policy to the Core-Networking folder that denies ingress TCP traffic on port 22. To allow remote access, a development team attaches another hierarchical firewall policy directly to the App-Workloads folder with a high-priority rule allowing ingress TCP traffic on port 22. However, SSH traffic to the VMs connected to the Shared VPC subnets remains blocked.
Why is the ingress traffic on TCP port 22 still blocked on these VM instances?
Hierarchical firewall policies are evaluated in order from the highest level of the resource hierarchy (Organization) down through child folders to the project level. When policies exist at multiple folder tiers within the same ancestral path, evaluation proceeds based on rule order and explicit rule actions.
goto_next action or if traffic does not match an explicit upper rule.Core-Networking and App-Workloads) are separate sibling trees rather than a direct parent-child relationship, meaning this is an architectural scoping boundary issue specific to Shared VPC rather than standard vertical inheritance.The App-Workloads folder were a direct subfolder inside Core-Networking and the parent policy contained an explicit terminal deny rule that was evaluated before any child policy rules.
Hierarchical evaluation strictly follows the resource tree ancestry of the governing resource, which for network packets is the host project owning the VPC.
In Google Cloud networking, hierarchical firewall policies allow organizations to define and enforce consistent firewall rules across resource hierarchy nodes such as organizations and folders. When resources utilize Shared VPC, network interfaces attached to shared subnets reside logically within the shared network hosted by the host project.
Core-Networking folder).App-Workloads folder, the network interfaces inherit policies from the ancestry of the VPC network they attach to, completely ignoring the hierarchical firewall policies applied to the App-Workloads folder.
This model preserves strict centralized security boundaries across enterprise cloud deployments. It prevents decentralized teams in child folders from opening security holes on corporate shared networks, ensuring compliance across all connected workloads.
Organization Policies provide centralized governance constraints (such as restricting external IPs or resource locations) over Google Cloud resource configurations. Hierarchical Firewall Policies configure network packet filtering rules (allowing or denying specific IP protocols, ports, and IP ranges).
compute.orgSecurityResourceAdmin), provided the network ancestry matches.constraints/compute.vmExternalIpAccess).The issue involved a constraint such as constraints/compute.vmExternalIpAccess blocking the creation of instances with public IPs, which would require an Organization Policy override at the project or folder level.
Confusing Organization Policy constraints with Cloud NGFW hierarchical firewall rules is a common misconception in multi-folder governance planning.
Compute Engine instances evaluate multiple layers of network filtering, combining hierarchical firewall policies, global/regional network firewall policies, and traditional VPC firewall rules into a single effective firewall ruleset via the Andromeda virtualization layer.
goto_next.Hierarchical firewall policies did not exist and all network controls were solely configured as traditional per-project VPC firewall rules.
To view all active firewall rules on an instance across both hierarchical and local policies, administrators can check the effective firewall rules on the instance or network.
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