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 Slack notifications
quiz
90 / 105
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Why a digest, not instant email for every message? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Why a digest, not instant email for every message? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Per-message SMTP cost — sending 100M emails an hour through SendGrid would exceed Slack's marketing budget several times over.
B
Aggregation respects user attention; ping fatigue kills engagement. Digest after delay = signal not spam.
C
GDPR's email-frequency clause requires aggregation into a single daily summary for any user located inside the European Economic Area.
D
Email infrastructure is too slow to deliver per-message alerts in time — digests batch them so the SMTP queue never falls behind real chat.
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…