Which statement best describes manual dependencies in NPM?

Which statement best describes manual dependencies in NPM?

• A. A group can be designated as a parent object, but cannot be a child object.
• B. A group can be designated as a child object, but cannot be a parent object.
• C. A group can be designated as a child object, but a parent object may also be a member of a group.
• D. Parent objects are always outside any group.

Answer: (C)

Manual dependencies in NPM let you define explicit, user-specified relationships between objects rather than relying on automatic topology. The key idea is flexibility in who can appear in a dependency: a group can be the target of a dependency as a child object, meaning the dependency can point to or include an entire group. At the same time, the object that acts as the source (the parent in the relationship) can itself be a member of a group. This combination allows you to organize devices into groups for management while still expressing precise dependency relationships between individual devices and groups as needed. That flexibility is what makes the described statement the best fit: a group can be designated as a child object, and a parent object may also be a member of a group. The other options imply rigid restrictions that manual dependencies do not require, such as excluding groups from being children or preventing parent objects from joining groups.

Manual dependencies in NPM let you define explicit, user-specified relationships between objects rather than relying on automatic topology. The key idea is flexibility in who can appear in a dependency: a group can be the target of a dependency as a child object, meaning the dependency can point to or include an entire group. At the same time, the object that acts as the source (the parent in the relationship) can itself be a member of a group. This combination allows you to organize devices into groups for management while still expressing precise dependency relationships between individual devices and groups as needed.

That flexibility is what makes the described statement the best fit: a group can be designated as a child object, and a parent object may also be a member of a group. The other options imply rigid restrictions that manual dependencies do not require, such as excluding groups from being children or preventing parent objects from joining groups.