Microsoft Microsoft Certifications AZ-400 Questions & Answers

• Question 501:

  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 have an approval process that contains a condition. The condition requires that releases be approved by a team leader before they are deployed.

  You have a policy stating that approvals must occur within eight hours.

  You discover that deployment fail if the approvals take longer than two hours.

  You need to ensure that the deployments only fail if the approvals take longer than eight hours.

  Solution: From Pre-deployment conditions, you modify the Time between re-evaluation of gates option.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.

  Approvals and gates give you additional control over the start and completion of the deployment pipeline. Each stage in a release pipeline can be configured with pre-deployment and post-deployment conditions that can include waiting for users to manually approve or reject deployments, and checking with other automated systems until specific conditions are verified.

  References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates

• Question 502:

  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 have an approval process that contains a condition. The condition requires that releases be approved by a team leader before they are deployed.

  You have a policy stating that approvals must occur within eight hours.

  You discover that deployment fail if the approvals take longer than two hours.

  You need to ensure that the deployments only fail if the approvals take longer than eight hours.

  Solution: From Post-deployment conditions, you modify the Time between re-evaluation of gates option.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Use a gate From Pre-deployment conditions instead.

  References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates

• Question 503:

  Your company has a project in Azure DevOps for a new web application.

  The company uses ServiceNow for change management.

  You need to ensure that a change request is processed before any components can be deployed to the production environment.

  What are two ways to integrate ServiceNow into the Azure DevOps release pipeline? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. Define a deployment control that invokes the Service Now SOAP API.

  B. Define a post deployment gate after the deployment to the QA stage.

  C. Define a deployment control that invokes the ServiceNow REST API.

  D. Define a pre deployment gate before the deployment to the Prod stage.

  Correct Answer: AB

  An example of a release pipeline that can be modeled through a release pipeline in shown below:

  

  In this example, a release of a website is created by collecting specific versions of two builds (artifacts), each from a different build pipeline. The release is first deployed to a Dev stage and then forked to two QA stages in parallel. If the deployment succeeds in both the QA stages, the release is deployed to Prod ring 1 and then to Prod ring 2. Each production ring represents multiple instances of the same website deployed at various locations around the globe.

  References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release

• Question 504:

  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:

  1.

  Two resource groups

  2.

  Four Azure virtual machines in one resource group

  3.

  Two Azure SQL databases in other resource group

  You need to recommend a solution to deploy the resources.

  Solution: Create a main template that will deploy the resources in one resource group and a nested template that will deploy the resources in the other resource group.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Use two linked templates, instead of the nested template.

  References: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-linked-templates

• Question 505:

  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:

  1.

  Two resource groups

  2.

  Four Azure virtual machines in one resource group

  3.

  Two Azure SQL databases in other resource group

  You need to recommend a solution to deploy the resources.

  Solution: Create a main template that has two linked templates, each of which will deploy the resources in its respective group.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: A

  To deploy your solution, you can use either a single template or a main template with many related templates. The related template can be either a separate file that is linked to from the main template, or a template that is nested within the main template.

  References: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-linked-templates

• Question 506:

  Your company is concerned that when developers introduce open source libraries, it creates licensing compliance issues.

  You need to add an automated process to the build pipeline to detect when common open source libraries are added to the code base.

  What should you use?

  A. Microsoft Visual SourceSafe

  B. Code Style

  C. Black Duck

  D. Jenkins

  E. SourceGea

  F. OWASP ZAP

  Correct Answer: C

  Secure and Manage Open Source Software Black Duck helps organizations identify and mitigate open source security, license compliance and code-quality risks across application and container portfolios. Black Duck Hub and its plugin for Team Foundation Server (TFS) allows you to automatically find and fix open source security vulnerabilities during the build process, so you can proactively manage risk. The integration allows you to receive alerts and fail builds when any Black Duck Hub policy violations are met.

  Note: WhiteSource would also be a good answer, but it is not an option here.

  References: https://marketplace.visualstudio.com/items?itemName=black-duck-software.hub-tfs

• Question 507:

  Your company is concerned that when developers introduce open source libraries, it creates licensing compliance issues.

  You need to add an automated process to the build pipeline to detect when common open source libraries are added to the code base.

  What should you use?

  A. Microsoft Visual SourceSafe

  B. PDM

  C. WhiteSource

  D. OWASP ZAP

  Correct Answer: C

  WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.

  Azure DevOps integration with WhiteSource Bolt will enable you to:

  1.

  Detect and remedy vulnerable open source components.

  2.

  Generate comprehensive open source inventory reports per project or build.

  3.

  Enforce open source license compliance, including dependencies' licenses.

  4.

  Identify outdated open source libraries with recommendations to update. Note: Black duck would also be a good answer, but it is not an option here. References: https://www.azuredevopslabs.com/labs/vstsextend/WhiteSource/

• Question 508:

  Your company has a project in Azure DevOps for a new application. The application will be deployed to several Azure virtual machines that run Windows Server 2019. You need to recommend a deployment strategy for the virtual machines. The strategy must meet the following requirements:

  Ensure that the virtual machines maintain a consist configuration. Minimize administrative effort to configure the virtual machines.

  What should you include in the recommendation?

  A. Azure Resource Manager templates and the PowerShell Desired State Configuration (DSC) extension for Windows

  B. Deployment YAML and Azure pipeline deployment groups

  C. Azure Resource Manager templates and the Custom Script Extension for Windows

  D. Deployment YAML and Azure pipeline stage templates

  Correct Answer: A

  References: https://azure.microsoft.com/en-us/blog/what-why-how-azure-automation-desired-state-configuration/

• Question 509:

  Your company develops an app for iOS. All users of the app have devices that are members of a private distribution group in Microsoft Visual Studio App Center.

  You plan to distribute a new release of the app.

  You need to identify which certificate file you require to distribute the new release from App Center.

  Which file type should you upload to App Center?

  A. .cer

  B. .pfx

  C. .p12

  D. .pvk

  Correct Answer: C

  A successful IOS device build will produce an ipa file. In order to install the build on a device, it needs to be signed with a valid provisioning profile and certificate. To sign the builds produced from a branch, enable code signing in the configuration pane and upload a provisioning profile (.mobileprovision) and a valid certificate (.p12), along with the password for the certificate.

  References: https://docs.microsoft.com/en-us/appcenter/build/xamarin/ios/

• Question 510:

  You plan to share packages that you wrote, tested, validated, and deployed by using Azure Artifacts.

  You need to release multiple builds of each package by using a single feed. The solution must limit the release of packages that are in development.

  What should you use?

  A. local symbols

  B. views

  C. global symbols

  D. upstream sources

  Correct Answer: B

  Upstream sources enable you to manage all of your product's dependencies in a single feed. We recommend publishing all of the packages for a given product to that product's feed, and managing that product's dependencies from remote feeds in the same feed, via upstream sources. This setup has a few benefits:

  1.

  Simplicity: your NuGet.config, .npmrc, or settings.xml contains exactly one feed (your feed).

  2.

  Determinism: your feed resolves package requests in order, so rebuilding the same codebase at the same commit or changeset uses the same set of packages

  3.

  Provenance: your feed knows the provenance of packages it saved via upstream sources, so you can verify that you're using the original package, not a custom or malicious copy published to your feed

  4.

  Peace of mind: packages used via upstream sources are guaranteed to be saved in the feed on first use; if the upstream source is disabled/removed, or the remote feed goes down or deletes a package you depend on, you can continue to develop and build

  References: https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/upstream-sources?view=vsts