Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization hosts a web application behind a global external Application Load Balancer with Cloud CDN enabled. You need to configure a Google Cloud Armor security policy that satisfies the following requirements:
198.51.100.0/24) and allow an authorized vulnerability scanner (203.0.113.10/32) unfiltered access.Which security policy configuration should you implement?
CLOUD_ARMOR) attached to the backend service with rules ordered as: deny 198.51.100.0/24 (deny-403) at priority 100; allow 203.0.113.10/32 (allow) at priority 200; evaluate sqli-v422-canary, xss-v422-canary, and rfi-v422-canary with deny-403 in preview mode at priority 300; evaluate sqli-v422-stable, xss-v422-stable, and rfi-v422-stable with {'sensitivity': 1} and deny-403 at priority 400; and set the default rule (2147483647) to allow.A Google Cloud Armor backend security policy (CLOUD_ARMOR) is a Layer 3 through Layer 7 traffic-filtering policy attached directly to an external Application Load Balancer's backend service. It evaluates incoming HTTP(S) requests—including cache misses and dynamic origin traffic when Cloud CDN is enabled—against prioritized rules using preconfigured WAF expressions (evaluatePreconfiguredWaf()) derived from the OWASP ModSecurity Core Rule Set (CRS) 4.22.
sqli-v422-stable, xss-v422-stable, and rfi-v422-stable with {'sensitivity': 1} enforces only the highest-confidence attack signatures rather than the default sensitivity level of 4, dramatically reducing noise on legitimate application payloads.0 is highest priority), placing the explicit IP deny (100) first blocks known attackers immediately, while placing the trusted scanner allow (200) second permits 203.0.113.10/32 to bypass downstream WAF inspection (300 and 400). Leaving intervals of 100 between rules allows future rule insertions without renumbering.-v422-canary rules in preview mode at a higher priority (300) than the enforced -v422-stable rules (400) logs matches from newly released CRS signatures for analysis without dropping live production traffic.2147483647) to allow permits all traffic that passes both IP filtering and WAF inspection.deny-403 works reliably across both the header and body processing phases.stable.This configuration follows Google Cloud's recommended security policy hierarchy—explicit denies, trusted explicit allows, canary preview WAF rules, enforced sensitivity-tuned stable WAF rules, and a default allow—ensuring deterministic evaluation and safe operational scaling.
CLOUD_ARMOR_EDGE) attached to the backend service with rules ordered as: deny 198.51.100.0/24 (deny-403) at priority 100; allow 203.0.113.10/32 (allow) at priority 200; evaluate sqli-v422-canary, xss-v422-canary, and rfi-v422-canary in preview mode at priority 300; evaluate sqli-v422-stable, xss-v422-stable, and rfi-v422-stable with {'sensitivity': 1} and deny-403 at priority 400; and set the default rule (2147483647) to allow.A Cloud Armor edge security policy (CLOUD_ARMOR_EDGE) is a perimeter filtering policy enforced upstream of the Cloud CDN cache at the outermost edge of Google's network. It is designed to control access to cached content on Cloud CDN-enabled backend services and Cloud Storage backend buckets before a request ever reaches the cache layer.
evaluatePreconfiguredWaf() rules or perform request body inspection. Attempting to deploy SQLi, XSS, or RFI preconfigured rule sets inside a CLOUD_ARMOR_EDGE policy is unsupported.origin.asn, origin.ip, origin.region_code, request.headers, request.method, request.path, request.query, and request.scheme.The requirement was solely to enforce IP-based, ASN-based, or geographic access controls (origin.ip, origin.region_code) or simple path blocking before requests hit the Cloud CDN cache or a Cloud Storage backend bucket.
When protecting a Cloud CDN-enabled application against OWASP Top 10 injection attacks, an edge security policy can optionally block malicious IPs upstream of the cache, but a backend security policy (CLOUD_ARMOR) is mandatory to run preconfigured WAF rules against origin-bound requests.
CLOUD_ARMOR) attached to the backend service with rules ordered as: deny 198.51.100.0/24 (deny-403) at priority 100; allow 203.0.113.10/32 (allow) at priority 200; evaluate sqli-v422-canary, xss-v422-canary, and rfi-v422-canary with redirect in preview mode at priority 300; evaluate sqli-v422-stable, xss-v422-stable, and rfi-v422-stable with a redirect action to a custom block URL at priority 400; and set the default rule (2147483647) to allow.redirect Action and Default Sensitivity DoIn Google Cloud Armor, the redirect action sends an HTTP 302 redirect to a configured external URL or a reCAPTCHA challenge, while leaving evaluatePreconfiguredWaf() without a sensitivity argument enables all signatures at sensitivity level 4.
redirect Behavior During Body Inspection: Cloud Armor processes HTTP headers before the request body. The redirect action works only during the header processing phase. When a preconfigured WAF rule matches a SQLi, XSS, or RFI payload inside the request body (such as a POST form or JSON payload), Cloud Armor translates the redirect action into a standard deny action rather than redirecting the client to the custom block URL.{'sensitivity': 1} leaves the CRS 4.22 rules at sensitivity level 4, which includes aggressive, lower-confidence signatures that routinely trigger false positives on production traffic.redirect and custom header insertion actions cannot take effect during the body phase.1–4): Sensitivity level 1 maps to OWASP CRS paranoia level 1 (highest fidelity, lowest noise), whereas level 4 evaluates all available signatures.deny-403 (or deny-404 / deny-502), which operates consistently regardless of whether the attack appears in a URL query string, header, or request body.The redirect action were replaced with deny-403 and the -v422-stable rules were explicitly configured with {'sensitivity': 1} to minimize false positives.
The redirect action is primarily intended for bot management (such as routing suspicious clients to a reCAPTCHA challenge or alternate URL based on headers or IP attributes), not for mitigating Layer 7 injection payloads inside HTTP request bodies.
CLOUD_ARMOR) attached to the backend service with rules ordered as: evaluate sqli-v422-stable, xss-v422-stable, and rfi-v422-stable with deny-403 at priority 100; evaluate sqli-v422-canary, xss-v422-canary, and rfi-v422-canary in preview mode at priority 200; deny 198.51.100.0/24 (deny-403) at priority 300; allow 203.0.113.10/32 (allow) at priority 400; and set the default rule (2147483647) to allow.This configuration uses the correct policy type (CLOUD_ARMOR) and CRS 4.22 rule sets, but it inverts the rule evaluation hierarchy and omits sensitivity tuning. In Cloud Armor, rules are processed strictly from the lowest numeric priority to the highest, stopping as soon as an enforced rule matches.
allow rule sits at priority 400, any attack payload sent by 203.0.113.10/32 matches priority 100 first and is immediately blocked with HTTP 403—never reaching priority 400.stable enforced rules (100) ahead of canary preview rules (200) prevents requests caught by existing stable signatures from ever being logged against the canary rule set, and fails to isolate new signature testing prior to enforcement.allow or deny rule evaluates to true, all subsequent lower-priority rules (higher numeric values) are skipped.2147483647) last.The numeric priorities were reordered so the explicit IP deny (100) and trusted scanner allow (200) precede the canary preview WAF rules (300) and sensitivity-1 stable WAF rules (400).
Even when the malicious IP 198.51.100.0/24 sends non-WAF flood traffic, placing its deny rule below the WAF rules at priority 300 forces unnecessary WAF signature evaluation on traffic that should be dropped immediately at priority 100.
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 Validated