WebSphere Application Server's containers provide the runtime environments for different component types. The web container processes requests for servlets, JavaServer Pages, and static content that is packaged in a web module. When a web application, packaged in an EAR, includes static files such as HTML pages, images, or stylesheets, the web container serves them. A request that reaches the application server is handled by the web container's default file serving behaviour, which is provided by the file serving servlet in the web application, and the page is sent back to the client. Option C is correct.
The other components do not serve web pages. The client container, option A, runs application client modules, which are stand-alone Java client programs, and it is on the client side. The EJB container, option B, manages enterprise beans and their lifecycle, transactions, and security, and it does not respond to HTTP requests. The HTTP server, option D, is IBM HTTP Server or another web server placed in front of the application server; it can serve static content if that content is placed on the web server itself, but a page deployed inside the EAR is served by the application server's web container, unless the web server has been configured to hold a copy.
For static content with heavy traffic, administrators often offload it to the web server or a content delivery network, using file serving and plug-in settings to reduce the application server's load.
[Reference: Web container; Web modules and static content; File serving enabled in web applications.]