Google Associate Cloud Engineer
Get started today
Ultimate access to all questions.
You have configured an instance within your new network and subnet, and established the following firewall rules targeting all instances in your network:
- NAME: open-ssh | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 1000 | ALLOW: tcp:22
- NAME: deny-all | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 5000 | DENY: tcp:0-65535,udp:0-65535
What would be the outcome if you attempt to SSH into the instance?
You have configured an instance within your new network and subnet, and established the following firewall rules targeting all instances in your network:
- NAME: open-ssh | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 1000 | ALLOW: tcp:22
- NAME: deny-all | NETWORK: devnet | DIRECTION: INGRESS | PRIORITY: 5000 | DENY: tcp:0-65535,udp:0-65535
What would be the outcome if you attempt to SSH into the instance?
Real Exam
A
SSH access would be denied, requiring the execution of the gcloud firewall refresh command for the allow rule to become effective.
16.7%
B
SSH access would be permitted as the allow rule takes precedence over the deny rule.
Comments
Loading comments...