Core Concepts - Quiz

Which scaling technique involves increasing the power of a single server by adding more CPU or memory?

What is the main goal of a load balancer in a distributed system?

Which availability strategy involves maintaining backup components that can take over if the primary fails?

Which consistency model allows temporary inconsistencies but guarantees that, eventually, all replicas will converge?

A distributed key-value store needs to route requests efficiently as servers are added or removed. Which technique reduces rehashing disruptions?

What does 'latency' refer to in system performance?

In a system, which component is considered a single point of failure?

Which of the following best describes horizontal scaling?

Which factor is LEAST likely to affect system reliability?

Which availability tier corresponds with less than 5 minutes of downtime per year?

Which technique ensures that requests are automatically redirected to backup resources if the primary resource fails?

What is an example of a system using strong consistency?

Which option best describes throughput in a distributed system?

Which situation might cause massive rehashing in a distributed database using hash(key) mod N?

Which distributed systems challenge does the CAP theorem describe?

When using a geographically distributed system, which risk increases if data is not replicated?

Which option introduces the highest risk of a single point of failure?

Which architecture is most suitable for handling both high reads and writes in a global application?

Why is it critical to monitor system metrics and trigger alerts?

Which scenario is BEST suited for eventual consistency?

Which of the following directly improves both reliability and availability?

Arrange the following steps for a highly available web service during a failover event.

Drag and drop to reorder, or use the arrows.

Order the steps involved in horizontal scaling of an application server layer.

Drag and drop to reorder, or use the arrows.

Arrange the stages to achieve strong consistency in a distributed database write operation.

Drag and drop to reorder, or use the arrows.

Match each method to how it improves system availability.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match the concept to the system design characteristic.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each consistency model description to its name.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.

Match each availability approach to its primary advantage.

Click an item on the left, then click its match on the right. Click a matched item to unmatch.