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.
You manage an e-commerce web application behind a global external Application Load Balancer protected by a Google Cloud Armor security policy. You must implement a two-tiered bot management workflow with the following requirements:
execute() on every user interaction./checkout, allow requests with a session score of 0.8 or higher, redirect requests scoring between 0.4 and 0.8 to an interstitial challenge page, and deny requests scoring below 0.4.Which configuration should you implement?
POLICY_BASED_CHALLENGE integration type, install it across your web pages, and link it to the Cloud Armor security policy using --recaptcha-redirect-site-key. Configure rules on /checkout using token.recaptcha_session.score to allow >= 0.8, redirect >= 0.4 with --redirect-type google-recaptcha, and deny < 0.4.A POLICY_BASED_CHALLENGE key is a standard website reCAPTCHA key type used for direct frontend-to-backend integrations rather than Cloud Armor WAF workflows. It evaluates user interactions against a configured score threshold and deterministically triggers a visual CAPTCHA challenge when the initial score falls below that threshold.
SCORE integration type (wafFeature: SESSION_TOKEN), whereas WAF challenge-page keys require the INVISIBLE integration type (wafFeature: CHALLENGE_PAGE). Using POLICY_BASED_CHALLENGE does not generate recaptcha-ca-t session cookies for token.recaptcha_session.score evaluation.--recaptcha-redirect-site-key applies to manual challenge redirects at the policy level and does not bind a session-token key to the scoring rules to block stolen tokens.POLICY_BASED_CHALLENGE keys are designed for direct web application forms, logins, and signups evaluated by backend CreateAssessment API calls.wafSettings (wafService: CA) required for Cloud Armor inline token decryption.You were protecting a website without Cloud Armor WAF bot management—using backend application servers to call the reCAPTCHA Enterprise CreateAssessment API directly and trigger deterministic challenges based on a key-level score threshold.
A common misconception is that a single reCAPTCHA key handles every Cloud Armor bot management capability. In practice, each WAF feature (ACTION_TOKEN, SESSION_TOKEN, and CHALLENGE_PAGE) demands its own dedicated key configured with the corresponding wafFeature and integrationType.
SCORE integration type) installed across your web pages and a separate WAF-enabled Web challenge-page key (INVISIBLE integration type). Link the challenge-page key to the security policy using --recaptcha-redirect-site-key, and configure /checkout rules using token.recaptcha_session.score with the session-token key associated with the rules to allow >= 0.8, redirect >= 0.4 with --redirect-type google-recaptcha, and deny < 0.4.Integrating reCAPTCHA Enterprise with Google Cloud Armor for multi-layered bot defense requires provisioning a dedicated WAF-enabled Web key (wafService: CA) for each distinct protection feature. A session-token key (SCORE integration type) silently evaluates browsing behavior and stores an encrypted token in the recaptcha-ca-t browser cookie, while a challenge-page key (INVISIBLE integration type) powers an interstitial HTML challenge page that issues an recaptcha-ca-e exemption cookie when passed.
recaptcha-ca-t cookie every 30 minutes without calling execute() on every action, while Cloud Armor enforces rules on /checkout rather than blocking the initial landing page./checkout enforcement: Security policy rules evaluate token.recaptcha_session.score inline at Google's network edge to allow scores >= 0.8, trigger --action redirect --redirect-type google-recaptcha for scores from 0.4 to 0.8, and deny scores < 0.4.key attribute against the rule's allowed keys and treat tokens from unknown keys as invalid.--recaptcha-redirect-site-key ensures you can inspect challenge analytics and train a site-specific risk model.0.4 to 0.8).recaptcha-ca-e cookie (valid for three hours by default).HTTP-COOKIE (recaptcha-ca-t or recaptcha-ca-e) to prevent cookie replay abuse.Combining separate session-token and challenge-page keys gives you continuous behavioral telemetry across pages alongside custom challenge branding, analytics, and strict rule-level key validation without modifying backend application code.
SCORE integration type) installed across your web pages, and omit creating a challenge-page key so Cloud Armor defaults to the Google-managed site key for redirects. Configure /checkout rules using token.recaptcha_session.score without binding the session-token key to the rules so any valid token is accepted, allowing >= 0.8, redirecting >= 0.4, and denying < 0.4.When a Cloud Armor security policy executes a --redirect-type google-recaptcha rule without an explicitly configured --recaptcha-redirect-site-key, Cloud Armor falls back to a Google-managed site key to render the challenge page. Similarly, writing rules with token.recaptcha_session.score without associating specific reCAPTCHA keys evaluates the score inside any cryptographically valid session token.
key against keys associated with the rule, attackers can replay tokens harvested from other keys or applications without Cloud Armor rejecting them as invalid.Score overview and Challenges charts).You needed rapid, temporary emergency bot mitigation on a non-critical endpoint where viewing challenge-page metrics, training a custom site model, and preventing cross-key token theft were not required.
Although Cloud Armor can technically execute redirect challenges without a customer-owned challenge-page key and read scores without rule-level key binding, production deployments must always pair customer-owned challenge-page keys (--recaptcha-redirect-site-key) with rule-level key associations to achieve observability and prevent token replay attacks.
SCORE integration type) installed exclusively on /checkout, and a challenge-page key (INVISIBLE integration type) attached to the redirect rule via --recaptcha-action-site-keys. Enforce token.recaptcha_session.score rules across all pages including the landing page, and add a rate-limiting rule keyed on the X-Recaptcha-Token HTTP header to limit token reuse.A reCAPTCHA session-token operates as a browser cookie (recaptcha-ca-t) created after the reCAPTCHA JavaScript loads and executes on a page. Because the cookie must already exist when the browser requests a protected path, session-token JavaScript must be installed on preceding pages, while Cloud Armor rules enforce access on protected pages rather than the initial landing page.
/checkout and enforcing token.recaptcha_session.score on the landing page blocks legitimate first-time visitors before the browser has loaded the script and obtained a recaptcha-ca-t cookie.--recaptcha-redirect-site-key, not per rule with --recaptcha-action-site-keys (which applies to action-tokens).X-Recaptcha-Token is the HTTP request header used exclusively by action-tokens. Session tokens use the recaptcha-ca-t cookie (HTTP-COOKIE), and exemption cookies use recaptcha-ca-e (HTTP-COOKIE), so rate-limiting X-Recaptcha-Token fails to throttle session or exemption cookie reuse.X-Recaptcha-Token requires manual client-side JavaScript (XHR, Fetch, or mobile SDK) attachment per request.You were implementing action-tokens on specific user interactions (such as a button click on /checkout or a mobile app request) rather than continuous session-wide scoring, and linking action-token keys with --recaptcha-action-site-keys alongside X-Recaptcha-Token rate limiting.
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