CLOUD-NETWORK practice question 15 of 30

Your organization has a subset of applications in multiple regions that require internet access. You need to control internet access from applications to URLs, including hostnames and paths. The compute instances that run these applications have an associated secure tag. What should you do?

Full set: 233 questions
Answer options
A: Deploy a Cloud NAT gateway. Use fully qualified domain name (FQDN) objects in the firewall policy rules to filter outgoing traffic to specific domains from machines that match the secure tag.
B: Deploy a single Secure Web Proxy instance with global access enabled. Apply a Secure Web Proxy policy to allow access from machines that match the secure tag to the URLs defined in a URL list. Correct answer
C: Deploy a Secure Web Proxy instance in each region. Apply a Secure Web Proxy policy to allow access from machines that match the secure tag to the URLs defined in a URL list.
D: Deploy a Cloud NAT gateway. Use fully qualified domain name (FQDN) objects in the firewall policy rules to filter outgoing traffic to specific domains from machines that match a service account.
Correct Answer:
B. Deploy a single Secure Web Proxy instance with global access enabled. Apply a Secure Web Proxy policy to allow access from machines that match the secure tag to the URLs defined in a URL list.
Explanation

Secure Web Proxy is the Google Cloud service designed for granular, policy-based control over web egress traffic, including filtering by full URLs (hostnames and paths). A single Secure Web Proxy instance can be configured with global access, allowing it to serve instances from multiple regions, which simplifies policy management. Policies can be applied based on secure tags associated with the source compute instances, allowing access to predefined URL lists. This solution directly meets all requirements: multi-region support, URL path filtering, and control based on secure tags, in a centrally managed and efficient manner.

Why Incorrect

A. Cloud NAT provides internet egress but lacks URL path filtering capabilities. Firewall FQDN objects only filter based on domain names, not the full URL path.
C. While deploying a Secure Web Proxy instance in each region is a valid architecture, it is less efficient to manage than a single global instance for a unified policy.
D. This option has the same limitation as A (no URL path filtering) and incorrectly suggests using a service account for filtering instead of the specified secure tag.

References

1. Google Cloud Documentation, "Secure Web Proxy overview". It states, "Secure Web Proxy is a cloud-native service that helps you secure your web outbound traffic... You can create granular policies based on cloud-native constructs such as secure tags."

2. Google Cloud Documentation, "Create and deploy proxies", Section: "Proxy scope". This section describes the "globalaccess" option, which "lets you deploy a proxy in one region and use it to access resources from any region."

3. Google Cloud Documentation, "Create Secure Web Proxy policies", Section: "Session matcher". This section explains that session matchers use CEL expressions, which can include source.matchTag('SECURETAG').

4. Google Cloud Documentation, "Create Secure Web Proxy policies", Section: "URL lists". This section describes how to create lists of URLs to be used in security policies for allow or deny actions.

Scroll to Top