You recently configured Google Cloud Armor security policies to manage traffic to your application. You discover that Google Cloud Armor is incorrectly blocking some traffic to your application. You…

Question

Options

• AEnable firewall logs, and view the logs in Firewall Insights.
• BEnable HTTP(S) Load Balancing logging with sampling rate equal to 1, and view the logs in Cloud
• CEnable VPC Flow Logs, and view the logs in Cloud Logging.
• DEnable Google Cloud Armor audit logs, and view the logs on the Activity page in the Google

• A
  7% (3)
• B
  79% (33)
• C
  12% (5)
• D
  2% (1)

Explanation

Google Cloud Armor security policies are attached to backend services of HTTP(S) Load Balancers. When a WAF rule incorrectly blocks traffic, the request-level details - including which specific Cloud Armor rule triggered and the action taken - are captured in the HTTP(S) Load Balancer logs, not in firewall or VPC Flow Logs. Setting the sampling rate to 1 (100%) ensures every request is logged, so you can identify the exact WAF rule responsible. Option A is wrong because Firewall Insights is for VPC firewall rules, not Cloud Armor WAF rules. Option C is wrong because VPC Flow Logs capture IP-level metadata and have no knowledge of application-layer WAF rule decisions. Option D is wrong because Cloud Armor audit logs record configuration changes to policies, not per-request blocking decisions.

No community discussion yet for this question.