Service edge: The advertised prefix does not match the service
The incident
Internal API clients and an independent observability edge share a transit network with an isolated partner segment. Client, partner and service access branches attach to different vertices of a routed core triangle. The primary service subnet is missing remotely even though a similar-looking network statement exists on the service edge. The secondary subnet works. Investigate internal API transport from R1: 10.172.160.0/24 to 10.172.170.0/24 (TCP/8443), and 10.172.161.0/24 to 10.172.171.0/24 (TCP/443).
Your objective
Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R4 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R3. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.
The network
Link addressing (6)
- R1 R2
10.172.176.0/30 - R2 R3
10.172.177.0/30 - R3 R5
10.172.178.0/30 - R5 R2
10.172.179.0/30 - R3 R4
10.172.180.0/30 - R5 R6
10.172.181.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.