Microsoft AZ-400 Practice Test - Questions Answers

Get started with Python packages in Azure Artifacts

Create a feed

1. Select Artifacts (in the left navigation of your Azure DevOps project).

2. On the Artifacts page, select Create Feed.

3. In the Create new feed dialog box:

4. In the Name field, give the feed a name.

PyPI is the default repository name for twine, which is a tool for publishing Python packages.

Reference:

https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/python-packages

1. Sign in to the portal.

2. Choose template Deploy-lod9940427

3. Select Edit template, and then paste your JSON template code into the code window.

4. Change the ASddressPrefixes to 10.0.0.0/24 in order to support only 256 total IP addresses.

addressSpace":{"addressPrefixes": ["10.0.0.0/24"]},

5. Change the firstSubnet addressprefix to 10.0.0.0/26 to support only 64 total IP addresses.

"subnets":[

{

"name":"firstSubnet",

"properties":{

"addressPrefix":"10.0.0.0/24"

}

6. Select Save.

7. Select Edit parameters, provide values for the parameters that are shown, and then select OK.

8. Select Subscription. Choose the subscription you want to use, and then select OK.

9. Select Resource group. Choose an existing resource group or create a new one, and then select OK.

10. Select Create. A new tile on the dashboard tracks the progress of your template deployment.

Reference:

https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-deploy-template-portal?view=azs-1908

https://docs.microsoft.com/en-us/azure/architecture/building-blocks/extending-templates/update-resource

1. In the Azure portal, navigate to the az400-9940427-main app's management page. In the app's left menu, click Configuration > Application settings.

2. Click New Application settings

3. Enter the following:

Name: MAX_ITEMS

Value: 50

Reference:

https://docs.microsoft.com/en-us/azure/app-service/configure-common

You can use the Azure DevTest Labs Tasks extension that's installed in Azure DevOps to easily integrate your CI/CD build-and-release pipeline with Azure DevTest Labs. The extension installs three tasks:

Create a VM

Create a custom image from a VM

Delete a VM

The process makes it easy to, for example, quickly deploy a "golden image" for a specific test task and then delete it when the test is finished.

Reference:

https://docs.microsoft.com/en-us/azure/lab-services/devtest-lab-integrate-ci-cd-vsts

1. Sign in to the Azure portal.

2. Navigate to the container registry az40010480345acr1.

3. Under Services, select Webhooks.

4. Select the existing webhook https://contoso.com/statushook, and double-click on it to get its properties. 5. For Trigger actions select image push

Example web hook:

Reference:

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-webhook

Cherry-pick a pull request

To copy changes made in a pull request to another branch in your repo, follow these steps:

1. In a completed pull request, select Cherry-pick, or for an active pull request, select Cherry-pick from the ... menu. Cherry-picking a pull request in this way creates a new branch with the copied changes. Merge into a target branch in a second pull request.

2. In Target branch, enter the branch you want to merge the copied changes.

3. In Topic branch name, enter a new branch to contain the copied changes, then select Cherry-pick. 4. Select Create pull request to merge the topic branch into the target branch to complete the cherry-pick.

Reference:

https://docs.microsoft.com/en-us/azure/devops/repos/git/pull-requests

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure- devops&tabs=browser#faq

There are two different ways to deploy templates to Azure DevOps Services. Both methods provide the same results, so choose the one that best fits your workflow. 1. Add a single step to your build pipeline that runs the PowerShell script that’s included in the Azure Resource Group deployment project (Deploy-AzureResourceGroup.ps1). The script copies artifacts and then deploys the template. 2. Add multiple Azure DevOps Services build steps, each one performing a stage task.

The first option has the advantage of using the same script used by developers in Visual Studio and providing consistency throughout the lifecycle.

Reference:

https://docs.microsoft.com/en-us/azure/vs-azure-tools-resource-groups-ci-in-vsts