Which statement about Grizzly libraries used for HTTP connectors is true?

• A. Grizzly is a standard open source library supporting HTTP/S protocols.
• B. Grizzly uses a single global selector pool for all Mule apps.
• C. Listeners have a shared selector pool for each Mule app; Requesters have a dedicated selector pool for each Mule app.
• D. Grizzly only supports HTTP, not HTTPS.

Answer: (A)

Grizzly being an open-source HTTP transport framework is what sets its role here: it’s Apache’s standard library that provides scalable, non-blocking I/O for HTTP and HTTPS. That means it supports both protocols, not just HTTP, which is exactly why the statement about Grizzly supporting HTTP/S is true. The other options describe a fixed pooling setup that isn’t how Grizzly’s architecture is defined in Mule integrations, and they also incorrectly claim HTTPS isn’t supported. In Mule, Grizzly’s role is to offer the HTTP transport with TLS as needed, not to enforce a universal single global selector pool or a rigid per-app listener/requester pool scheme.