Your 'Orders' table is partitioned by `customer_id`. One customer is responsible for 20% of all orders (Data Skew). How do you resolve the write hotspot?

1. A Horizontal CPU Verticalization, where the database automatically migrates the 'whale' customer to a much larger and more powerful physical instance within the cluster.
2. B Salting the Partition Key by appending a random suffix (e.g., 1..N) to the ID, spreading that single customer's data across multiple physical partitions for parallel writing.
3. C Global Sequential Numbering, which replaces the existing partition key with a strictly monotonic auto-incrementing integer that is synchronized across all regional data centers.
4. D Write-Buffer Caching, which leverages a specialized, ultra-high-speed memory layer to absorb the bursty write volume before eventually flushing the data to the physical disk.