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.
An e-commerce application behind a global external Application Load Balancer uses Google Cloud Armor Enterprise and two reCAPTCHA WAF keys: an action-token key (checkout-action-key) with action checkout, and a challenge-page key (checkout-challenge-key). The checkout-policy default rule is set to allow.
You must protect /checkout with the following requirements:
>= 0.8 while rate-limiting token reuse.0.5 up to 0.8 to a reCAPTCHA challenge page unless a rate-limited exemption cookie is valid./checkout requests, including scores < 0.5, missing/expired tokens, falsified actions, and unauthorized keys.Which configuration and rule order (lowest to highest priority number) should you implement?
Associate checkout-challenge-key with checkout-policy using --recaptcha-redirect-site-key. Then create rules in this order:
throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-HEADER, enforce_on_key_name: X-Recaptcha-Token): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.8 with --recaptcha-action-site-keys="checkout-action-key".throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-COOKIE, enforce_on_key_name: recaptcha-ca-e): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 && token.recaptcha_exemption.valid with --recaptcha-action-site-keys="checkout-action-key".redirect, --redirect-type google-recaptcha): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 with --recaptcha-action-site-keys="checkout-action-key".deny-403): Match request.path.matches('/checkout').This configuration establishes a complete, multi-tiered Google Cloud Armor bot management pipeline combining reCAPTCHA action-token scoring, manual challenge fallback, token/cookie rate limiting, and cryptographic key and action binding at the network edge.
/checkout with a valid action-token (token.recaptcha_action.valid), matching action (token.recaptcha_action.action == 'checkout'), authorized site key (--recaptcha-action-site-keys="checkout-action-key"), and score >= 0.8 are allowed up to the rate threshold, keyed per token via HTTP-HEADER X-Recaptcha-Token.0.5 and 0.8 first hit Priority 1010; if the client already holds a valid exemption cookie (token.recaptcha_exemption.valid), the request is allowed and rate-limited on HTTP-COOKIE recaptcha-ca-e. Otherwise, evaluation continues to Priority 1020, which redirects the client (--redirect-type google-recaptcha) using the policy-associated checkout-challenge-key./checkout traffic (Priority 1030): Because Cloud Armor reCAPTCHA subexpressions evaluate to false for missing, expired, malformed, or mismatched-key tokens, placing an unconditional path match (request.path.matches('/checkout')) with deny-403 at Priority 1030 ensures bots without valid tokens or with scores below 0.5 cannot fall through to the policy's default allow rule.--recaptcha-action-site-keys forces Cloud Armor to reject tokens from unauthorized keys, while verifying token.recaptcha_action.action stops attackers from replaying tokens generated on other pages.X-Recaptcha-Token) and per-exemption-cookie (recaptcha-ca-e) throttling prevent automated scripts from reusing a single valid token or solved challenge across hundreds of carding attempts.Unlike relying on score < 0.5 deny expressions (which fail open when tokens are omitted), inverting the redirect/exemption priorities, or using external-302 redirects, this exact rule sequence enforces fail-closed security on /checkout while keeping the rest of the site accessible.
Associate checkout-challenge-key with checkout-policy using --recaptcha-redirect-site-key. Then create rules in this order:
throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-HEADER, enforce_on_key_name: X-Recaptcha-Wafdata): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.8 with --recaptcha-action-site-keys="checkout-action-key".throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-COOKIE, enforce_on_key_name: recaptcha-ca-e): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 && token.recaptcha_action.captcha_status == 'PASS' with --recaptcha-action-site-keys="checkout-action-key".redirect, --redirect-type external-302 --redirect-target "https://www.google.com/recaptcha/"): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 with --recaptcha-action-site-keys="checkout-action-key".deny-403): Match request.path.matches('/checkout').This configuration attempts to implement the tiered bot defense workflow with proper priority ordering and key binding, but misconfigures three Cloud Armor bot management mechanics: the action-token rate-limiting header, the exemption cookie evaluation attribute, and the redirect action type.
X-Recaptcha-Wafdata): Clients attach generated action-tokens to the X-Recaptcha-Token request header. X-Recaptcha-Wafdata is the metadata header populated with decoded score information for downstream inspection, so throttling on X-Recaptcha-Wafdata fails to rate-limit individual client action-tokens.captcha_status): The attribute token.recaptcha_action.captcha_status (NONE, PASS, or FAIL) reflects whether a checkbox challenge occurred when the original action-token was minted—it does not inspect the exemption cookie (recaptcha-ca-e) issued by the reCAPTCHA challenge page interstitial. Only token.recaptcha_exemption.valid checks for a valid exemption cookie.external-302): Using --redirect-type external-302 sends a generic HTTP 302 redirect to an external URL and never invokes Cloud Armor's integrated reCAPTCHA interstitial assessment or issues an exemption cookie.--redirect-type google-recaptcha to serve the interstitial challenge page and issue the recaptcha-ca-e exemption cookie using the policy's --recaptcha-redirect-site-key.X-Recaptcha-Token, making it the required enforce_on_key_name for action-token rate limiting.X-Recaptcha-Token, Priority 1010 checked token.recaptcha_exemption.valid instead of captcha_status == 'PASS', and Priority 1020 used --redirect-type google-recaptcha.Associate checkout-challenge-key with checkout-policy using --recaptcha-redirect-site-key. Then create rules in this order:
throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-HEADER, enforce_on_key_name: X-Recaptcha-Token): Match request.path.matches('/checkout') && token.recaptcha_action.score >= 0.8.throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-COOKIE, enforce_on_key_name: recaptcha-ca-e): Match request.path.matches('/checkout') && token.recaptcha_action.score >= 0.5 && token.recaptcha_exemption.valid.redirect, --redirect-type google-recaptcha): Match request.path.matches('/checkout') && token.recaptcha_action.score >= 0.5.deny-403): Match request.path.matches('/checkout') && token.recaptcha_action.score < 0.5.This configuration uses the proper priority order and rate-limiting keys (X-Recaptcha-Token and recaptcha-ca-e), but introduces severe security bypasses by checking token.recaptcha_action.score < 0.5 in the deny rule and omitting both site key binding and action name verification.
false when the token is missing, malformed, or expired. Consequently, if a bot sends a /checkout request with no X-Recaptcha-Token header or an expired token, token.recaptcha_action.score < 0.5 at Priority 1030 returns false. The request then falls through to the policy's default allow rule, completely bypassing protection.--recaptcha-action-site-keys="checkout-action-key", Cloud Armor does not verify which reCAPTCHA key issued the token, allowing attackers to substitute tokens minted from another site or application.token.recaptcha_action.action == 'checkout', an attacker can capture a high-scoring action-token from a low-risk action (such as homepage_view) and replay it against /checkout.false on absent or invalid tokens, negative score comparisons (score < 0.5) cannot catch unauthenticated or malformed bot requests.allow, the final rule protecting a sensitive path must match purely on request.path rather than token attributes.request.path.matches('/checkout') unconditionally, and Priorities 1000–1020 included token.recaptcha_action.valid, token.recaptcha_action.action == 'checkout', and --recaptcha-action-site-keys="checkout-action-key".Associate checkout-challenge-key with checkout-policy using --recaptcha-redirect-site-key. Then create rules in this order:
throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-HEADER, enforce_on_key_name: X-Recaptcha-Token): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.8 with --recaptcha-action-site-keys="checkout-action-key".redirect, --redirect-type google-recaptcha): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 with --recaptcha-action-site-keys="checkout-action-key".throttle, conform allow, exceed deny-429, enforce_on_key: HTTP-COOKIE, enforce_on_key_name: recaptcha-ca-t): Match request.path.matches('/checkout') && token.recaptcha_action.valid && token.recaptcha_action.action == 'checkout' && token.recaptcha_action.score >= 0.5 && token.recaptcha_exemption.valid with --recaptcha-action-site-keys="checkout-action-key".deny-403): Match request.path.matches('/checkout').This configuration correctly binds both the challenge-page key and the action-token key, validates the checkout action name, and ends with a catch-all deny rule for /checkout. However, it breaks the challenge exemption workflow through rule priority inversion and specifies the wrong cookie name for rate-limiting exemption cookies.
redirect) matches any request with score >= 0.5 before Priority 1020 (token.recaptcha_exemption.valid) is ever evaluated, clients returning with a valid exemption cookie are redirected back to the reCAPTCHA challenge page repeatedly.recaptcha-ca-t): The cookie name recaptcha-ca-t identifies a reCAPTCHA session-token, not a reCAPTCHA exemption cookie. Even if Priority 1020 were reachable, throttling on recaptcha-ca-t would fail to track and limit reuse of the exemption cookie (recaptcha-ca-e).redirect rule matches, lower-priority allow or throttle rules are ignored completely.recaptcha-ca-e for exemption cookies, recaptcha-ca-t for session-tokens, and the X-Recaptcha-Token HTTP header for action-tokens.enforce_on_key_name leaves the exemption cookie unthrottled, allowing attackers who solve a single CAPTCHA to replay the cookie at high volume.throttle rule were placed at a higher priority (Priority 1010) than the redirect rule (Priority 1020), and enforce_on_key_name were changed from recaptcha-ca-t to recaptcha-ca-e.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