Win IT Exam with Last Dumps 2025

Microsoft AZ-400 Exam

Page 40/54
Viewing Questions 391 400 out of 535 Questions
74.07%

Question 391
HOTSPOT -
How should you configure the release retention policy for the investment planning depletions suite? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
AZ-400_391Q.jpg related to the Microsoft AZ-400 Exam
Image AZ-400_391R.jpg related to the Microsoft AZ-400 Exam



Box 1: Shared Access Authorization token
Every request made against a storage service must be authorized, unless the request is for a blob or container resource that has been made available for public or signed access. One option for authorizing a request is by using Shared Key.
Box 2: Azure Storage with HTTPS access
Scenario: The mobile applications must be able to call the share pricing service of the existing retirement fund management system. Until the system is upgraded, the service will only support basic authentication over HTTPS.
The investment planning application suite will include one multi-tier web application and two iOS mobile application. One mobile application will be used by employees; the other will be used by customers.
Reference:
https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key
Design a DevOps Strategy

Question 392
You create NuGet packages and host them via Azure Artifacts.
You want to grant availability to external anonymous users for one of the packages, while keeping the number of publication points to a minimum.
Which of the following actions should you take?



Azure Artifacts introduces the concept of multiple feeds that you can use to organize and control access to your packages.
Packages you host in Azure Artifacts are stored in a feed. Setting permissions on the feed allows you to share your packages with as many or as few people as your scenario requires.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers.
References:
https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/feed-permissions?view=vsts&tabs=new-nav

Question 393
HOTSPOT -
You manage the Git repository for a large enterprise application.
You need to minimize the data size of the repository.
How should you complete the commands? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
AZ-400_393Q.png related to the Microsoft AZ-400 Exam
Image AZ-400_393R.png related to the Microsoft AZ-400 Exam



Box 1: --aggressive -
Cleanup unnecessary files and optimize the local repository:
git gc --aggressive
Box 2: prune -
Prune all unreachable objects from the object database:
git prune
Reference:
https://gist.github.com/Zoramite/2039636

Question 394
SIMULATION -
You plan to deploy a template named D:\Deploy.json to a resource group named Deploy-lod123456789.
You need to modify the template to meet the following requirements, and then to deploy the template:
- The address space must be reduced to support only 256 total IP addresses.
- The subnet address space must be reduced to support only 64 total IP addresses.
To complete this task, sign in to the Microsoft Azure portal.



1. Sign in to the portal.
2. Choose template Deploy-lod123456789
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.
AZ-400_394E_1.jpg related to the Microsoft AZ-400 Exam
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.
AZ-400_394E_2.jpg related to the Microsoft AZ-400 Exam
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

Question 395
You need to the merge the POC branch into the default branch. The solution must meet the technical requirements.
Which command should you run?



The commit history of the POC branch must replace the history of the default branch.
Rebasing is the process of moving or combining a sequence of commits to a new base commit. Rebasing is most useful and easily visualized in the context of a feature branching workflow. The general process can be visualized as the following:
AZ-400_395E.jpg related to the Microsoft AZ-400 Exam
Note: The primary reason for rebasing is to maintain a linear project history. For example, consider a situation where the main branch has progressed since you started working on a feature branch. You want to get the latest updates to the main branch in your feature branch, but you want to keep your branch's history clean so it appears as if you've been working off the latest main branch. This gives the later benefit of a clean merge of your feature branch back into the main branch. Why do we want to maintain a "clean history"? The benefits of having a clean history become tangible when performing Git operations to investigate the introduction of a regression.
Incorrect:
Not B: git-merge - Join two or more development histories together.
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 adds all the file changes to a single new commit on the default branch.
Not D: git merge --allow-unrelated-histories
By default, git merge command refuses to merge histories that do not share a common ancestor. This option can be used to override this safety when merging histories of two projects that started their lives independently. As that is a very rare occasion, no configuration variable to enable this by default exists and will not be added.
Reference:
https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase


Question 396
SIMULATION -
You need to configure an Azure web app named az400-123456789-main to contain an environmental variable named `MAX_ITEMS`. The environmental variable must have a value of 50.
To complete this task, sign in to the Microsoft Azure portal.



1. In the Azure portal, navigate to the az400-123456789-main app's management page. In the app's left menu, click Configuration > Application settings.
AZ-400_396E.png related to the Microsoft AZ-400 Exam
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

Question 397
SIMULATION -
You need to configure an Azure web app named az400-9940427-main to contain an environmental variable named `MAX_ITEMS`. The environmental variable must have a value of 50.
To complete this task, sign in to the Microsoft Azure portal.



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.
AZ-400_397E.png related to the Microsoft AZ-400 Exam
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

Question 398
In Azure DevOps, you create Project3.
You need to meet the requirements of the project.
What should you do first?



The first thing to do is to declare your SonarQube server as a service endpoint in your VSTS/DevOps project settings.
Reference:
https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Extension+for+vsts-TFS

Question 399
DRAG DROP -
You provision an Azure Kubernetes Service (AKS) cluster that has RBAC enabled. You have a Helm chart for a client application.
You need to configure Helm and Tiller on the cluster and install the chart.
Which three commands should you recommend be run in sequence? To answer, move the appropriate commands from the list of commands to the answer area and arrange them in the correct order.
Select and Place:
AZ-400_399Q.png related to the Microsoft AZ-400 Exam
Image AZ-400_399R.png related to the Microsoft AZ-400 Exam



Step 1: Kubectl create -
You can add a service account to Tiller using the --service-account <NAME> flag while you're configuring Helm (step 2 below). As a prerequisite, you'll have to create a role binding which specifies a role and a service account name that have been set up in advance.
Example: Service account with cluster-admin role
$ kubectl create -f rbac-config.yaml
serviceaccount "tiller" created
clusterrolebinding "tiller" created
$ helm init --service-account tiller
Step 2: helm init -
To deploy a basic Tiller into an AKS cluster, use the helm init command.
Step 3: helm install -
To install charts with Helm, use the helm install command and specify the name of the chart to install.
Reference:
https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm
https://docs.helm.sh/using_helm/#tiller-namespaces-and-rbac

Question 400
Your company builds a multi-tier web application.
You use Azure DevOps and host the production application on Azure virtual machines.
Your team prepares an Azure Resource Manager template of the virtual machine that you will use to test new features.
You need to create a staging environment in Azure that meets the following requirements:
- Minimizes the cost of Azure hosting
- Provisions the virtual machines automatically
- Uses the custom Azure Resource Manager template to provision the virtual machines
What should you do?



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