You plan to use Terraform to deploy an Azure resource group. You need to install the required frameworks to support the planned deployment. Which two frameworks should you install? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
A. Vault
B. Terratest
C. Node.js
D. Yeoman
E. Tiller
You can use the combination of Terraform and Yeoman. Terraform is a tool for creating infrastructure on Azure. Yeoman makes it easy to create Terraform modules. Terratest provides a collection of helper functions and patterns for common infrastructure testing tasks, like making HTTP requests and using SSH to access a specific virtual machine. The following list describes some of the major advantages of using Terratest: - Convenient helpers to check infrastructure - This feature is useful when you want to verify your real infrastructure in the real environment. - Organized folder structure - Your test cases are organized clearly and follow the standard Terraform module folder structure. - Test cases are written in Go - Many developers who use Terraform are Go developers. If you're a Go developer, you don't have to learn another programming language to use Terratest. - Extensible infrastructure - You can extend additional functions on top of Terratest, including Azure-specific features. Reference: https://docs.microsoft.com/en-us/azure/developer/terraform/create-base-template-using-yeoman https://docs.microsoft.com/en-us/azure/developer/terraform/test-modules-using-terratest
Question 322
DRAG DROP - Your company has two virtual machines that run Linux in a third-party public cloud. You plan to use the company's Azure Automation State Configuration implementation to manage the two virtual machines and detect configuration drift. You need to onboard the Linux virtual machines. You install PowerShell Desired State Configuration (DSC) on the virtual machines, and then run register.py. Which three actions should you perform next in sequence? To answer, move the actions from the list of actions to the answer area and arrange them in the correct order. Select and Place:
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.
Question 323
HOTSPOT - Where should the build and release agents for the investment planning applications suite run? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Box 1: A source control system - A source control system, also called a version control system, allows developers to collaborate on code and track changes. Source control is an essential tool for multi-developer projects. Box 2: A hosted service - To build and deploy Xcode apps or Xamarin.iOS projects, you'll need at least one macOS agent. If your pipelines are in Azure Pipelines and a Microsoft-hosted agent meets your needs, you can skip setting up a self-hosted macOS agent. Scenario: The investment planning applications suite will include one multi-tier web application and two iOS mobile applications. One mobile application will be used by employees; the other will be used by customers. Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops
Question 324
DRAG DROP - You are creating a container for an ASP.NET Core app. You need to create a Dockerfile file to build the image. The solution must ensure that the size of the image is minimized. How should you configure the file? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. 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: 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
Question 325
DRAG DROP - You are configuring the settings of a new Git repository in Azure Repos. You need to ensure that pull requests in a branch meet the following criteria before they are merged: - Committed code must compile successfully. - Pull requests must have a Quality Gate status of Passed in SonarCloud. Which policy type should you configure for each requirement? To answer, drag the appropriate policy types to the correct requirements. Each policy type may be used once, more than once, or not at all. 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: A check-in policy - Administrators of Team Foundation version control can add check-in policy requirements. These check-in policies require the user to take actions when they conduct a check-in to source control. By default, the following check-in policy types are available: - Builds Requires that the last build was successful before a check-in. - Code Analysis Requires that code analysis is run before check-in. - Work Items Requires that one or more work items be associated with the check-in. Box 2: Build policy - Reference: https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies https://azuredevopslabs.com/labs/vstsextend/sonarcloud/
Question 326
You use a Git repository in Azure Repos to manage the source code of a web application. Developers commit changes directly to the default branch. You need to implement a change management procedure that meets the following requirements: - The default branch must be protected, and new changes must be built in the feature branches first. - Changes must be reviewed and approved by at least one release manager before each merge. - Changes must be brought into the default branch by using pull requests. What should you configure in Azure Repos?
A. branch policies of the default branch
B. Services in Project Settings
C. Deployment pools in Project Settings
D. branch security of the default branch
Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards. Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies
Question 327
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. Your company uses Azure DevOps to manage the build and release processes for applications. You use a Git repository for applications source control. You need to implement a pull request strategy that reduces the history volume in the master branch. Solution: You implement a pull request strategy that uses fast-forward merges. Does this meet the goal?
A. Yes
B. No
No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch. Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies
Question 328
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. Your company uses Azure DevOps to manage the build and release processes for applications. You use a Git repository for applications source control. You need to implement a pull request strategy that reduces the history volume in the master branch. Solution: You implement a pull request strategy that uses squash merges. Does this meet the goal?
A. Yes
B. No
Instead use fast-forward merge. Note: Squash merge - Complete all pull requests with a squash merge, creating a single commit in the target branch with the changes from the source branch. No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch. Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies
Question 329
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. Your company uses Azure DevOps to manage the build and release processes for applications. You use a Git repository for applications source control. You need to implement a pull request strategy that reduces the history volume in the master branch. Solution: You implement a pull request strategy that uses an explicit merge. Does this meet the goal?
A. Yes
B. No
Instead use fast-forward merge. Note: No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch. Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies
Question 330
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. Your company uses Azure DevOps to manage the build and release processes for applications. You use a Git repository for applications source control. You need to implement a pull request strategy that reduces the history volume in the master branch. Solution: You implement a pull request strategy that uses a three-way merge. Does this meet the goal?
A. Yes
B. No
Instead use fast-forward merge. Note: No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch. Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies
