App Development Tools and Technologies Practice Test

Transitive dependencies are the libraries pulled in by the libraries you directly include. In a mobile project, they can creep in unseen, adding additional versions and libraries to your build. This often leads to version conflicts when different dependencies require different versions of the same library, which can break builds or cause runtime crashes. It also contributes to bloat—more code, resources, and potentially duplicate classes—making the app larger and slower to start. That combination is the core risk, so the option describing dependencies of dependencies that can cause version conflicts or bloat is the best fit. The other statements miss the real impact: transitive dependencies don’t inherently streamline the dependency tree, aren’t guaranteed to be compatible across all modules, and don’t by themselves speed up startup time; they usually add overhead instead.