Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is deploying a dual-stack (IPv4 and IPv6) application in Google Cloud protected by a Cloud NGFW global network firewall policy. You must enforce least-privilege traffic filtering across all endpoints:
INTERNAL_MANAGED_LB).ping6) from backend VMs to an IPv6 monitoring subnet.Which Cloud NGFW firewall policy rule configuration meets all of these requirements?
This option correctly identifies tcp (without ports) for INTERNAL_MANAGED_LB and protocol 58 for IPv6 ICMP, while trying to optimize rule management by relying on implied ingress behavior, filtering client ephemeral source ports, and restricting ICMPv6 to Echo Request messages (type 128).
INTERNAL_MANAGED_LB: Unlike VM network interfaces (whose implied ingress action is deny), the implied ingress action for internal Application Load Balancers and internal proxy Network Load Balancers is allow. Relying on the implied action leaves the load balancer open to all sources instead of restricting access.1024-65535) for tcp:8080-8090 is invalid.128).| Feature | VM Instances (INSTANCES) | Internal LBs (INTERNAL_MANAGED_LB) |
|---|---|---|
| Implied Ingress Action | deny | allow |
| Implied Egress Action | allow | Not applicable (ingress only) |
| Source Port Filtering | Not supported | Not supported |
| ICMP Types/Codes | Not supported | Not supported |
Explicit low-priority INGRESS deny rules were added for INTERNAL_MANAGED_LB (and INSTANCES if logging is needed), source port filtering was removed from the tcp:8080-8090 rule, and ICMP type 128 was omitted from the protocol 58 rule.
This option attempts to restrict inbound and outbound traffic using broad deny rules paired with selective allow rules for HTTPS (tcp:443) on the internal load balancer, tcp:8080-8090 on backend VMs, and icmp for outbound IPv6 monitoring.
INTERNAL_MANAGED_LB port definition: Specifying tcp:443 in a rule with target type INTERNAL_MANAGED_LB is rejected by Cloud NGFW. Load balancer firewall rules support only the TCP protocol (tcp or 6) and require omitting destination ports because the forwarding rule dictates the exposed port.icmp applies strictly to IPv4 ICMP (protocol 1). Outbound ping6 traffic uses IPv6 ICMP, which requires IANA protocol number 58, causing ping6 packets to fall through to the low-priority deny rule.0.0.0.0/0 and ::/0 within the same rule is not supported; a single firewall rule can contain either IPv4 or IPv6 CIDR ranges, never both.INTERNAL_MANAGED_LB apply to all traffic directed to the forwarding rule and cannot include port numbers or ranges.icmp only match IPv4, whereas dual-stack or IPv6-specific protocols with differing IANA numbers (such as ICMPv6) require explicit numeric configuration.The INTERNAL_MANAGED_LB rule omitted :443 (specifying only tcp), separate IPv4 and IPv6 deny rules were created for both INSTANCES and INTERNAL_MANAGED_LB, and the outbound monitoring rule used IANA protocol 58 instead of icmp.
This configuration tries to enforce strict bidirectional control by adding explicit return-traffic rules (tcp:1024-65535) for backend VMs, applying EGRESS deny rules to internal load balancers, and consolidating IPv4 and IPv6 ranges into shared rules.
0.0.0.0/0) and IPv6 (::/0) CIDR ranges; separate rules are mandatory for dual-stack default policies.EGRESS rule on INTERNAL_MANAGED_LB: Firewall policy EGRESS rules apply exclusively to Compute Engine VM network interfaces (INSTANCES), not to INTERNAL_MANAGED_LB forwarding rules.INGRESS traffic on tcp:8080-8090 is allowed, a connection tracking table entry automatically permits outbound response packets matching the reversed 5-tuple, bypassing any EGRESS deny rules. Adding an EGRESS allow rule for tcp:1024-65535 violates least privilege by allowing backend VMs to initiate brand-new outbound TCP connections to any destination on ports 1024–65535.icmp applies only to IPv4 ICMP, failing to permit IPv6 ping6 traffic (which requires IANA protocol 58).INSTANCES support EGRESS direction rules.icmp keyword.IPv4 and IPv6 ranges were placed in separate rules, EGRESS rules were applied only to INSTANCES, the unnecessary tcp:1024-65535 egress rule was removed, and IANA protocol 58 replaced icmp.
This configuration uses Cloud Next Generation Firewall (Cloud NGFW) policy rules with properly scoped traffic direction (INGRESS and EGRESS), target types (INSTANCES and INTERNAL_MANAGED_LB), IP version separation, and Layer 4 protocol and port constraints to implement strict least-privilege filtering across a dual-stack VPC network.
allow for EGRESS traffic on VM instances and an implied allow for INGRESS traffic targeting INTERNAL_MANAGED_LB. Creating explicit low-priority deny rules with separate IPv4 (0.0.0.0/0) and IPv6 (::/0) ranges overrides those implied permissions, while also enabling firewall logging for blocked traffic.INTERNAL_MANAGED_LB support only tcp (or IANA protocol 6) and prohibit destination port specifications because the load balancer's forwarding rule already defines the listening port (TCP 443).tcp:8080-8090 permits inbound connections to the exact application port range without attempting to configure unsupported source port filters. Because Cloud NGFW is stateful, connection tracking automatically permits outbound return traffic matching the reversed 5-tuple back to clients' ephemeral ports.ping6): While the protocol name icmp in Google Cloud firewall rules maps exclusively to IPv4 ICMP (IANA protocol 1), specifying IANA protocol number 58 accurately permits IPv6 ICMP packets to the monitoring subnet.INTERNAL_MANAGED_LB) and Compute Engine NICs (INSTANCES).deny rules allow administrators to log dropped traffic that would otherwise silently hit implied rules.This design satisfies every Cloud NGFW Layer 4 constraint—omitting destination ports on load balancer rules, omitting unsupported source ports, using IANA protocol 58 for IPv6 ICMP, and separating IPv4/IPv6 ranges—while enforcing a true zero-trust posture.
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