Diagram
A decision tree that branches from an access failure on whether the cause is network or permission to select Connectivity Tests, flow and firewall logs, or Policy Troubleshooter.
Choosing the Right Tool for an Access Failure
Each troubleshooting tool answers a different question about the same failed access, so the choice depends on whether configuration, actual traffic, or effective permission evidence is needed. Connectivity Tests validates the intended network path, flow and firewall logs validate what traffic occurred, and Policy Troubleshooter validates what IAM allows. Using them together prevents fixing a firewall when the real problem is a missing permission, or changing IAM when the real problem is a blocked route.
| Tool | What it checks | Use when |
|---|---|---|
| Connectivity Tests | Static configuration of the path from source endpoint to destination endpoint across VPC network, VPC Network Peering, and VPN tunnels | Access may be blocked by routing or a firewall rule and the network versus permission cause is still unknown |
| VPC Flow Logs and Firewall Rules Logging | Actual sampled traffic entering or leaving a VM and the firewall rule that allowed or denied it | Traffic needs verification by port and direction, or a firewall rule needs proof that it works as intended |
| Policy Troubleshooter | Effective IAM permission for a principal on a specific resource | A user or service account is denied an action and the missing underlying permission must be identified |
Domain 3 of 6
23 practice questions
Practice this DomainLast updated