nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #132

You are migrating a three-tier application architecture from on-premises to Google Cloud. As a first step in the migration, you want to create a new Virtual Private Cloud (VPC) with an external…

The correct answer is C. Create a Google Cloud Armor policy, and apply it to a backend service that uses an internet. Google Cloud Armor provides WAF capabilities (including XSS protection) by attaching security policies to backend services of an HTTP(S) Load Balancer. Because the presentation tier runs on on-premises resources (not GCP VMs), the load balancer backend must use an Internet…

Submitted by salim_om· Apr 18, 2026Implementing network security

Question

You are migrating a three-tier application architecture from on-premises to Google Cloud. As a first step in the migration, you want to create a new Virtual Private Cloud (VPC) with an external HTTP(S) load balancer. This load balancer will forward traffic back to the on-premises compute resources that run the presentation tier. You need to stop malicious traffic from entering your VPC and consuming resources at the edge, so you must configure this policy to filter IP addresses and stop cross-site scripting (XSS) attacks. What should you do?

Options

  • ACreate a Google Cloud Armor policy, and apply it to a backend service that uses an unmanaged
  • BCreate a hierarchical firewall ruleset, and apply it to the VPC's parent organization resource node.
  • CCreate a Google Cloud Armor policy, and apply it to a backend service that uses an internet
  • DCreate a VPC firewall ruleset, and apply it to all instances in unmanaged instance groups.

How the community answered

(23 responses)
  • A
    13% (3)
  • B
    9% (2)
  • C
    74% (17)
  • D
    4% (1)

Explanation

Google Cloud Armor provides WAF capabilities (including XSS protection) by attaching security policies to backend services of an HTTP(S) Load Balancer. Because the presentation tier runs on on-premises resources (not GCP VMs), the load balancer backend must use an Internet Network Endpoint Group (NEG), which is specifically designed to represent endpoints outside of Google Cloud. Option A is wrong because unmanaged instance groups contain GCP VM instances, not on-premises servers. Option B is wrong because hierarchical firewall rulesets operate at the network layer and do not provide WAF or XSS filtering capabilities. Option D is wrong because VPC firewall rules also lack WAF/XSS capabilities and apply only to GCP instances.

Topics

#Google Cloud Armor#External HTTP(S) Load Balancer#Internet Network Endpoint Group (NEG)#Web Application Firewall (WAF)

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice