
Answer-first summary for fast verification
Answer: Modify the updates-1 rule to perform the TLS inspection.
For HTTPS traffic, a rule is evaluated only if it has the TLS inspection flag enabled; otherwise, that rule is skipped. https://cloud.google.com/secure-web-proxy/docs/tls-rule-evaluation#before_you_configure_tls_inspection
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are reviewing and tuning Secure Web Proxy at your organization, Mount Kirk Games. Users have reported that they are unable to reach the documents they need on the Terram Earth website (https://www.terramearth.com/docs/*). The Secure Web Proxy rules configuration is as follows:
| Rule Name | Priority | Action | TLS Inspection | Session/Host Match |
|---|---|---|---|---|
| core-rule1 | 1000 | ALLOW | FALSE | host().contains('mountkirkgames.com') |
| updates-1 | 1002 | ALLOW | FALSE | host().contains('terramearth.com') AND request.path.contains('/docs/') |
| updates-limiter | 1050 | DENY | FALSE | host().contains('terramearth.com') |
| allow-tf-src | 1110 | ALLOW | TRUE | host().contains('github.com') AND request.path.contains('/fast/stages/') |
You need to enable access to these documents. What should you do?

A
Delete the updates-limiter rule.
B
Modify the updates-1 rule to perform the TLS inspection.
C
Review Cloud Logging for errors with Cloud NAT. If there are no errors, assign the VM a public IP address.
D
Modify the priority of the updates-limiter rule to 1000.
No comments yet.