A cloud engineer is deploying a custom-mode Virtual Private Cloud (VPC) network named `corp-network` in Google Cloud to host multi-region microservices. The engineer needs to configure subnets in `us-central1` and `europe-west1` and ensure that internal Compute Engine virtual machines across these subnets can communicate with each other over TCP port 8080. Which TWO configurations accurately reflect Google Cloud VPC subnet and firewall rule deployment behaviors? (Select TWO answers.)
- Creating custom-mode subnets requires manually defining non-overlapping primary IPv4 CIDR ranges for each region, which can later be expanded without recreating the subnet.Answer
- Custom firewall ingress rules with priorities between 0 and 65534 must be explicitly created to allow internal TCP port 8080 traffic, because the implied ingress rule denies all incoming traffic.Answer
- CSetting a firewall rule priority value of 65535 ensures that the rule takes maximum precedence and overrides all other conflicting network rules.
- DCreating a custom-mode VPC network automatically provisions one default subnet per Google Cloud region using pre-allocated `/20` CIDR blocks.
Answer
Custom-mode subnets require manual definition of non-overlapping primary IPv4 ranges that can be expanded later, and custom ingress firewall rules with higher precedence (0-65534) must be created to allow port 8080 traffic because VPC networks feature an implied deny-all ingress rule.
The correct responses state that custom-mode VPC subnets require manual definition of non-overlapping IP ranges (which can be expanded later) and that explicit ingress firewall rules (priority 0-65534) are required to allow internal port 8080 traffic due to the implied deny-all ingress rule.
Step-by-Step Solution
Key Concept
Deploying custom VPC networks, subnet expansion rules, and VPC firewall rule evaluation precedence.
Estimated Time:1m 30s