A new member of your development team introduced a library from an external source to add functionality. You want to prevent malicious or outdated code and conflicts with usage requirements. Which measure satisfies this requirement while the additions are still in progress?
Carrying out repeated test cycles that confirm new features within a private environment
Using a system that scans third-party files for recognized flaws and restricted usage conditions
Collecting telemetry with an embedded defense mechanism that reacts to suspicious events
Enforcing a manual inspection of all lines to catch errors and logic gaps
A dependency scanner checks known flaws and usage obligations in imported components before finalizing the application. Manual review and repeated tests can catch some problems, but they do not give deep insight into the library's background or potential conflicts. Embedded defense tools monitor issues during runtime, rather than examining the integrity and license status of external code artifacts.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a dependency scanner, and how does it work?
Open an interactive chat with Bash
How does a dependency scanner differ from runtime monitoring tools?
Open an interactive chat with Bash
Why do manual reviews and repeated tests fall short compared to dependency scanning?