Download Microsoft Azure DevOps Solutions.AZ-400.Braindump2go.2019-06-27.44q.vcex

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.        References: https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/register-azurermautomationdscnode?view=azurermps-6.13.0

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.  References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals

Scenario: Visual Studio App Center must be used to centralize the reporting of mobile application crashes and device types in use.  In order to use App Center, you need to opt in to the service(s) that you want to use, meaning by default no services are started and you will have to explicitly call each of them when starting the SDK. Insert the following line to start the SDK in your app's AppDelegate class in the didFinishLaunchingWithOptions method.  MSAppCenter.start("{Your App Secret}", withServices: [MSAnalytics.self, MSCrashes.self]) References: https://docs.microsoft.com/en-us/appcenter/sdk/getting-started/ios

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

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.  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 applications 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.  References: https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key

The Register-AzureRmAutomationDscNode cmdlet registers an Azure virtual machine as an APS Desired State Configuration (DSC) node in an Azure Automation account.  Scenario: The Azure DevOps organization includes: The Docker extension  A deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server        References: https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/register-azurermautomationdscnode

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

Step 1: Create a Desired State Configuration (DSC) configuration file that has an extension of .ps1. Step 2: Run the Import-AzureRmAutomationDscConfiguration Azure Powershell cmdlet The Import-AzureRmAutomationDscConfiguration cmdlet imports an APS Desired State Configuration (DSC) configuration into Azure Automation. Specify the path of an APS script that contains a single DSC configuration.  Example: PS C:\>Import-AzureRmAutomationDscConfiguration -AutomationAccountName "Contoso17"-ResourceGroupName "ResourceGroup01" -SourcePath "C:\DSC\client.ps1" -Force This command imports the DSC configuration in the file named client.ps1 into the Automation account named Contoso17. The command specifies the Force parameter. If there is an existing DSC configuration, this command replaces it.  Step 3: Run the Start-AzureRmAutomationDscCompilationJob Azure Powershell cmdlet The Start-AzureRmAutomationDscCompilationJob cmdlet compiles an APS Desired State Configuration (DSC) configuration in Azure Automation.  References: https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/import-azurermautomationdscconfiguration  https://docs.microsoft.com/en-us/powershell/module/azurerm.automation/start-azurermautomationdsccompilationjob

Scenario:       References: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers

Step 1: Create a repository A Git repository, or repo, is a folder that you've told Git to help you track file changes in. You can have any number of repos on your computer, each stored in their own folder.  Step 2: Create a branch Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards.  Step 3: Add a build validation policy When a build validation policy is enabled, a new build is queued when a new pull request is created or when changes are pushed to an existing pull request targeting this branch. The build policy then evaluates the results of the build to determine whether the pull request can be completed.  Scenario: Implement a code flow strategy for Project2 that will: Enable Team2 to submit pull requests for Project2.  Enable Team2 to work independently on changes to a copy of Project2. Ensure that any intermediary changes performed by Team2 on a copy of Project2 will be subject to the same restrictions as the ones defined in the build policy of Project2.        References: https://docs.microsoft.com/en-us/azure/devops/repos/git/manage-your-branches