1Z0-599 · Question #68
A customer stores environmental settings in the deployment descriptors of an application. Whenever they promote the application version from testing to the production environment, they need to open…
The correct answer is B. Keep environmental data in Deployment Plan XML files. WebLogic Server uses the standard J2EE web.xml deployment descriptor for defining a Web Application. Some applications also require the WebLogicspecific deployment descriptor, You use these deployment descriptors to define components and operating parameters for a Web…
Question
A customer stores environmental settings in the deployment descriptors of an application. Whenever they promote the application version from testing to the production environment, they need to open the archive and modify the deployment descriptor. This process is against their security policy. What approach should you recommend to leverage WebLogic features such that they do not have to modify the application archive for different environments?
Options
- AKeep environmental data in the global settings of domain and the application can read it from the
- BKeep environmental data in Deployment Plan XML files.
- CKeep environmental data in the database because it is the most effective way of parametrizing
- DKeep archive in exploded format so the customer does not have to open the archive files.
- EEliminate all environmental settings from the application.
How the community answered
(44 responses)- A9% (4)
- B59% (26)
- C23% (10)
- D2% (1)
- E7% (3)
Explanation
WebLogic Server uses the standard J2EE web.xml deployment descriptor for defining a Web Application. Some applications also require the WebLogicspecific deployment descriptor, You use these deployment descriptors to define components and operating parameters for a Web Application. Deployment descriptors are standard text files, formatted using XML notation. You package them in the Web Application.
Topics
Community Discussion
No community discussion yet for this question.