Free AZ-400 Practice Exam Questions

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 single standalone template that will deploy all the resources. Does this meet the goal?

A. Yes

B. No

A. Yes

Explanation: Use two templates, one for each resource group, and link the templates.

Your company uses a Git repository in Azure Repos lo manage the source code of a web application. The master branch is protected from direct updates. Developers work on new features in the topic branches. Because of the high volume of requested features, it is difficult to follow the history of the changes to the master branch. You need to enforce a pull request merge strategy. The strategy must meet the following requirements:

Consolidate commit histories
Merge tie changes into a tingle commit

Which merge strategy should you use in the branch policy?

A. Git fetch

B. no-fast-forward merge

C. squash merge

D. fast-forward merge

C. squash merge

Explanation:
Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge takes all the file changes and adds them to a single new commit on the default branch.
A simple way to think about this is that squash merge gives you just the file changes, and a regular merge gives you the file changes and the commit history.
Note: Squash merging keeps your default branch histories clean and easy to follow without demanding any workflow changes on your team. Contributors to the topic branch work how they want in the topic branch, and the default branches keep a linear history through the use of squash merges. The commit history of a master branch updated with squash merges will have one commit for each merged branch. You can step through this history commit by commit to find out exactly when work was done.

You have a private GitHub repository. You need to display the commit status of the repository on Azure Boards. What should you do first?

A. Create a GitHub action in GitHub

B. Add the Azure Pipelines app to the GitHub repository

C. Configure multi-factor authentication (MFA) for your GitHub account

D. Add the Azure Boards app to the repository.

Explanation:
To connect Azure Boards to GitHub.com, connect and configure from Azure Boards. Or, alternatively, install and configure the Azure Boards app from GitHub. Both methods have been streamlined and support authenticating and operating via the app rather than an individual.
Note (see step 4 below):
Add a GitHub connection:
Sign into Azure Boards.
Choose (1) Project Settings, choose (2) GitHub connections and then (3) Connect your GitHub account.
If this is your first time connecting to GitHub from Azure Boards, you will be asked to sign in using your GitHub credentials. Choose an account for which you are an administrator for the repositories you want to connect to.
The Add GitHub Repositories dialog automatically displays and selects all GitHub.com repositories for which you are an administrator. Unselect any repositories that you don't want to participate in the integration.

You have a multi-tier application. The front end of the application is hosted in Azure App Service. You need to identify the average load times of the application pages. What should you use?

A. the diagnostics logs of the App Service

B. Azure Application Insights

C. Azure Advisor

D. the activity log of the App Service

B. Azure Application Insights

You have an app named App1 that uses Application Insights to monitor application performance. You need to analyze how often a page in App1 is accessed. Which pane in Application Insights should you use?

A. Events

B. Sessions

C. Impact

D. Users

AZ-400 Practice Test