Which term describes a pool of connections used by an application to connect to a server?

• A. Branch
• B. Class
• C. Connection Pool
• D. Browser Developer Tools

Answer: (C)

The idea here is connection pooling: keeping a set of open connections to a server that an application can borrow, use, and then return for reuse. Creating a new connection for every request is expensive in terms of time and resources, so a pool lets the application reuse existing connections, which reduces latency and improves throughput while controlling how many connections are active at once.

When the app needs to talk to the server (such as a database or an HTTP service), it checks out a connection from the pool, uses it, and then returns it to the pool instead of closing it. The pool can enforce a maximum size and timeouts, so resources aren’t exhausted.

Other terms listed aren’t about managing a shared set of connections: a branch is a path in version control or a conditional flow in code; a class is a blueprint for objects; and browser developer tools are debugging features built into the browser. The term that fits a pool of connections used by an application to connect to a server is connection pool.