Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An e-commerce company is preparing for a major seasonal promotion. Leadership is concerned that malicious actors might use thousands of compromised external devices to flood their website with overwhelming traffic, rendering the application unavailable to legitimate shoppers.
The company wants to use Google Cloud Armor to defend against this type of threat without exhausting compute resources inside their Virtual Private Cloud (VPC).
How does Google Cloud Armor leverage Google's infrastructure to protect the application?
Google Cloud Armor is a network security and distributed denial-of-service (DDoS) mitigation service built on top of Google's global infrastructure and frontend load balancing systems. In a DDoS attack, malicious actors utilize numerous compromised hosts (often referred to as a botnet) to flood a target with overwhelming volumes of traffic, attempting to exhaust resources and render the application unavailable to legitimate users. Cloud Armor defends against these threats by operating at the network edge, positioning security controls as close to the source of the incoming traffic as possible.
SYN floods) inline and in real time without adding latency.
Stopping a volumetric DDoS attack requires having greater network capacity than the attacker and dropping bad traffic before it hits narrow network bottlenecks. Intercepting threats at Google's global network edge neutralizes attacks at the perimeter rather than straining internal virtual networks or application servers.
Routing traffic directly to backend Virtual Machine (VM) instances relies on the compute and network capacity of individual servers inside a Virtual Private Cloud (VPC) to process, inspect, and drop unwanted network packets using local host firewalls or operating system resources.
The fundamental goal of a Distributed Denial of Service (DDoS) attack is to exhaust the target's bandwidth, CPU, and memory so legitimate users cannot connect. If Google Cloud Armor allowed massive volumes of attack traffic to enter the VPC network and reach backend VMs, the attack would succeed. The sheer volume of malicious packets would saturate internal network links and overwhelm the backend servers just trying to inspect and drop the traffic, leading to complete service unavailability.
This approach would only apply if an organization were inspecting trusted, low-volume internal east-west traffic between virtual machines inside a VPC using host-based intrusion detection agents, rather than defending public-facing endpoints against external volumetric DDoS attacks at the network perimeter.
VPC Network Peering is a networking feature that allows private connectivity between two separate Virtual Private Cloud networks (such as connecting a customer VPC to a Google-managed tenant project). Cloud CDN (Content Delivery Network) uses Google's globally distributed edge points of presence to cache static web and video content closer to end users to reduce latency and offload origin servers.
In a Distributed Denial of Service (DDoS) attack, traffic is generated by thousands of untrusted, compromised external devices across the public internet. A cloud provider never establishes a private VPC peering connection with malicious external attackers. Furthermore, Cloud CDN is designed to serve valid cached content to legitimate users, not to act as a storage vault for malicious DDoS payloads. In fact, attackers often attempt cache-busting attacks to bypass the CDN cache and overload the backend origin server.
These technologies would be relevant in two separate, legitimate architectural scenarios: using VPC Network Peering to privately connect a customer VPC with a Google-managed Apigee tenant project, or using Cloud CDN alongside Cloud Armor to serve static website assets from edge caches while filtering out cache-busting requests.
In Google Cloud Armor, administrators can manually configure custom security policies using match conditions, IP address lists, geographic controls, and Web Application Firewall (WAF) rules to filter specific types of incoming application requests.
While manual rules are used to customize Layer 7 (application layer) filtering, Cloud Armor does not rely on manual human intervention to stop Layer 3 and Layer 4 volumetric DDoS attacks. Network and protocol-based volumetric floods happen rapidly and at a massive scale that humans cannot manually react to in real time. Instead, Cloud Armor provides always-on, automated inline mitigation for L3 and L4 attacks out of the box for applications behind external load balancers.
UDP or SYN floods) is built-in, continuous, and requires zero manual configuration.This concept would apply if the scenario asked how an administrator enforces custom Layer 7 access controls—such as blocking requests to a specific /admin URL path or restricting access based on specific IP ranges—which requires defining explicit rules in a Cloud Armor security policy.
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