Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.Start 7-day trial →
⚡
← Courses›System Design for Python JuniorsModule 5 · Real-World Case Studies›Predict: back-of-envelope for global LBpredict74 / 105
+75 XP
Task
📝 **Question:** Tokyo user → us-east round-trip is ~200ms; same user → Tokyo region is ~5ms. Single API call extra latency from running only us-east? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
Predict the output

Read the code carefully

# A Tokyo mobile app makes ONE API call per screen.
# Origin: us-east only. Asia region would be ~5ms RTT.
#
# rtt_to_us_east_ms = 200   # cross-Pacific
# rtt_to_tokyo_ms   = 5     # intra-region
# added_latency    = rtt_to_us_east_ms - rtt_to_tokyo_ms
#
# What's the exact string the test expects? (form: '~NNN ms per call')
# Type your prediction.

What will the program print? Write here:

💬 Discussion

Be the first to ask a question or share a tip.
Sign in to join the discussion. Reading is free.
Loading discussion…