A user configures an HTTP(S) Load Balancer but finds that requests to /api/* are not routed to the intended backend service. Which is the most likely cause?

medium📝 Debug Q14 of 15

GCP - Cloud Load Balancing

A user configures an HTTP(S) Load Balancer but finds that requests to /api/* are not routed to the intended backend service. Which is the most likely cause?

AThe backend service is not in the same region

BThe forwarding rule is missing

CThe target proxy is not HTTPS

DThe URL map lacks a path rule for <code>/api/*</code>

Step-by-Step Solution

Solution:

Step 1: Check URL map path rules
If /api/* is missing in path rules, requests won't route correctly.
Step 2: Verify other components
Forwarding rule and target proxy affect traffic flow but missing path rule directly causes routing failure. Backend region mismatch usually causes latency, not routing failure.
Final Answer:
The URL map lacks a path rule for /api/* -> Option D
Quick Check:
Missing path rule = routing failure [OK]

Quick Trick: Check URL map paths if routing fails [OK]

Common Mistakes:

Assuming forwarding rule absence causes routing error
Confusing HTTPS proxy with routing logic
Ignoring URL map path rules

Master "Cloud Load Balancing" in GCP

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More GCP Quizzes

A user configures an HTTP(S) Load Balancer but finds that requests to /api/* are not routed to the intended backend service. Which is the most likely cause?

Step 1: Check URL map path rules

Step 2: Verify other components

Final Answer:

Quick Check:

Want More Practice?