
Google Cloud Armor security policies attach to the backend services of an Application Load Balancer. With a global external Application Load Balancer, client connections end at Google Front Ends on the edge of Google's network, and that is where Cloud Armor evaluates each request. A policy sees the original client IP address and can drop unwanted requests before they reach your instances or use any backend capacity. The Professional Cloud Network Engineer exam tests where that enforcement point sits, which load balancers a policy can attach to, which kinds of attack each rule type handles, and what falls outside Cloud Armor entirely.
A single security policy can combine several kinds of rules:
These rules work together on the same backend service, so one policy can restrict sources and inspect requests for attack patterns at the same time.
Different floods are handled at different layers. Network and protocol floods, such as SYN floods and UDP floods, are absorbed by the always-on network and protocol DDoS protection that comes with the global external Application Load Balancer and Cloud Armor.
HTTP request floods are different, because each request is valid layer 7 traffic. Handling them is the job of a Cloud Armor rate limiting rule, which acts on clients that send too many requests.
Cloud Armor can also protect web servers that are not in Google Cloud. A global external Application Load Balancer can reach servers that still sit in a data center through a backend service that uses an internet network endpoint group, and a Cloud Armor policy on that backend service filters requests at the edge before they reach those servers.
Cloud Armor Standard backend security policies work without a Cloud Armor Enterprise subscription, but they only attach to backend services of proxy-based load balancers, such as the global external Application Load Balancer. A Standard policy therefore needs one of those backend services to exist before it can filter anything.
Passthrough Network Load Balancers are covered by two other features, advanced network DDoS protection and network edge security policies, and both need Cloud Armor Enterprise. The type of load balancer in front of a workload is part of the Cloud Armor design, since it decides whether a Standard backend policy can be used at all.
Cloud Armor only applies to traffic arriving at load balancers, so it has no role in traffic that VMs start toward the internet, such as calls to a vendor API. Other controls work at different points:
For the Professional Cloud Network Engineer exam, we would place Cloud Armor by its attachment point: Standard backend security policies on the backend services of proxy-based load balancers, enforced at the edge with the original client IP in view, and Enterprise features where a passthrough Network Load Balancer needs protection.
Our Professional Cloud Network Engineer practice exams cover Google Cloud Armor security policies alongside rate limiting and VPC Service Controls, with detailed explanations that drill these distinctions.