Download Microsoft.AZ-400.Dump4Pass.2023-12-08.118q.vcex

Instead use Octopus Tentacle.    Reference: https://explore.emtecinc.com/blog/octopus-for-automated-deployment-in-devops-models

Instead use Octopus Tentacle.    Reference: https://explore.emtecinc.com/blog/octopus-for-automated-deployment-in-devops-models

B: Jenkins requires a plug-in to connect to TFS and check for updates to a project. Jenkins’ built-in Git Plugin or Team Foundation Server Plugin can poll a Team Services repository every few minutes and queue a job when changes are detected.    C: Use Azure DevOps/ Visual Studio Team Services to create a Personal access token. D: After you have generated credentials using Visual Studio Team Services, you need to use those credentials in Jenkins.   Reference:   http://www.aisoftwarellc.com/blog/post/how-to-setup-automated-builds-using-jenkins-and-visual-studio-team-foundation-server/2044

Use Publish Code Coverage Results task in a build pipeline to publish code coverage results to Azure Pipelines or TFS, which were produced by a build in  Cobertura or JaCoCo format.    Incorrect Answers: A: Bullseye Coverage is used for C++ code, and not for Java.   Note: There are several versions of this question in the exam. The question has two possible correct answers: Cobertura  JaCoCo    Other incorrect answer options you may see on the exam include the following: Coverlet  NUnit  Coverage.py    Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results

Box 1: Hosted macOS Hosted macOS pool (Azure Pipelines only): Enables you to build and release on macOS without having to configure a self-hosted macOS agent. This option affects where your data is stored.    Box 2: Hosted Hosted pool (Azure Pipelines only): The Hosted pool is the built-in pool that is a collection of Microsoft-hosted agents.   Incorrect Answers: Default pool: Use it to register self-hosted agents that you've set up.   Hosted Windows Container pool (Azure Pipelines only): Enabled you to build and release inside Windows containers. Unless you're building using containers, Windows builds should run in the Hosted VS2017 or Hosted pools.  Hosted Linux/Ubuntu 18.04 does not apply for Mac OS or for Microsoft IIS.  Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents

Use Publish Code Coverage Results task in a build pipeline to publish code coverage results to Azure Pipelines or TFS, which were produced by a build in Cobertura or JaCoCo format.    Incorrect Answers: B: Bullseye Coverage is used for C++ code, and not for Java.   D: If you're building on Linux or macOS, you can use Coverlet or a similar tool to collect code coverage metrics. Code coverage results can be published to the server by using the Publish Code Coverage Results task. To leverage this functionality, the coverage tool must be configured to generate results in Cobertura or JaCoCo coverage format.  F: Coverage.py is used for Python, not for Java. Note: There are several versions of this question in the exam. The question has two possible correct answers: 1. Cobertura  2. JaCoCo    Other incorrect answer options you may see on the exam include the following: 1. Junit  2. NUnit  3. Coverage.py    Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results

When you run a pipeline on a self-hosted agent, by default, none of the subdirectories are cleaned in between two consecutive runs. As a result, you can do incremental builds and deployments, provided that tasks are implemented to make use of that. You can override this behavior using the workspace setting on the job.    Incorrect Answers: B: The workspace clean options are applicable only for self-hosted agents. When using Microsoft-hosted agents job are always run on a new agent.   Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases

The Custom Script Extension downloads and executes scripts on Azure virtual machines. This extension is useful for post deployment configuration, software installation, or any other configuration or management tasks. Scripts can be downloaded from Azure storage or GitHub, or provided to the Azure portal at extension run time. The Custom Script Extension integrates with Azure Resource Manager templates, and can be run using the Azure CLI, PowerShell, Azure portal, or the Azure Virtual Machine REST API.    Incorrect Answers: B: YAML doesn't work with Azure pipeline deployment groups.   Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows

Step 1: Create a DSC metaconfiguration Load up the DSC Configuration into Azure Automation.    Step 2: Copy the metaconfiguration to the virtual machines. Linking the Node Configuration to the Linux Host    Step 3: Add the virtual machines as DSC nodes in Azure Automation. go to DSC Nodes, select your node, and then click Assign node configuration. This step assigns the DSC configuration to the Linux machine.    Next up will be to link the node configuration to the host. Go to the host and press the “Assign node…”-button. Next up you can select your node configuration.

Box 1: mcr.microsoft.com/dotnet/sdk:5.0 The first group of lines declares from which base image we will use to build our container on top of. If the local system does not have this image already, then docker will automatically try and fetch it. The mcr.microsoft.com/dotnet/core/sdk:5.0 comes packaged with the .NET core 5.0 SDK installed, so it's up to the task of building ASP .NET core projects targeting version 5.0    Box 2: dotnet restore The next instruction changes the working directory in our container to be /app, so all commands following this one execute under this context.    COPY *.csproj ./  RUN dotnet restore    Box 3: mcr.microsoft.com/dotnet/aspnet:5.0 When building container images, it's good practice to include only the production payload and its dependencies in the container image. We don't want the .NET core SDK included in our final image because we only need the .NET core runtime, so the dockerfile is written to use a temporary container that is packaged with the SDK called build-env to build the app.    Reference: https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/building-sample-app