What is the primary goal of data partitioning in system design?

To enhance system scalability and availability.

To improve the user interface responsiveness.

To increase data security by encrypting data.

To reduce the overall application development time.

In the context of data partitioning, what does 'horizontal partitioning' specifically refer to?

Distributing rows of a table across multiple servers.

Splitting columns of a table into multiple tables.

Creating multiple copies of the entire database on different servers.

Storing different types of data (e.g., users and products) on separate servers.

It minimizes the amount of data that needs to be rebalanced.

It eliminates the need for data replication.

It guarantees strong data consistency across all partitions.

It ensures all partitions have exactly the same amount of data at all times.

Increased complexity for cross-partition transactions and queries.

Decreased query latency for single-partition queries.

Easier and faster data backup and recovery processes.

Simplified data modeling due to smaller datasets.

The query will require a distributed join across multiple partitions, potentially fetching data from various servers.

The query will always be fast as both tables are partitioned.

The query will involve a full table scan on the orders table across all partitions.

The query will only hit a single order partition if the `user_id` and `order_id` happen to hash to the same server.

Moving data between existing partitions to redistribute load or accommodate changes in the number of nodes.

Restoring data from backups after a system failure.

Consolidating small, underutilized partitions into a single, larger partition.

Duplicating data across multiple partitions solely for redundancy purposes.

Composite partition, first by `region` (range or list) and then by `driver_id` (hash) or `start_time` (range) within each region's partition.

Hash partition by `trip_id` across all servers.

Range partition by `start_time` and replicate data to each region.

Vertical partition, storing `region` and `start_time` in one table, and `driver_id` in another.

Data Partitioning in System Design — Free MCQ Practice Test | testpaper.space