An enterprise application is packaged as an enterprise archive, or EAR, which contains modules of several types. The module types the product recognises are web modules, packaged as WAR files, enterprise bean modules, packaged as JAR files, application client modules, also JAR files, and resource adapter modules, packaged as RAR files. Of the four extensions offered, only JAR corresponds to a module type that can be installed, since it is used for EJB modules and client modules. Option D is correct.
The other extensions do not correspond to enterprise modules. SAR, option A, is a name used by some other application servers for service archives, and it is not an enterprise module type in this product. CAR, option C, is not an enterprise module type either; the term client archive does appear in some other contexts, but the product's application client module uses the JAR extension. BAR, option B, is likewise not a module type in this product.
When an application is installed, the console or wsadmin reads the modules from the EAR and presents each one for mapping to servers and for binding of references. A standalone WAR or JAR may also be installed, in which case the product wraps it in an enterprise application, so the same module types apply. Understanding the module types helps in planning the mapping of modules to targets.
[Reference: Enterprise application modules: WAR, EJB JAR, application client JAR, and RAR; Installing enterprise applications; Application packaging.]