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 runs a global web application behind a global external Application Load Balancer with Cloud CDN enabled on a backend service (web-backend). Currently, web-backend is attached to a backend security policy (prod-waf-policy) enforcing google:xss:stable at priority 200, with a default rule (2147483647) set to allow.
You must meet these requirements without disrupting live traffic:
google:xss:canary rules in preview mode alongside the enforced stable rules.Which configuration should you implement?
CLOUD_ARMOR_EDGE policy with the regional deny rule, update its default rule (2147483647) to deny-403, and attach it to web-backend using --edge-security-policy. In prod-waf-policy, add google:xss:canary with --preview at priority 300, and permanently set --log-level=VERBOSE on prod-waf-policy to stream rule match logs.This configuration attaches an edge security policy with a default-deny action (deny-403), positions the preview-mode canary rule at priority 300 below the enforced stable rule (200), and relies on permanent verbose logging without enabling load balancer request logging.
2147483647) to deny-403 without explicit allow rules for legitimate users blocks all non-matching traffic at the edge before requests ever reach Cloud CDN or prod-waf-policy.200 has higher precedence than 300, any request blocked by google:xss:stable stops evaluation immediately and never triggers or logs the google:xss:canary rule at 300.--log-level=VERBOSE does not activate HTTP(S) request logging if logging is still disabled on web-backend. Furthermore, keeping verbose logging enabled permanently in production risks storing end-user PII in Cloud Logging.2147483647 acts as the catch-all fallback for any traffic not matched by higher-priority rules.100 evaluates before 200, whereas 300 evaluates after 200.The edge policy's default rule remained allow, the preview-mode canary rule were placed at priority 100, backend service logging were enabled with a sampling rate of 1, and verbose logging were used only temporarily during tuning.
prod-waf-policy to CLOUD_ARMOR_EDGE so its rules protect Cloud CDN cache hits, add the regional deny rule at priority 50, and add google:xss:canary in preview mode at priority 100. Enable Adaptive Protection and inspect the network_security_policy logs in Cloud Logging to review every rule match.This approach attempts to consolidate regional blocking, WAF managed rules, and canary previewing inside a single CLOUD_ARMOR_EDGE policy while relying on Adaptive Protection logs (network_security_policy) for per-request WAF rule telemetry.
CLOUD_ARMOR_EDGE) on Application Load Balancers only support basic filtering (such as client IP address and geography) with allow and deny actions. They do not support preconfigured WAF rules, managed rules (google:xss:canary or google:xss:stable), body filtering, or Adaptive Protection, and cannot serve as a backend policy.network_security_policy resource only record Layer 7 DDoS anomaly alerts after at least a one-hour baseline training period. They do not emit per-request WAF match logs or preview-mode rule evaluations, and Adaptive Protection ignores requests served from Cloud CDN or rejected by security policies.CLOUD_ARMOR).http_load_balancer) when HTTP(S) logging is enabled on the backend service.A separate CLOUD_ARMOR_EDGE policy were used exclusively for pre-cache regional filtering alongside the CLOUD_ARMOR backend policy for managed XSS rules, and backend HTTP(S) request logging were enabled at a sampling rate of 1.
CLOUD_ARMOR) containing the regional deny rule to web-backend. In prod-waf-policy, add google:xss:canary with --preview at priority 300, and review the default Cloud Monitoring security dashboard without changing load balancer logging settings.This approach attempts to attach a second backend security policy to a single backend service, places the preview-mode canary rule at a lower logical priority (300) than the enforced rule (200), and relies solely on default Cloud Monitoring metrics without enabling HTTP(S) request logging.
200), placing google:xss:canary in preview mode at priority 300 prevents requests already matched by google:xss:stable from ever reaching the canary rule.CLOUD_ARMOR policy and one CLOUD_ARMOR_EDGE policy.You attached a CLOUD_ARMOR_EDGE policy instead of a second backend policy, placed the preview-mode canary rule at a higher priority (such as 100) above the stable rule, and enabled backend service request logging with a sampling rate of 1.
CLOUD_ARMOR_EDGE policy with the regional deny rule and a default allow rule, and attach it to web-backend using --edge-security-policy. In prod-waf-policy, add google:xss:canary with --preview at priority 100. Enable HTTP(S) logging on web-backend with a sampling rate of 1, temporarily set --log-level=VERBOSE on prod-waf-policy, and inspect enforcedEdgeSecurityPolicy and enforcedSecurityPolicy logs.This architecture pairs an edge security policy (CLOUD_ARMOR_EDGE) with an existing backend security policy (CLOUD_ARMOR) on the same backend service, places canary rules in preview mode at a higher logical priority than enforced stable rules, and configures full-fidelity request logging for safe rule tuning.
CLOUD_ARMOR_EDGE policy via --edge-security-policy enforces the regional deny rule at the outermost network perimeter upstream of Cloud CDN, blocking unwanted requests even if the content is cached. Retaining prod-waf-policy via --security-policy keeps backend WAF inspection active for cache misses.google:xss:canary with --preview at priority 100 ensures it is evaluated before the enforced google:xss:stable rule at priority 200. When a preview rule triggers, Cloud Armor logs the match and continues evaluation, allowing stable at 200 to still enforce protection without risking production outages from unvalidated signatures.web-backend with a sampling rate of 1 guarantees every request is logged during active tuning. Temporarily enabling --log-level=VERBOSE surfaces offending request snippets and subexpressions, while enforcedEdgeSecurityPolicy and enforcedSecurityPolicy log fields separate edge and backend decisions.--no-preview.100, 200) allows future rule insertions without renumbering.enforcedEdgeSecurityPolicy from enforcedSecurityPolicy simplifies troubleshooting across cache hits and origin traffic.Unlike replacing the backend policy, placing canary rules below enforced rules, or leaving logging disabled, this design preserves production availability while providing 100% request visibility across both edge cache enforcement and backend WAF evaluation.
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