Service edge: Export recovery leaves a return-path failure
The incident
Internal API clients and an independent observability edge share a transit network with an isolated partner segment. Two distribution routers carry separate client, partner, monitoring and service branches. Clients cannot reach the primary service. Restoring its BGP advertisement still leaves replies to one client address failing. Investigate internal API transport from R1: 10.172.192.0/24 to 10.172.198.0/24 (TCP/8443), and 10.172.193.0/24 to 10.172.199.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 R5 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R6. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.
The network
Link addressing (5)
- R1 R2
10.172.208.0/30 - R2 R3
10.172.209.0/30 - R3 R4
10.172.210.0/30 - R2 R5
10.172.211.0/30 - R3 R6
10.172.212.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.