When a database reaches 100 percent utilization, what action can be taken to support it?

Vertical scaling is the correct choice when a database reaches 100 percent utilization. This method involves adding resources to the existing server, such as increasing CPU power, adding more RAM, or enhancing storage capabilities. The primary advantage of vertical scaling is that it can lead to improved performance for a single database instance, allowing it to handle larger workloads without needing to change the architecture significantly.

In scenarios involving database utilization, vertical scaling helps address performance bottlenecks that occur due to reaching resource limits. When you enhance the capabilities of an existing database server, it can read and process larger amounts of data more efficiently, mitigating issues that arise from high utilization.

While horizontal scaling involves adding more servers to distribute the load, it often requires significant changes to the application architecture, especially for databases, which may not be straightforward. Pooling generally refers to the practice of pooling resources and is more applicable in contexts like connection pooling or resource allocation within a managed environment. Bursting, on the other hand, refers to temporarily using cloud resources beyond the provisioned limits, which is typically a short-term solution and might not suffice for a sustained high utilization scenario.

For a persistent issue like 100 percent database utilization, vertical scaling is the most effective immediate response.