An organization is deploying a custom VPC network named `prod-vpc` containing two regional subnets: `subnet-us` () and `subnet-eu` (). A Cloud Engineer must restrict SSH access (TCP port 22) so that Compute Engine instances tagged with `admin-workload` in `subnet-us` can only accept SSH connections coming from a management host residing in `subnet-eu` (). Additionally, all other inbound SSH traffic to any instance across the VPC must be blocked. The engineer creates Rule 1 with action ALLOW, direction INGRESS, protocol/port `tcp:22`, source IP `10.20.0.15/32`, target tag `admin-workload`, and priority 100. They also create Rule 2 with action DENY, direction INGRESS, protocol/port `tcp:22`, source IP `0.0.0.0/0`, targets specified as all instances in the network, and priority 50. Which outcome will occur when the management host at attempts an SSH connection to an instance tagged `admin-workload` in `subnet-us`?
- The SSH connection will be denied because Rule 2 has a lower priority number (50) than Rule 1 (100), causing the DENY rule to take precedence over the ALLOW rule regardless of IP specificity or target tags.Answer
- BThe SSH connection will be allowed because Rule 1 specifies a more specific source IP range (10.20.0.15/32) and target tag (admin-workload) than Rule 2.
- CThe SSH connection will be allowed because explicit ALLOW firewall rules override DENY rules when both rules match the incoming packet.
- DThe SSH connection will be denied because organizational IAM policy inheritance blocks cross-subnet SSH traffic unless a explicit primitive Owner role is assigned to the subnet.