CoreHRx Jobs

Apply in one click, save jobs and take free mock tests.

Register free Log in
Hiring? Post jobs with CoreHRx
My account
user

View & update profile

System Design mock test: free online practice

15 to 30 random questions in 15 to 30 minutes, by the level you choose: caching, load balancing, sharding, queues, consistency and estimation. After you submit you get your score, your strong and weak topics, and the right answer with an explanation for every question.

Choose your level

Free with a CoreHRx Jobs account: you will be asked to sign in or create one first.

What does the System Design mock test cover?

The test covers 13 topics across three levels. Each attempt picks 15 to 30 questions at random, by the level you choose, so every attempt is different.

  • Capacity Estimation
  • Databases and Indexing
  • Queues and Event Streams
  • Replication and Sharding
  • Caching
  • Consistency and CAP
  • Design Case Studies
  • Observability
  • Reliability and Fault Tolerance
  • Storage and CDN
  • API Design and Rate Limiting
  • Load Balancing
  • Scalability Basics

Sample System Design mock test questions

One question from each level, the way they appear in the test. A new set comes on the 1st of every month. Try it, then open the answer.

  1. FresherDatabases and Indexing

    What is the main goal of normalising a relational schema?

    • Store each fact once, so updates do not leave copies that disagree
    • Put all the data in a single table to avoid foreign keys
    • Store each fact in many tables, so reads never need a join
    • Make every column a text type so any value can be saved
    Show the answer

    Answer: Store each fact once, so updates do not leave copies that disagree. Normalisation removes duplicated data, so changing a customer's city means one update, not many. Copying data into many tables to avoid joins is denormalisation, which teams sometimes choose on purpose for read speed.

  2. Intermediate (1-5 years)API Design and Rate Limiting

    A feed uses OFFSET pagination. New posts arrive while a user scrolls, and they see some posts twice. What fixes this?

    • Sorting by a random number on each request
    • Returning the total count in every response
    • Shorter pages of 5 items each
    • Cursor pagination using the last item's sort key, for example created_at and id
    Show the answer

    Answer: Cursor pagination using the last item's sort key, for example created_at and id. New rows at the top shift every OFFSET, so items slide into the next page and repeat. A cursor says 'give me items older than this one', which is stable under inserts. Smaller pages make the shifting happen more often.

  3. Experienced (5+ years)Load Balancing

    Many independent load balancer instances each pick the least-loaded backend from their own slightly stale view. Backends that look idle get flooded. What strategy avoids this herding?

    • Pure least-connections with all instances sharing the same stale data
    • Always send to the backend with the lowest IP address
    • Power of two choices: pick two backends at random, use the less loaded
    • Increase the health-check interval to one minute
    Show the answer

    Answer: Power of two choices: pick two backends at random, use the less loaded. When every balancer chases the same 'best' backend with stale data, they all pile onto it. Random two-choice picks spread load well and tolerate stale information. Least-connections on stale data is the cause of the herding here.

Take the full System Design mock test: 15 to 30 questions and 15 to 30 minutes, by level.

How is the System Design mock test scored?

A question counts as right only when you pick exactly the right option, or all the right options where it says so; a question left blank counts as wrong. Your score is the share of the test's questions you got right (15 to 30, by level). The result also scores every topic, so you know what to revise before the interview.

  • 75% or more in a topica strength
  • 50% to 74%worth a revision
  • Under 50%a topic to work on

System Design mock test: questions people ask

Is the System Design mock test free?

Yes. The System Design mock test is free. You need a free CoreHRx Jobs account to start it, so your score and the topics to work on are saved.

How many questions are in the System Design mock test?

It depends on the level: Fresher has 15 questions in 15 minutes, Intermediate has 20 questions in 20 minutes, Experienced has 30 questions in 30 minutes. They are multiple-choice questions picked at random from a larger bank of System Design questions at your level, so every attempt is different.

Which System Design topics does the test cover?

The questions cover Capacity Estimation, Databases and Indexing, Queues and Event Streams, Replication and Sharding, Caching, Consistency and CAP, Design Case Studies, Observability, Reliability and Fault Tolerance, Storage and CDN, API Design and Rate Limiting, Load Balancing, Scalability Basics. Your result shows how you did in each topic.

Which level should I choose?

Fresher: Students and freshers: the building blocks and the terms interviewers use. Intermediate (1-5 years): 1 to 5 years: choosing components for a requirement and finding bottlenecks. Experienced (5+ years): 5+ years: trade-offs, failure modes, consistency and capacity numbers. Start with Fresher and move up.

Can employers see my System Design score?

Only your best System Design score, and only when it is 60% or more. It shows on the job applications you send on CoreHRx. Lower scores stay private.

Can I take the System Design mock test again?

Yes, up to 10 tests a day. Each attempt picks questions you have not seen recently first.

All mock tests