The deployment configuration for an application or module is NOT stored in which type of the following XML document:

Dragan P.Jun 20, 2026

D is your answer, and if you burn that into your brain now you will not second-guess it on exam day. config.xml is the domain configuration document, it holds topology, server definitions, cluster membership, JDBC and JMS resources, and security realm wiring, none of which is application deployment descriptor content. The J2EE standard descriptors like web.xml and ejb-jar.xml, the WebLogic extension descriptors like weblogic.xml and weblogic-ejb-jar.xml, and the deployment plan all participate directly in describing how an application or module deploys and behaves at runtime. The plan in particular was introduced specifically so you could override descriptor values per environment without touching the archive, which is the whole point of separating deployment configuration from domain configuration. Oracle has maintained this separation since WLS 9.0 and MOS Note 1305139.1 spells out the relationship between these artifacts if you want the official reference before sitting the exam.

Hiroshi T.Jun 10, 2026

The correct answer is D, and this is a point the official Oracle WebLogic Server documentation makes clearly. The config.xml file is the domain configuration file, it records server settings, network channels, data sources, and other domain-level resources, but it is not where you store deployment configuration for individual applications or modules. Deployment configuration lives in J2EE standard deployment descriptors (option A), WebLogic-specific weblogic-*.xml descriptors (option B), and WebLogic deployment plans (option C), which the Deployer utility and console use to manage module-level settings without touching the domain config. If you see a question on the exam that tries to conflate domain infrastructure configuration with application deployment configuration, this distinction is exactly what they are testing.

Mateus R.Jun 26, 2026

Okay so I keep coming back to B on this one and here is my thinking. Picture a restaurant kitchen: the J2EE deployment descriptors are the recipe card that any chef anywhere can read, the WebLogic deployment plan is the manager's last-minute note that says "swap the salt for low-sodium tonight," and config.xml is the building's master blueprint covering every room and utility. The weblogic-*.xml files, though, those are more like the waiter's cheat sheet for which table gets which substitution, meaning they handle runtime-binding details like JNDI mappings and connection pool references, not the actual deployment configuration itself. The deployment configuration is the "where does this app live and how is it wired up" question, and weblogic-*.xml answers a narrower question: "how do the app's internal names map to the server's real resources." That is a layer below deployment config, not deployment config itself. So when the question asks what does NOT store deployment configuration, B is the one that gets disqualified because its whole job is resource resolution, not deployment setup.