Why do database drivers and HTTP clients use 'Connection Pooling'?

1. A To ensure that multiple disparate users can share the same encrypted login credentials when accessing a shared resource on a multi-tenant server.
2. B To apply high-level AES-256 encryption to all data in transit between the application layer and the physical storage medium to ensure absolute privacy.
3. C To eliminate the significant latency cost of repeated TCP/TLS handshakes by maintaining a set of open sockets that can be reused for multiple sequential requests.
4. D To act as a preventive measure that keeps the underlying database from running out of physical disk space during high-frequency write operations.