The Cross-Region Egress Bill
You are the data engineer on call for this production path. A data pipeline works correctly but incurs a large bill because storage and compute are in different regions. What would you investigate, how would you fix it safely, and how would you prove the issue is resolved?
Scenario context
The incident centers on data locality and egress cost. The current implementation or operating process does not make that contract explicit, so the team needs a diagnosis supported by evidence rather than a tool or configuration guess.
Business requirement
Identify the most likely failure mechanism, propose a reversible production-safe fix, and explain validation, trade-offs, monitoring, and recovery.
Schema
Cloud Platform evidence is shown below. Treat it as a production review artifact rather than a toy exercise.Broken logic / code
workload_region=ap-south-1
storage_region=us-east-1
autoscaling_signal=cpu_average
quota_headroom=3%
cost_owner=UNKNOWN
# Reliability, locality, quota, and cost contracts were not reviewed together.Logs / error
[Production review] Scenario 157: The Cross-Region Egress Bill
Observed symptom: A data pipeline works correctly but incurs a large bill because storage and compute are in different regions. What would you investigate, how would you fix it safely, and how would you prove the issue is resolved?
Core contract at risk: data locality and egress cost.
Evidence to collect: Track cost by workload, egress bytes, quota utilization, scaling events, API throttles, drift, failed deployments, and recovery readiness. Add game days for regional, control-plane, and credential failures. Run budgets and alerts tied to accountable owners.Actual output
A data pipeline works correctly but incurs a large bill because storage and compute are in different regions. What would you investigate, how would you fix it safely, and how would you prove the issue is resolved?Expected output / expected logic
A strong response should define the contract, rank likely causes, propose a safe fix, and prove correctness with monitoring and reconciliation.Your attempt
Write your root-cause analysis
Think before revealing the answer. A partial but honest attempt is better practice than reading the model solution first.
Saved
Interview-style explanation
Now explain your solution as if you are in an interview: symptom, root cause, fix, edge cases, trade-offs, monitoring, and prevention.