In a Maven BOM, what is the effect of listing modules under dependencyManagement with respect to child projects?

• A. It defines versions and scope for dependencies, but does not automatically add them to child projects; you must still declare them in dependencies.
• B. It automatically adds all listed modules to child projects.
• C. It duplicates dependencies in child pom
• D. It restricts child projects from using those dependencies

Answer: (A)

In a Maven BOM, listing modules under dependencyManagement sets the versions and (optionally) the scope that child projects should use for those dependencies. This centralizes version alignment across modules, so when a child declares a dependency on one of those coordinates without a version, Maven will apply the version defined in the BOM. It does not automatically add those dependencies to every child project; the child must still declare the dependency in its own pom. If a child explicitly specifies a version, that version takes precedence over the BOM’s, allowing overrides when needed.