You’ve configured an instance within your new network and subnet, setting up firewall rules targeting all instances in your network. The rules are as follows:

NAME: deny-all | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 1000 | ACTION: DENY:tcp:0-65535,udp:0-6553

NAME: open-ssh | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 5000 | ACTION: ALLOW:tcp:22

Despite these settings, your SSH connection attempts to the instance are timing out. What is the most probable reason for this issue?

Real Exam

The SSH connection is denied, and the instance requires a reboot for the allow rule to become effective.

7.7%

The SSH key has not been properly uploaded to the instance.

15.4%

The firewall rule must be specifically applied to the instance.

7.7%

The SSH connection is denied because the deny rule, having a higher priority, overrides the allow rule.

69.2%

Google Associate Cloud Engineer