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 e-commerce platform hosted on Google Cloud is protected by an external Application Load Balancer and Google Cloud Armor. During high-traffic promotional events, the authentication and checkout APIs experience distributed brute-force and credential stuffing attacks from automated bots.
The security engineering team needs to enforce the following defensive requirements:
sid.429 Too Many Requests status code.0.5 using reCAPTCHA Enterprise integration before requests reach backend services.Which configuration strategy in Google Cloud Armor satisfies these requirements?
BRUTE_FORCE_SSH, and trigger a Cloud Run function to blacklist offending client IP addresses.This option suggests using VPC Service Controls and Event Threat Detection (within Security Command Center) to observe brute force patterns and invoke Cloud Run functions to update firewall rules.
BRUTE_FORCE_SSH inspects VM operating system syslog authentication logs for SSH login attempts, which has no relationship to HTTP/HTTPS web application credential stuffing.sid) or evaluate reCAPTCHA Enterprise bot assessment scores.The objective was to prevent authorized identities from copying sensitive database or storage bucket objects outside an approved enterprise perimeter.
allow rule for traffic matching request.headers['User-Agent'], set enforce_on_key to ALL, and configure Cloud Logging alerts to export logs to Google Security Operations for retroactive deduplication.This configuration relies on standard header matching on the User-Agent string, applies a global rate limit across all traffic (ALL), and streams access logs to Google Security Operations (SecOps) for post-hoc threat investigation.
User-Agent HTTP header, rendering static header matching completely ineffective against automated credential stuffing.enforce_on_key to ALL aggregates the request count across every single user on the platform, causing the entire website to be throttled when total platform traffic exceeds 100 requests per minute.enforce_on_key: ALL applies a single shared bucket to all incoming connections.The organization required long-term audit logging and threat hunting across historical telemetry rather than real-time edge rate limiting and automated bot mitigation.
throttle action, setting enforce_on_key to IP, rate_limit_threshold to 100 requests per 60s, conform_action to allow, and exceed_action to redirect to an external reCAPTCHA verification URL.This configuration sets up basic IP-based rate limiting using the throttle action, which delays or drops individual requests that exceed the 100-request threshold without placing the client into an extended ban state, and attempts to use a redirect action instead of a rate-based ban.
throttle action only restricts requests that exceed the rate threshold during the evaluation window; it does not ban or block subsequent legitimate-rate requests for the required 600-second (ban_duration_sec) cooldown.enforce_on_key: IP aggregates all users behind a shared public IP/NAT gateway, which can cause false positives for distinct users sharing an office network rather than tracking the requested sid session cookie.throttle is designed for rate shaping and smoothing traffic bursts, not punitive multi-minute bans.The goal was to smooth out temporary traffic spikes on a per-IP basis without issuing temporary multi-minute bans or tracking specific application cookie identifiers.
rate_based_ban action, setting enforce_on_key to HTTP_COOKIE with enforce_on_key_name as sid, rate_limit_threshold to 100 requests per 60s, ban_duration_sec to 600s, exceed_action to deny(429), and add a reCAPTCHA assessment rule denying requests where the bot score is below 0.5.Google Cloud Armor rate limiting rules allow administrators to control request volume by client keys and apply granular throttling or banning actions. A rate-based ban (rate_based_ban) temporarily blocks all further traffic from a client identifier once request thresholds are exceeded, rather than merely clipping excess traffic. reCAPTCHA Enterprise integration evaluates user interaction risk scores (from 0.0 to 1.0) directly at the Cloud Armor perimeter layer.
enforce_on_key to HTTP_COOKIE with enforce_on_key_name configured as sid ensures that rate counting is uniquely tracked against individual user sessions rather than shared NAT IP addresses.rate_limit_threshold with a count of 100 and interval_sec of 60, combined with action: rate_based_ban and ban_duration_sec: 600, enforces a strict 10-minute ban once the limit is breached.exceed_action to deny(429) explicitly returns the standard 429 Too Many Requests HTTP error code to offending clients.deny action whenever the score is below the 0.5 threshold, filtering out automated credential-stuffing bots.Using native rate_based_ban alongside reCAPTCHA token evaluation provides full perimeter defense at the global load balancer, minimizing backend resource consumption without requiring custom application middleware.
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