Free Preparation Discussions
MENU
Microsoft AZ-400 Exam Questions
- Topic 1: Design and implement processes and communications: The topic includes the design and implementation of traceability and the flow of work, along with establishing appropriate metrics and queries for DevOps. It also involves configuring collaboration and communication strategies to ensure smooth operations.
- Topic 2: Design and implement a source control strategy: Under this topic, the focus is on creating effective branching strategies for source code. Additionally, configuring and managing repositories is an essential component to support version control and code integrity.
- Topic 3: Design and implement build and release pipelines: The topic covers designing a package management strategy, as well as developing a testing strategy for pipelines. It also includes implementing pipelines and deployments, utilizing infrastructure as code (IaC), and maintaining these pipelines.
- Topic 4: Develop a security and compliance plan: The topic involves designing and implementing authentication and authorization methods. It also covers strategies for managing sensitive information in automation and automating security and compliance scanning processes.
- Topic 5: Implement an instrumentation strategy: In this topic, the key areas include configuring monitoring for a DevOps environment. Additionally, it focuses on analyzing metrics derived from instrumentation to optimize system performance and reliability.
Free Microsoft AZ-400 Exam Actual Questions
Note: Premium Questions for AZ-400 were last updated On May. 07, 2025 (see below)
Your company uses Azure DevOps for the build pipelines and deployment pipelines of Java-based projects.
You need to recommend a strategy for managing technical debt.
Which action should you include in the recommendation?
You can manage technical debt with Sonar Rube and Azure DevOps.
Note: Technical debt is the set of problems in a development effort that make forward progress on customer value inefficient. Technical debt saps productivity by making code hard to understand, fragile, time-consuming to change, difficult to validate, and creates unplanned work that blocks progress. Unless they are managed, technical debt can accumulate and hurt the overall qualityof the software and the productivity of the development team in the long term
SonarQube an open source platform for continuous inspection of code quality to perform automatic reviews with static analysis of code to:
Detect Bugs
Code Smells
Security Vulnerabilities
Centralize Quality
What's covered in this lab
https://azuredevopslabs.com/labs/vstsextend/sonarqube/
SIMULATION
You have several apps that use an Azure SQLDatabase named db1.
You need to ensure that queries to db1 are tuned by Azure over time. The solution must only apply to db1.
To complete this task, sign in to the Microsoft Azure portal.
1. To enable automatictuning on a single database, navigate to the database in the Azure portal and select Automatic tuning.
2. Select the automatic tuning options you want to enable and select Apply.
Note: Individual automatic tuning settings can be separately configuredfor each database. You can manually configure an individual automatic tuning option, or specify that an option inherits its settings from the server.
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable
You have a GitHub repository that uses GitHub Actions and stores access keys by using GitHub encrypted secrets.
You plan to update the secrets by using the GitHub REST API.
You need to wrap the secrets before adding them to a REST-based call.
Which encryption library should you are that you use?
SIMULATION
Task 7
Initialize the default main branch, if it does not exist already
In the User 1-42147509 organization, you need to install the Microsoft Security DevOps extension.
Next, create a new starter pipeline named starter1 that will use the following starter code.
Ensure that starter! includes a task that executes the extension and uses the following input*:
* Command: run
* Policy aruredevops
* Publish: true
Save the pipeline to a new branch named starter
Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps:
Go toAzure DevOpsand sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Initialize the Main Branch:
Go toRepos>Files.
Step 2: Install the Microsoft Security DevOps Extension
Navigate to Extensions:
In Azure DevOps, click on theShopping Bagicon in the top right corner and selectBrowse Marketplace.
Search for the Extension:
Search forMicrosoft Security DevOps.
Install the Extension:
Click onGet it free.
Select your organization (User1-42147509) and clickInstall.
Follow the prompts to complete the installation2.
Step 3: Create a New Starter Pipeline
Navigate to Pipelines:
Go toPipelines>New pipeline.
Select the Repository:
ChooseAzure Repos Gitand select the relevant repository.
Configure the Pipeline:
SelectStarter pipelineand replace the default YAML with the following starter code:
trigger:
- starter
pool:
vmImage: 'windows-latest'
steps:
- task: MicrosoftSecurityDevOps@1
inputs:
command: 'run'
policy: 'azuredevops'
publish: true
Save the Pipeline:
Click onSaveand enterstarteras the branch name.
Click onSave and runto save the pipeline to the new branch namedstarter3.
SIMULATION
Task 6
Initialize the default main branch, if it does not exist already.
For Project 1, you need to implement branch merging restrictions to enable squash merge for all changes merged into the main branch.
Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps:
Go to Azure DevOps and sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Initialize the Main Branch:
Go toRepos>Files.
Step 2: Enable Squash Merge for the Main Branch
Navigate to Branch Policies:
Go toRepos>Branches.
Find themainbranch and click on the...(ellipsis) next to it.
SelectBranch policies.
Enable Squash Merge:
UnderPolicies, scroll down to theMerge strategysection.
SelectSquash mergeas the required merge strategy2.
Save Changes:
Click onSave changesto apply the policies.
Step 3: Verify the Squash Merge Policy
Create a Pull Request:
Make a change in a branch and create a pull request to merge it into the main branch.
Complete the Pull Request:
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Antonio
14 days agoErick
16 days agoXuan
2 months agoDwight
2 months agoGarry
2 months agoIzetta
3 months agoEdison
3 months agoDino
3 months agoJamey
4 months agoVilma
4 months agoTwanna
4 months agoTawna
4 months agoWilliam
5 months agoRicki
5 months agoKattie
5 months agoGeoffrey
5 months agoDulce
5 months agoCherelle
5 months agoBillye
6 months agoAmber
6 months agoTula
6 months agoThea
6 months agoBrittani
7 months agoRoy
7 months agoEttie
7 months agoJannette
7 months agoLindsay
7 months agoBev
8 months agoGwenn
8 months agoGlendora
8 months agoVernell
8 months agoAlison
8 months agoMarguerita
9 months agoLacresha
9 months agoSalley
10 months agoJanae
10 months agoYoulanda
10 months agoAmber
11 months agoTyisha
11 months ago