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 runs a public web application behind a global external Application Load Balancer on Google Cloud. The security team needs to configure a Google Cloud Armor security policy to meet the following requirements:
Which Google Cloud Armor capability should the company use?
Google Threat Intelligence in Google Cloud Armor is an enterprise capability that allows or blocks incoming traffic based on continuously updated threat intelligence data feeds—such as Tor exit nodes, VPN providers, known malicious IP addresses, or public cloud IP ranges—using the evaluateThreatIntelligence() match expression.
evaluateThreatIntelligence() match condition.The security team wanted to automatically block incoming requests originating from known Tor exit nodes, anonymous VPN providers, or compromised IP addresses tracked by threat intelligence feeds.
Google Threat Intelligence complements preconfigured WAF rules in a defense-in-depth architecture: Threat Intelligence blocks traffic from high-risk network origins upfront, while preconfigured WAF rules inspect the remaining requests for OWASP Top 10 vulnerabilities.
Always-on Layer 3 and Layer 4 volumetric DDoS protection is Google Cloud Armor's built-in, automatic defense mechanism that detects and mitigates large-scale network and transport protocol-based distributed denial-of-service (DDoS) attacks at the edge of Google's network.
The scenario asked how Google Cloud Armor automatically protects applications behind an external Application Load Balancer from large-scale network and protocol-based volumetric DDoS floods in real time without requiring manual policy configuration.
A complete cloud defense strategy pairs Cloud Armor's automatic L3/L4 volumetric DDoS protection with user-configured Layer 7 security policies containing preconfigured WAF rules to protect both the network infrastructure and the web application code.
IP address allowlists and denylists are access control rules within a Google Cloud Armor security policy that permit or reject incoming requests based exclusively on the client's source IP address or Classless Inter-Domain Routing (CIDR) range.
origin.ip), not the contents of the HTTP request headers, URL parameters, or body. They cannot detect SQL injection (SQLi) or cross-site scripting (XSS) attack strings.deny rule.The organization needed to restrict an internal application so that only users connecting from specific corporate branch office IP ranges could access it, or needed to block all requests coming from a known malicious IP address.
While IP lists alone cannot detect SQLi or XSS attacks across public traffic, administrators can combine IP range conditions with preconfigured WAF rules in a single custom expression—for example, enforcing specific WAF checks on traffic originating from a particular subnet.
Google Cloud Armor preconfigured WAF rules are ready-to-use, complex Web Application Firewall (WAF) rule sets built on open-source industry standards—specifically the OWASP ModSecurity Core Rule Set (CRS). Each preconfigured rule bundles dozens of distinct attack detection signatures under a single, convenient rule name (such as sqli-v422-stable or xss-v422-stable).

Unlike network-layer DDoS protections or basic IP filtering, preconfigured WAF rules inspect actual Layer 7 application payloads for code injection attempts while removing the burden of writing and maintaining complex custom regular expressions from scratch.
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