You have a project in Azure DevOps named Project1. Project1 contains a pipeline that builds a container image named Image1 and pushes Image1 to an Azure container registry named ACR1. Image1 uses a base image stored in Docker Hub. You need to ensure that Image1 is updated automatically whenever the base image is updated. What should you do?
ACR Tasks supports automated container image builds when a container's base image is updated, such as when you patch the OS or application framework in one of your base images. Reference: https://docs.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-base-image-update
Question 372
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 have an Azure DevOps project. Your build process creates several artifacts. You need to deploy the artifacts to on-premises servers. Solution: You deploy an Octopus Deploy server. You deploy a polled Tentacle agent to an on-premises server. You add an Octopus task to the deployment pipeline. Does this meet the goal?
Instead you should deploy an Azure self-hosted agent to an on-premises server. Note: To build your code or deploy your software using Azure Pipelines, you need at least one agent. If your on-premises environments do not have connectivity to a Microsoft-hosted agent pool (which is typically the case due to intermediate firewalls), you'll need to manually configure a self-hosted agent on on-premises computer(s). Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops
Question 373
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 create a release pipeline that will deploy Azure resources by using Azure Resource Manager templates. The release pipeline will create the following resources: - Two resource groups - Four Azure virtual machines in one resource group - Two Azure SQL databases in other resource group You need to recommend a solution to deploy the resources. Solution: Create a main template that will deploy the resources in one resource group and a nested template that will deploy the resources in the other resource group. Does this meet the goal?
Use two linked templates, instead of the nested template. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-linked-templates
Question 374
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 create a release pipeline that will deploy Azure resources by using Azure Resource Manager templates. The release pipeline will create the following resources: - Two resource groups - Four Azure virtual machines in one resource group - Two Azure SQL databases in other resource group You need to recommend a solution to deploy the resources. Solution: Create a main template that has two linked templates, each of which will deploy the resources in its respective group. Does this meet the goal?
To deploy your solution, you can use either a single template or a main template with many related templates. The related template can be either a separate file that is linked to from the main template, or a template that is nested within the main template. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-linked-templates
Question 375
DRAG DROP - You are building an application that has the following assets: - Source code - Logs from automated tests and builds - Large and frequently updated binary assets - A common library used by multiple applications Where should you store each asset? To answer, drag the appropriate Azure services to the correct assets. Each service may be used once. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Select and Place:
Box 1: Azure Repos - Box 2: Azure Artifacts - Use Azure Artifacts to create, host, and share packages with your team. Box 3: Azure Pipelines - In the pipeline view you can see all the stages and associated tests. The view provides a summary of the test results Box 4: Azure Storage - Reference: https://docs.microsoft.com/en-us/azure/devops/repos/get-started/what-is-repos https://azure.microsoft.com/en-us/services/devops/artifacts/ https://docs.microsoft.com/en-us/azure/devops/pipelines/test/review-continuous-test-results-after-build
Question 376
You plan to share packages that you wrote, tested, validated, and deployed by using Azure Artifacts. You need to release multiple builds of each package by using a single feed. The solution must limit the release of packages that are in development. What should you use?
Upstream sources enable you to manage all of your product's dependencies in a single feed. We recommend publishing all of the packages for a given product to that product's feed, and managing that product's dependencies from remote feeds in the same feed, via upstream sources. This setup has a few benefits: - Simplicity: your NuGet.config, .npmrc, or settings.xml contains exactly one feed (your feed). - Determinism: your feed resolves package requests in order, so rebuilding the same codebase at the same commit or changeset uses the same set of packages - Provenance: your feed knows the provenance of packages it saved via upstream sources, so you can verify that you're using the original package, not a custom or malicious copy published to your feed - Peace of mind: packages used via upstream sources are guaranteed to be saved in the feed on first use; if the upstream source is disabled/removed, or the remote feed goes down or deletes a package you depend on, you can continue to develop and build Reference: https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/upstream-sources?view=vsts
Question 377
You have a project in Azure DevOps named Project1. Project1 contains a build pipeline named Pipe1 that builds an application named App1. You have an agent pool named Pool1 that contains a Windows Server 2019-based self-hosted agent. Pipe1 uses Pool1. You plan to implement another project named Project2. Project2 will have a build pipeline named Pipe2 that builds an application named App2. App1 and App2 have conflicting dependencies. You need to minimize the possibility that the two build pipelines will conflict with each other. The solution must minimize infrastructure costs. What should you do?
To get more control over software dependencies and operating system, you can use Container jobs. Note that the decisions whether to run your pipeline inside a container and whether to use a self-hosted agent are independent. You can directly run your pipeline on a self-hosted agent, or inside a container. You can also execute your pipeline in a container on a Microsoft-hosted agent or on a self-hosted agent. Incorrect Answers: A: For additional control over hardware, you can use a self-hosted build agent. Reference: http://thewindowsupdate.com/2019/09/09/resolving-complex-software-and-hardware-dependencies-in-azure-devops-pipelines/
Question 378
SIMULATION - You plan to store signed images in an Azure Container Registry instance named az4009940427acr1. You need to modify the SKU for az4009940427acr1 to support the planned images. The solution must minimize costs. To complete this task, sign in to the Microsoft Azure portal.
1. Open Microsoft Azure Portal, and select the Azure Container Registry instance named az4009940427acr1. 2. Under Policies, select Content Trust > Enabled > Save. Reference: https://docs.microsoft.com/en-us/azure/container-registry/container-registry-content-trust
Question 379
You manage build pipelines and deployment pipelines by using Azure DevOps. Your company has a team of 500 developers. New members are added continually to the team. You need to automate the management of users and licenses whenever possible. Which task must you perform manually?
Incorrect Answers: A: You can seamlessly replace existing solutions with group-based licensing to more easily manage licenses in Azure DevOps. You can use Group rules. C: Member Entitlement Management APIs allow managing Entitlements that include - - License - Extensions - Project/Team memberships Reference: https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/migrate-to-group-based-resource-management?view=vsts&tabs=new-nav https://docs.microsoft.com/en-us/rest/api/azure/devops/memberentitlementmanagement/?view=azure-devops-rest-5.0
Question 380
HOTSPOT - Your company uses Team Foundation Server 2013 (TFS 2013). You plan to migrate to Azure DevOps. You need to recommend a migration strategy that meets the following requirements: - Preserves the dates of Team Foundation Version Control changesets - Preserves the changed dates of work items revisions Minimizes migration effort - - Migrates all TFS artifacts What should you recommend? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: Upgrade TFS to the most recent RTM release. One of the major prerequisites for migrating your Team Foundation Server database is to get your database schema version as close as possible to what is currently deployed in Azure Devops Services. Box 2: Use the TFS Database Import Service In Phase 3 of your migration project, you will work on upgrading your Team Foundation Server to one of the supported versions for the Database Import Service in Azure Devops Services.
