1Z0-102 · Question #103
Which three techniques can create a new WebLogic domain?
The correct answer is A. Configuration Wizard C. WLST E. Unpack command. See the full explanation below for the reasoning.
Question
Which three techniques can create a new WebLogic domain?
Options
- AConfiguration Wizard
- BDomain Template Builder
- CWLST
- DAdministration console
- EUnpack command
- FNode Manager
How the community answered
(22 responses)- A73% (16)
- B5% (1)
- D14% (3)
- F9% (2)
Community Discussion
6The answer is A, C, and E. Configuration Wizard is the point-and-click way Oracle has given us since the early WLS 8 days, WLST offline lets you script readTemplate and writeDomain to stamp out domains without a running server, and the unpack command extracts a template JAR produced by pack to lay down a domain skeleton on a remote machine, which is exactly how you provision managed server nodes in a cluster. B trips people up because Domain Template Builder makes templates, not domains, D requires a domain to already exist before you can even log in, and F is Node Manager, which starts and stops servers but has nothing to do with domain creation.
Dragan covered the core three well, but worth flagging that pack and unpack are technically a pair and the unpack command specifically requires the template JAR that pack produced from an existing domain, so it is less an independent creation method and more a remote provisioning step that presupposes a source domain already configured on the admin host.
Think of a WebLogic domain like a new office building. You can get one built three ways: hire an architect who walks you through it room by room, write up your own blueprint instructions for a contractor, or stamp out a copy from a master floor plan somebody already packed up and shipped to you. That maps exactly to A, C, and E here, so yes, the correct answers are Configuration Wizard, WLST, and the Unpack command. The Configuration Wizard is your GUI walkthrough, WLST handles it via scripting with commands like readTemplate and writeDomain, and Unpack creates a domain on a remote machine from a packed template archive, which counts as domain creation on that target host. The Domain Template Builder trips people up because it sounds relevant, but it only creates the template file itself, not an actual domain, same as designing a blueprint is not the same as constructing the building. Node Manager and the Administration Console both operate on domains that already exist, so they have no business being on this list.
Solid breakdown, though worth being precise that WLST can create domains in both offline mode using readTemplate/updateDomain/writeDomain and online mode is not involved in domain creation at all, so the scripting path is specifically an offline WLST operation per the Oracle Fusion Middleware docs.
I initially marked B because the Domain Template Builder sounds like it builds domains, but the Oracle docs clarify it only creates or modifies domain templates, not domains themselves, so the three correct methods per the official WebLogic documentation are A (Configuration Wizard), C (WLST offline via createDomain), and E (the unpack command, which expands a packed domain template into a full domain on a Managed Server host). D is a trap because the Administration Console requires an already-running domain to connect to.
Hiroshi nailed it, and the unpack command trap is especially worth flagging because a lot of test-takers see "unpack" and assume it is only for file distribution, missing that it is doing the actual domain instantiation work on the remote machine.