PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #254
Your VPC is configured with regional dynamic routing mode. You have deployed VMs and VLAN attachments in the europe-west2 region, and regional internal Application Load Balancers in us- east1. You…
The correct answer is D. Create the backend service in us-east1, create the forwarding rule in us-east1, and then enable. Internal regional Application Load Balancers live entirely in the region where you create them, so both your backend service and your forwarding rule belong in us-east1. To let clients in europe- west2 reach that us-east1 load balancer, you then simply enable global access on…
Question
Options
- ACreate the backend in us-east1, create multiple forwarding rules in each region, and then enable
- BCreate the backend service in europe-west2, create the forwarding rule in us-east1, and then
- CCreate the backend service in us-east1, create the forwarding rule in europe-west2, and then
- DCreate the backend service in us-east1, create the forwarding rule in us-east1, and then enable
How the community answered
(29 responses)- A7% (2)
- B21% (6)
- C10% (3)
- D62% (18)
Explanation
Internal regional Application Load Balancers live entirely in the region where you create them, so both your backend service and your forwarding rule belong in us-east1. To let clients in europe- west2 reach that us-east1 load balancer, you then simply enable global access on the internal forwarding rule. This preserves your regional deployment while transparently routing traffic over Google’s backbone.
Topics
Community Discussion
No community discussion yet for this question.