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 is designing network security controls in Google Cloud to prevent data exfiltration from resources within a Virtual Private Cloud (VPC) network. Workloads in the VPC must communicate with Google APIs exclusively through the restricted virtual IP (VIP) range 199.36.153.4/30 on TCP port 443.
The security architect must enforce strict egress controls to ensure that all general outbound internet traffic is blocked while outbound access to Google services via the restricted VIP is permitted without disrupting internal traffic flows or connector communication.
How should the VPC egress firewall rules and priority levels be configured?
Network tags are metadata strings assigned to Compute Engine VM instances used to apply firewall rules to specific VMs. The implied default allow egress rule in Google Cloud operates at priority 65535 and permits all outbound traffic to 0.0.0.0/0 unless explicitly overridden by higher-priority deny rules.
The network allowed open outbound internet access and only required tagging specific VMs for specialized monitoring or routing policies.
This configuration assigns a higher evaluation precedence (priority 900) to the broad deny 0.0.0.0/0 egress rule and a lower precedence (priority 1100) to the specific allow rule for 199.36.153.4/30.
199.36.153.4/30 falls within 0.0.0.0/0, all outbound traffic—including traffic aimed at the restricted Google VIP—matches the priority 900 deny rule first and is dropped.The objective were to achieve a total network isolation sandbox where no outbound connectivity to any endpoint, including Google Cloud APIs, was permitted under any condition.
Ingress firewall rules control incoming connections initiated from external sources toward instances in the VPC. The implied deny ingress rule (priority 65535) blocks incoming connection attempts from outside the VPC.
The workload was hosting an inbound web service and needed to accept external HTTPS connections while blocking all other unsolicited inbound traffic.
In Google Cloud VPC networks, firewall rules are evaluated sequentially based on their numerical priority (from 0 to 65535), where lower numerical values represent higher precedence. When traffic matches a rule with higher precedence, that rule is applied immediately, and subsequent lower-priority rules are ignored.
0.0.0.0/0 ensures that all outbound traffic destined for external internet endpoints is blocked.199.36.153.4/30 on TCP port 443 explicitly permits communication with Google APIs.900) and the broad deny rule at a priority after 1000 (e.g., 1100) ensures that traffic to the restricted VIP is evaluated and allowed before the broad deny rule is reached.
This configuration ensures that traffic destined for 199.36.153.4/30 is processed and allowed first, while all other egress is systematically dropped without interfering with default VPC internal routing.
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