microsoft az-400 practice test

Answer:

C

Explanation:
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

Answer:

C

Explanation:
Scenario: Implement Project4 and configure the project to push Docker images to Azure Container Registry.

You use Azure Container Registry Tasks commands to quickly build, push, and run a Docker container image natively within
Azure, showing how to offload your "inner-loop" development cycle to the cloud. ACR Tasks is a suite of features within
Azure Container Registry to help you manage and modify container images across the container lifecycle.
Reference:
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-quickstart-task-cli

Answer:

Explanation:
Scenario:

Step 1: Sign in to Azure Devops by using an account that is assigned the Administrator service connection security role.
Note: Under Agent Phase, click Deploy Service Fabric Application. Click Docker Settings and then click Configure Docker
settings. In Registry Credentials Source, select Azure Resource Manager Service Connection. Then select your Azure
subscription.
Step 2: Create a personal access token..
A personal access token or PAT is required so that a machine can join the pool created with the Agent Pools (read, manage)
scope.
Step 3: Install and register the Azure Pipelines agent on an Azure virtual machine.
By running a Azure Pipeline agent in the cluster, we make it possible to test any service, regardless of type.
References:
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-deploy-container-app-with-cicd-vsts
https://mohitgoyal.co/2019/01/10/run-azure-devops-private-agents-in-kubernetes-clusters/
Implement Continuous Integration

Answer:

Explanation:
Scenario: Implement Project3, Project5, Project6, and Project7 based on the planned changes

Step 1: Open the release pipeline editor.
In the Releases tab of Azure Pipelines, select your release pipeline and choose Edit to open the pipeline editor.
Step 2: Enable Gates.
Choose the pre-deployment conditions icon for the Production stage to open the conditions panel. Enable gates by using the
switch control in the Gates section.
Step 3: Add Query Work items.
Choose + Add and select the Query Work Items gate.
Configure the gate by selecting an existing work item query.

Note: A case for release gate is:
Incident and issues management. Ensure the required status for work items, incidents, and issues. For example, ensure
deployment occurs only if no priority zero bugs exist, and validation that there are no active incidents takes place after
deployment.
References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-
devops#configure-gate Implement Dependency Management

Answer:

A

Explanation:
Change the ConfigurationMode parameter from ApplyOnly to ApplyAndAutocorrect.
The Register-AzureRmAutomationDscNode cmdlet registers an Azure virtual machine as an APS Desired State
Configuration (DSC) node in an Azure Automation account.
Scenario: Current Technical Issue
The test servers are configured correctly when first deployed, but they experience configuration drift over time. Azure
Automation State Configuration fails to correct the configurations.
Azure Automation State Configuration nodes are registered by using the following command.

Reference: https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/register-
azurermautomationdscnode?view=azurermps-6.13.0

Answer:

D

Explanation:
Scenario: A branching strategy that supports developing new functionality in isolation must be used.
Feature isolation is a special derivation of the development isolation, allowing you to branch one or more feature branches
from main, as shown, or from your dev branches.

When you need to work on a particular feature, it might be a good idea to create a feature branch.
Incorrect Answers:
A: Release isolation introduces one or more release branches from main. The strategy allows concurrent release
management, multiple and parallel releases, and codebase snapshots at release time.
B: The Main Only strategy can be folder-based or with the main folder converted to a Branch, to enable additional visibility
features. You commit your changes to the main branch and optionally indicate development and release milestones with
labels.
C: Development isolation: When you need to maintain and protect a stable main branch, you can branch one or more dev
branches from main. It enables isolation and concurrent development. Work can be isolated in development branches by
feature, organization, or temporary collaboration.
Reference: https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops

Answer:

A

Explanation:
When a release is created from a release pipeline that defines approvals, the deployment stops at each point where
approval is required until the specified approver grants approval or rejects the release (or re-assigns the approval to another
user).
Scenario: Code quality and release quality are critical. During release, deployments must not proceed between stages if any
active bugs are logged against the release.
Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals

Answer:

Explanation:
Scenario: By default, all releases must remain available for 30 days, except for production releases, which must be kept for
60 days.
Box 1: Set the default retention policy to 30 days
The Global default retention policy sets the default retention values for all the build pipelines. Authors of build pipelines can
override these values.
Box 2: Set the stage retention policy to 60 days
You may want to retain more releases that have been deployed to specific stages.
References: https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/retention

Answer:

Explanation:
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 Microsofthosted 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.
References:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops
Implement Continuous Delivery

Answer:

C

Explanation:
Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.
Reference: https://docs.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time?view=vsts