000-221 · Question #184
When preparing to install a System WPAR using NIM, what action must occur before the planned WPAR can be successfully defined as a NIM client?
The correct answer is C. Define the global environment LPAR as a NIM client. Before a System WPAR can be defined as a NIM client, its host global environment (LPAR) must already be registered as a NIM client, since NIM manages WPARs through their parent LPAR.
Question
When preparing to install a System WPAR using NIM, what action must occur before the planned WPAR can be successfully defined as a NIM client?
Options
- AInstall AIX onto the global environment.
- BRegister the planned hostnames to DNS.
- CDefine the global environment LPAR as a NIM client.
- DCreate an lpp_source with the WPAR-specific backup files.
How the community answered
(53 responses)- A2% (1)
- B6% (3)
- C79% (42)
- D13% (7)
Why each option
Before a System WPAR can be defined as a NIM client, its host global environment (LPAR) must already be registered as a NIM client, since NIM manages WPARs through their parent LPAR.
AIX must already be running on the global LPAR to host a WPAR, so this is a prerequisite long satisfied before WPAR definition, not the immediate required action.
DNS hostname registration aids name resolution but is not a mandatory NIM prerequisite for defining a WPAR as a NIM client.
NIM manages System WPARs through their host AIX global environment LPAR. The NIM server must first have the global LPAR defined as a NIM client so it can communicate with and manage WPARs running within that LPAR. Without this prerequisite, NIM has no path to reach or define the WPAR as a client.
An lpp_source resource is used during NIM software installations, but creating one with WPAR-specific files is not required merely to define the WPAR as a NIM client.
Concept tested: NIM System WPAR client definition prerequisites
Source: https://www.ibm.com/docs/en/aix/7.3?topic=management-system-wpar-nim
Topics
Community Discussion
No community discussion yet for this question.