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 Juniors
›
Module 6 · Real-World System Design Cases
›
Design feature flags service
quiz
89 / 105
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why cache rules locally, not call the service per request? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why cache rules locally, not call the service per request? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Per-request lookups are cheaper at LaunchDarkly volume because each evaluation gets its own metered API call billed at the sub-cent tier.
B
Hot path evaluation must be sub-ms. Local cache + periodic refresh decouples latency from network conditions.
C
Browsers require flag rules to be inlined at page load — running a synchronous fetch to /flags/eval per request triggers CORS preflight rejections.
D
Security policy mandates that per-request evaluation reach the central flag service so audit logs capture every individual flag check.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…