Design a cloud-based customer consent & privacy preference platform
PremiumBackend systemHard
- Event distribution
- Consistency models
- Audit logging
Quick answer
This backend system interview question asks you to design a cloud-based customer consent & privacy preference platform. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a cloud-based Customer Consent & Privacy Preference Platform. End-users interact with preference centers to grant or withdraw consent for specific data processing purposes (e.g., analytics, personalized advertising, data sharing). The platform must persistently record these choices, maintain an immutable history of preference updates, and reliably propagate the updated permissions to dozens of internal downstream data processing systems.
What must a cloud-based customer consent & privacy preference platform do?
- Preference Ingestion: Accept and record consent preference changes submitted by users via web or mobile apps.
- Real-Time Evaluation: Provide a low-latency lookup API for downstream ad-tech and analytics services to check if a specific user has consented to a specific purpose.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Event distribution
- Consistency models
- Audit logging
- High throughput reads
- Data governance
- Async propagation
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a cloud-based customer consent & privacy preference platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Hard. It suits engineers preparing for senior interviews, where you are expected to drive the discussion and go deep on trade-offs.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team