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.
Your organization operates a public API behind a global external Application Load Balancer using cross-project service referencing. The forwarding rule and URL map reside in a host project, while the backend service resides in a service project. After a previous rate-limiting rollout blocked legitimate users, you must safely validate a new rate-based-ban Cloud Armor rule against live traffic.
Your workflow must:
Which workflow should you implement?
rate-based-ban rule in preview mode before enforcing it.This approach attempts to validate a Cloud Armor rate-limiting policy solely through Cloud Monitoring dashboards in the backend service project while leaving HTTP(S) request logging disabled on the backend service.
rateLimitAction details are captured.IP, XFF_IP, or HTTP_HEADER) per minute to calculate a 99th percentile baseline.1.rateLimitAction outcomes.You only needed high-level aggregate trend monitoring in a single-project deployment where per-request key analysis and 1:1 request capture were not required, and you were viewing dashboards inside the frontend project.
rate-based-ban rule with --preview, and analyze previewSecurityPolicy and rateLimitAction fields alongside Cloud Monitoring's Previewed Requests metric to set the threshold at the 99th percentile of peak traffic before disabling preview mode.Validating a Google Cloud Armor rate-based-ban rule using preview mode (--preview) combined with full HTTP(S) request logging lets you evaluate how live production traffic triggers rate limits without blocking legitimate users. Because Cloud Armor logs are emitted through the Application Load Balancer logging pipeline, enabling backend service logging at a sampling rate of 1 guarantees complete request visibility.
1 disables down-sampling so every evaluated request is recorded. Because cross-project service referencing exports load balancer logs and metrics to the host project containing the forwarding rule and URL map, granting read permissions on the host project ensures backend administrators can access all telemetry.--preview flag logs matched traffic while allowing requests to proceed normally and continue evaluating lower-priority rules.previewSecurityPolicy and rateLimitAction outcomes (RATE_LIMIT_THRESHOLD_CONFORM, RATE_LIMIT_THRESHOLD_EXCEED, and BAN_THRESHOLD_EXCEED) in Cloud Logging, paired with the Previewed Requests metric in Cloud Monitoring, lets you measure the 99th percentile of normal requests per key per minute and adjust thresholds before removing preview mode.Unlike relying on dynamically sampled Cloud Monitoring metrics alone or inspecting logs in the wrong project, this workflow combines un-sampled per-request logs in the host project with non-blocking preview evaluation, ensuring accurate threshold tuning without risking production outages.
rate-based-ban rule at a lower priority than an explicit allow rule for API clients, and convert the rule action from rate-based-ban to throttle if false positives appear in enforcedSecurityPolicy logs.This workflow enables partial HTTP(S) request logging at a 0.1 sampling rate, orders the rate-based-ban rule beneath an explicit allow rule, and assumes you can later convert a rate-based-ban rule into a throttle rule.
0.1 records only 10% of evaluated requests, leaving major visibility gaps when calculating peak per-client request rates and detecting false positives during active rule tuning.allow rule prevents Cloud Armor from ever evaluating the rate-limiting rule for those clients, because rule evaluation stops at the first non-preview match.rate-based-ban rule into a throttle rule; the action must be recreated if you want to switch from banning to throttling.throttle rule to a rate-based-ban rule later, but you cannot downgrade a rate-based-ban rule to throttle.previewSecurityPolicy rather than enforcedSecurityPolicy (which records the terminal enforced rule).allow rules to evaluate target traffic.The sampling rate were set to 1, the rule were placed above broad allow rules and originally created as a throttle rule (which can later be converted to rate-based-ban), and you inspected previewSecurityPolicy logs.
rate-based-ban rule at priority 0 with preview: false using the default 500-requests-per-minute threshold, and query network_security_policy logs in the host project for statusDetails="throttled_by_security_policy" to spot false positives.This configuration immediately enforces a rate-based-ban rule (preview: false) at the highest priority using the default 500-requests-per-minute threshold, while relying on verbose logging and network_security_policy resource logs to detect false positives.
preview: false enforces active bans immediately against live production traffic using an untuned default threshold (500 requests per 60 seconds), risking immediate outages for legitimate users behind shared NAT gateways.network_security_policy resource in Cloud Logging stores Adaptive Protection and network DDoS alerts—not Cloud Armor per-request rate-limiting logs, which are recorded under the http_load_balancer resource.statusDetails="throttled_by_security_policy" applies to THROTTLE rules returning HTTP 429, whereas rate-based-ban denials log denied_by_security_policy and BAN_THRESHOLD_EXCEED.500 requests/minute limit is a generic starting point that frequently misclassifies NAT-aggregated API clients.http_load_balancer in the host project after enabling backend service logging.You were investigating Adaptive Protection anomaly alerts rather than per-request rate-limiting thresholds, and you kept new rate-limiting rules in preview mode before enforcing them.
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