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.
A security engineering team is deploying a Google Cloud Armor security policy for a global external Application Load Balancer whose backend service serves both a JSON REST API and a browser-based /login portal. Legitimate users connect through an upstream reverse proxy that populates the X-Forwarded-For header, whereas corporate administrators access /admin endpoints directly from 203.0.113.0/24.
The team must enforce the following Layer 7 protections:
/admin access (including mixed-case and URL-encoded variations such as /a%64min) to 203.0.113.0/24, while ensuring permitted corporate requests still undergo WAF inspection./login based on their original client IP, and redirect suspicious /login requests to a reCAPTCHA challenge.Which Cloud Armor security policy configuration should the team implement?
CLOUD_ARMOR backend security policy attached to the backend service with default body inspection settings. Add a deny-403 rule matching request.path.matches('^/admin') && !inIpRange(origin.ip, '203.0.113.0/24'), a throttle rule on /login with --enforce-on-key=TLS_JA4_FINGERPRINT, a header-matched redirect (GOOGLE_RECAPTCHA) rule for suspicious /login traffic, and place evaluatePreconfiguredWaf('sqli-v422-canary') in preview mode at a lower priority than evaluatePreconfiguredWaf('sqli-v422-stable').A regionally scoped Cloud Armor backend security policy enforces Layer 7 security rules for regional backend services exposed by regional external Application Load Balancers or regional internal Application Load Balancers to satisfy regional data residency or isolation requirements.
TLS_JA4_FINGERPRINT, and using a TLS fingerprint does not enforce rate limits by the original client IP forwarded in X-Forwarded-For (XFF_IP).throttle rule caps request rates without temporarily banning repeat offenders unless a rate_based_ban action (or ban configuration) is used.request.path.matches('^/admin') without urlDecode() and backslash handling (such as r'^/\\*admin') leaves /admin vulnerable to encoding and backslash bypasses, while omitting JSON parsing causes false positives on JSON payloads.canary in preview mode at a lower priority than stable prevents preview logs from evaluating requests already blocked by stable.rate_based_ban, it cannot be converted to throttle, though throttle can later be upgraded to rate_based_ban.The workload used a regional external Application Load Balancer with JA3 or XFF_IP rate-based banning, JSON parsing enabled, normalized path matching, and higher-priority canary preview rules.
Match the security policy's scope (global versus --region) to the load balancer's backend service scope before attaching the policy.
CLOUD_ARMOR backend security policy attached to the backend service using default body inspection settings. Add a priority 100 allow rule for 203.0.113.0/24, a priority 110 deny-403 rule matching request.path.lower().urlDecode().startsWith('/admin'), a rate_based_ban rule on /login with --enforce-on-key=IP, a redirect (GOOGLE_RECAPTCHA) rule matching evaluatePreconfiguredWaf('sqli-v422-stable'), and place sqli-v422-canary in preview mode at priority 300 below sqli-v422-stable at priority 200.This configuration correctly selects a globally scoped CLOUD_ARMOR backend security policy and normalizes /admin paths, but introduces critical flaws in body parsing, rule processing phases, rule ordering, and rate-limiting keys.
redirect (GOOGLE_RECAPTCHA) only work during the header processing phase; when a redirect rule matches during the body processing phase (such as evaluatePreconfiguredWaf inspecting a JSON POST body), Cloud Armor converts the redirect into a deny action.100 allow rule for 203.0.113.0/24 stops rule evaluation immediately, exempting corporate requests from all lower-priority WAF rules.--enforce-on-key=IP groups all proxied users under the reverse proxy's IP address instead of using XFF_IP. Additionally, placing canary at priority 300 (lower priority) behind enforced stable at priority 200 prevents canary from previewing traffic already blocked by stable.302 or reCAPTCHA redirects.allow rules act as terminal actions that skip subsequent security rules.JSON parsing were enabled, the /admin check used a single negated deny rule, rate limiting used XFF_IP, redirect matched header attributes rather than body WAF rules, and canary preview had higher priority (lower number) than stable.
Always verify whether a rule inspects headers or payloads when pairing rules with redirect or custom header insertion actions.
CLOUD_ARMOR backend security policy attached to the backend service with JSON parsing enabled. Add a high-priority deny-403 rule matching request.path.lower().urlDecode().startsWith('/admin') && !inIpRange(origin.ip, '203.0.113.0/24'), a rate_based_ban rule on /login with --enforce-on-key=XFF_IP, a header-matched redirect (GOOGLE_RECAPTCHA) rule for suspicious /login traffic, and place evaluatePreconfiguredWaf('sqli-v422-canary') in preview mode at a higher priority (lower number) than an enforced evaluatePreconfiguredWaf('sqli-v422-stable') rule.A globally scoped Cloud Armor backend security policy (type=CLOUD_ARMOR) attaches directly to the backend service of a global external Application Load Balancer to provide full Layer 3 through Layer 7 inspection, preconfigured Web Application Firewall (WAF) rulesets, rate limiting, and bot management at Google's network edge.
evaluatePreconfiguredWaf('sqli-v422-stable'), preventing unparsed JSON syntax characters (such as quotes and braces) from triggering false positives./admin restriction with continued WAF evaluation: Combining request.path.lower().urlDecode().startsWith('/admin') with && !inIpRange(origin.ip, '203.0.113.0/24') in a single deny-403 rule blocks case-altered and percent-encoded paths like /Admin or /a%64min from untrusted IPs. Because corporate requests from 203.0.113.0/24 do not match the deny condition, evaluation continues to lower-priority WAF rules instead of short-circuiting.rate_based_ban action with --enforce-on-key=XFF_IP tracks request rates using the first IP address in the X-Forwarded-For header and temporarily bans abusive clients. Matching suspicious /login requests on header attributes allows the redirect (GOOGLE_RECAPTCHA) action to execute during the header processing phase, before body inspection occurs.evaluatePreconfiguredWaf('sqli-v422-canary') in preview mode at a higher logical priority (lower numeric value) than the enforced sqli-v422-stable rule logs matches from upcoming CRS updates without blocking live traffic.XFF_IP.This configuration correctly aligns policy scope, evaluation order, header-vs-body processing phases, and path normalization so every security control operates without bypassing downstream protections or causing proxy-wide lockouts.
CLOUD_ARMOR_EDGE edge security policy attached to the backend service. Add a priority 100 allow rule for 203.0.113.0/24 followed by a priority 110 deny-403 rule matching request.path.startsWith('/admin'), a throttle rule with --enforce-on-key=IP, and place evaluatePreconfiguredWaf('sqli-v422-canary') in preview mode at a lower priority (higher number) than an enforced evaluatePreconfiguredWaf('sqli-v422-stable') rule.A Cloud Armor edge security policy (CLOUD_ARMOR_EDGE) filters requests at the outermost perimeter of Google's network, upstream of the Cloud CDN cache, for Cloud CDN-enabled backend services and Cloud Storage backend buckets behind a global external Application Load Balancer.
Allow and Deny actions across a restricted attribute subset (origin.asn, origin.ip, origin.region_code, request.headers, request.method, request.path, request.query, and request.scheme). They do not support preconfigured WAF rules (evaluatePreconfiguredWaf), body filtering, rate limiting (throttle or rate_based_ban), or bot management (GOOGLE_RECAPTCHA).allow rule at priority 100 for 203.0.113.0/24 immediately terminates rule evaluation for matching corporate traffic, bypassing all lower-priority security rules.request.path.startsWith('/admin') without .lower().urlDecode() allows attackers to bypass the rule using mixed-case (/Admin) or URL-encoded (/a%64min) paths.canary at a lower priority (higher number) than stable prevents preview logs from capturing requests already matched by stable, while --enforce-on-key=IP counts all requests under the upstream proxy's IP instead of XFF_IP.The team only needed coarse IP, ASN, or geographic allow/deny filtering in front of a Cloud CDN cache or Cloud Storage backend bucket, rather than WAF inspection, rate-based bans, and reCAPTCHA bot management.
When both an edge security policy and a backend security policy are attached to the same backend service, the edge policy filters cache hits and misses first, and the backend security policy inspects cache misses and dynamic requests.
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