Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to update the Azure DevOps strategy of your company.
You need to identify the following issues as they occur during the company's development process:
-> Licensing violations
-> Prohibited libraries
Solution: You implement continuous deployment.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
Instead implement continuous integration.
Note: WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.
https://azuredevopslabs.com/labs/vstsextend/whitesource/No, implementing continuous deployment alone does not address the goal of identifying licensing violations and prohibited libraries during the development process.
Continuous deployment is a practice that involves automatically deploying code changes to production once they pass a set of automated tests. While it can help improve the speed and efficiency of the development process, it does not directly address the issues of licensing violations and prohibited libraries.
To identify licensing violations and prohibited libraries during the development process, you would need to implement additional tools and processes such as:
License compliance tools: These tools can help scan your codebase for any open-source or third-party libraries that may have licensing restrictions. They can also help you track the usage of licensed libraries across different projects and identify any violations.
Dependency scanners: These tools can help scan your codebase for any dependencies on prohibited libraries and flag them for review or removal.
Code reviews: Conducting regular code reviews can help identify any potential licensing or library issues before they become a problem.
Therefore, the correct answer is B. No, implementing continuous deployment alone does not meet the goal of identifying licensing violations and prohibited libraries during the development process.