As an Oracle WebLogic Server administrator, you are given an EAR file application to deploy.
Identity three reasons for creating an EAR file first.
A.
After the .ear file has been deployed, the developer will not have to ask for your assistance to
deploy it again.
B.
The EAR file is created to avoid namespace clashes in the Java code.
C.
The EAR file can contain multiple WAR, EAR, and other resources to easily bundle together.
D.
The EAR file is required if you are deploying an application.
E.
The EAR file can declare application-wide security roles definitions.
Explanation:
E: An EARfile contains:
* Web module
A WAR file containing the view logics like JSPs, Servlets, Html contents. Every web module must
have one Web Deployment descriptor placed inside “WEB-INF/web.xml”
web.xml is a J2EE standard deployment descriptor. Among other settings, it has a set of elements
for configuring security for the web application.
Note:
* An EAR file provides a convenient way to bundle up all pieces of a J2EE application. It may
contain Java Module, WAR Module or an EJB Jar module.
An EAR can contain at least any one of these modules. EAR may contain more Modules as well.
* To bring your portal online in a production environment, it is first necessary to prepare your portal
application. Typical preparation steps include modifying deployment descriptors for the product,building the Enterprise archive (EAR) with all its pre-compiled classes, and deciding if you want to
compress that EAR into an archive or leave it exploded.
Reference: Preparing and Deploying the EAR File
Looks like answer is not correct. Correct answer is like B, C, E
An EAR file provides a convenient way to bundle up all pieces of a J2EE application. It may
contain Java Module, WAR Module or an EJB Jar module.
An EAR can contain at least any one of these modules. EAR may contain more Modules as well.
Ans should be B,C,E
An ear cannot contain another ear. C is not correct.
Correct answer: ABE
I don’t think A is the right answer, for the reason of An update of apps will need redeploy the ear package .
I don’t think A is the right answer, for the reason of ear package is none business of the app namespace .
So, in my opinion CDE are the three right answers.
B,D,E We to create a EAR if we are deploying a application
I think D its correct. An ear cannot contain another Ear file, so we can discard C. According to documentation, E could be correct, buy it mentions “The EAR file can declare application-wide security roles definitions.” I’m not sure if deploying ear file can manage security roles definition