Designing and Implementing Microsoft DevOps Solutions: Integration Strategy for Java Application Builds

Recommended Integration Strategy for Java Application Builds

Question

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 need to recommend an integration strategy for the build process of a Java application. The solution must meet the following requirements:

-> The builds must access an on-premises dependency management system.

-> The build outputs must be stored as Server artifacts in Azure DevOps.

-> The source code must be stored in a Git repository in Azure DevOps.

Solution: Configure the build pipeline to use a Hosted Ubuntu agent pool. Include the Java Tool Installer task in the build pipeline.

Does this meet the goal?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

B

Instead use Octopus Tentacle.

https://explore.emtecinc.com/blog/octopus-for-automated-deployment-in-devops-models

The proposed solution does not fully meet the stated requirements.

The solution recommends configuring the build pipeline to use a Hosted Ubuntu agent pool and including the Java Tool Installer task in the build pipeline. This would allow the build process to access and use the required Java tools for building the application.

However, the solution does not address the requirement for the builds to access an on-premises dependency management system. To meet this requirement, additional configuration would be needed in the build pipeline to connect to the on-premises dependency management system and retrieve the required dependencies during the build process.

Additionally, while the solution proposes storing the build outputs as Server artifacts in Azure DevOps, it does not specify how the build pipeline would push these artifacts to Azure DevOps. Further configuration would be needed to ensure that the build outputs are properly uploaded and stored in Azure DevOps.

Therefore, the proposed solution does not fully meet the stated requirements and the answer is B. No.