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 hardening north-south traffic for a production VPC network using a global network firewall policy with Cloud NGFW Standard tier features. You must enforce these controls at the network layer without deploying zonal firewall endpoints or incurring Cloud NGFW Enterprise charges:
203.0.113.25/32) listed on the Tor exit node feed.c2.malicious-actor.example), ensuring logs identify which threat feed triggered each match.Which configuration should you implement?
203.0.113.25/32, separate lower-priority ingress deny rules for iplist-known-malicious-ips and iplist-tor-exit-nodes, and an egress deny rule using destination geolocation objects and the wildcard FQDN *.malicious-actor.example, while configuring a Cloud DNS outbound server policy with an alternative name server for external resolution.This configuration correctly separates the Google Threat Intelligence ingress rules for per-feed logging and places the exception IP allow rule at a higher priority, but it introduces two unsupported FQDN object configurations for outbound domain filtering: a wildcard domain pattern and an outbound DNS server policy with an alternative name server.
*) such as *.malicious-actor.example. Wildcard domain filtering is only supported at Layer 7 through Cloud NGFW Enterprise URL filtering security profiles.NXDOMAIN or unreachable DNS), Cloud NGFW ignores the FQDN object rather than failing closed.c2.malicious-actor.example instead of a wildcard, and the VPC network relied on standard Cloud DNS resolution without an outbound alternative name server policy.iplist-known-malicious-ips and iplist-tor-exit-nodes into a single high-priority ingress deny rule with a lower-priority ingress allow rule for 203.0.113.25/32, and configure an egress deny rule combining Non-internet network context with destination geolocation objects and c2.malicious-actor.example.This configuration attempts to consolidate Google Threat Intelligence feeds into one ingress rule, add an exception rule at a lower priority, and pair destination geolocation objects with a Non-internet network context in an egress rule.
iplist-tor-exit-nodes deny rule has a higher priority than the 203.0.113.25/32 allow rule, packets from the partner IP match the deny rule first and are dropped immediately.iplist-known-malicious-ips and iplist-tor-exit-nodes in a single rule prevents administrators from determining which threat intelligence feed caused a packet drop.Non-internet network context, so the egress rule configuration is invalid.Non-internet, VPC networks, or Inter-VPC contexts.Internet) is specified alongside other destination parameters, traffic must match the network context and at least one of the other destination parameters.Internet or All network contexts instead of Non-internet.203.0.113.25/32, separate lower-priority ingress deny rules for iplist-known-malicious-ips and iplist-tor-exit-nodes, and egress deny rules using Internet network context with destination geolocation objects and the exact FQDN c2.malicious-actor.example, ensuring the VPC does not use an outbound DNS server policy with an alternative name server.Cloud NGFW Standard extends foundational Layer 3 and Layer 4 firewalling with network-layer edge-filtering capabilities—Google Threat Intelligence lists, geolocation objects, and fully qualified domain name (FQDN) objects—evaluated directly within global, regional, or hierarchical firewall policy rules without requiring zonal firewall endpoints.
203.0.113.25/32 at a higher priority (lower integer) than the Google Threat Intelligence deny rules ensures legitimate partner traffic is permitted before matching iplist-tor-exit-nodes.iplist-known-malicious-ips and iplist-tor-exit-nodes into distinct rules makes logs unambiguously identify which threat feed triggered each block.Internet destination network context complies with Cloud NGFW rule-combination constraints. Using the exact two-label domain c2.malicious-actor.example allows Cloud NGFW to resolve the domain periodically and program up to 32 IPv4 and 32 IPv6 addresses into the data plane.iplist-known-malicious-ips and iplist-tor-exit-nodes) continuously update without manual CIDR maintenance.Unlike Essentials (which lacks FQDN, geolocation, and threat intelligence matching) and Enterprise (which deploys zonal Layer 7 firewall endpoints), this configuration uses only Cloud NGFW Standard features while respecting every rule-combination, priority, logging, and DNS constraint.
apply_security_profile_group action referencing a url-filtering security profile for c2.malicious-actor.example and a threat-prevention security profile for malicious IPs, while using VPC firewall rules with address groups for geolocation filtering.This configuration relies on Cloud NGFW Enterprise Layer 7 security profiles (url-filtering and threat-prevention) invoked via apply_security_profile_group, paired with Cloud NGFW Essentials legacy VPC firewall rules and address groups.
apply_security_profile_group with url-filtering or threat-prevention security profiles requires Cloud NGFW Enterprise, which mandates deploying Google-managed zonal firewall endpoints and incurs hourly endpoint charges plus per-gigabyte inspection fees.threat-prevention security profile performs Layer 7 signature-based intrusion detection and prevention (IPS) against payloads (anti-spyware, vulnerability protection, antivirus), rather than matching external IP feeds like Google Threat Intelligence (iplist-known-malicious-ips and iplist-tor-exit-nodes).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