Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise hosts an e-commerce platform behind an external Application Load Balancer with an attached Google Cloud Armor security policy. The security engineering team has the following access and threat protection requirements for a backend service:
198.51.100.0/24 to access administrative endpoints matching request.path.matches('/admin/.*') without being blocked by general WAF inspection./admin/.*.sqli-v33-stable) and Cross-Site Scripting (xss-v33-stable), denying matched exploits.How should the Cloud Armor security policy rules and priorities be configured to enforce these requirements correctly?
Priority 1000: Allow corporate admin CIDR and /admin/.* path.
Priority 2000: Deny requests matching preconfigured SQLi and XSS WAF expressions.
Priority 3000: Allow all general customer traffic.
Default Rule (2147483647): Deny all requests matching /admin/.*.
This configuration places an unconditional allow rule for all general traffic at Priority 3000 and attempts to place an administrative path deny condition in the Default Rule.
2147483647) evaluates match condition * (all traffic). It cannot be configured with custom Layer 7 match expressions such as request.path.matches('/admin/.*').* with a simple allow or deny action.Cloud Armor evaluated security policies in parallel using a most-specific-match algorithm rather than sequential first-match priority order.
Priority 1000: Allow corporate admin CIDR and /admin/.* path.
Priority 2000: Deny all other requests matching /admin/.*.
Priority 3000: Deny requests matching preconfigured SQLi and XSS WAF expressions.
Default Rule (2147483647): Allow all traffic.
Google Cloud Armor security policies are edge enforcement controls attached to backend services on external Application Load Balancers. They evaluate incoming HTTP(S) requests using priority-based rule evaluation where integer values range from 0 to 2147483646 (with the mandatory default rule fixed at 2147483647). Rules are evaluated in ascending numerical order (lowest priority number evaluated first). When a rule's match condition evaluates to true, Cloud Armor immediately executes the configured action (allow, deny, or throttle) and stops processing further rules.
inIpRange(origin.ip, '198.51.100.0/24') and the L7 path expression request.path.matches('/admin/.*') is explicitly granted an allow action. Because rule evaluation terminates upon the first match, authorized administrative traffic bypasses downstream WAF evaluations.request.path.matches('/admin/.*') is intercepted and denied (HTTP 403/404), ensuring unauthorized clients cannot access administrative endpoints.evaluatePreconfiguredExpr('sqli-v33-stable') || evaluatePreconfiguredExpr('xss-v33-stable')). Malicious payloads are blocked.Priority 1000: Deny requests matching preconfigured SQLi and XSS WAF expressions.
Priority 2000: Allow corporate admin CIDR and /admin/.* path.
Priority 3000: Deny all requests matching /admin/.*.
Default Rule (2147483647): Allow all traffic.
This configuration evaluates preconfigured WAF rules (SQLi and XSS) at Priority 1000, ahead of the corporate administrative allowlist at Priority 2000 and general administrative block at Priority 3000.
/admin/.* console, Priority 1000 triggers and blocks legitimate administrative operations.The organization mandated that all corporate administrative actions undergo full WAF payload sanitization and inspection prior to path access verification.
Priority 1000: Deny all requests matching /admin/.*.
Priority 2000: Allow corporate admin CIDR matching 198.51.100.0/24.
Priority 3000: Deny requests matching preconfigured SQLi and XSS WAF expressions.
Default Rule (2147483647): Allow all traffic.
This configuration places a broad Layer 7 path restriction at Priority 1000 before the corporate IP allowlist rule at Priority 2000.
/admin/.* immediately match Priority 1000 and are denied.The requirement was to completely disable and block all external administrative routes across all subnets, including corporate office IP addresses.
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