AZ-400 practice questions 421–430

1. Question 421 · 540 in bank

   SIMULATION - You have several apps that use an Azure SQL Database 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.

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   1. To enable automatic tuning 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 configured for each database. You can manually configure an individual automatic tuning option, or specify that an option inherits its settings from the server. Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable

   Source: Adapted from community discussion — Christian_garcia_martin

   

   Next question

2. Question 422 · 540 in bank

   HOTSPOT - You use Azure Pipelines to manage the build and deployment of apps. You are planning the release strategies for a new app. You need to choose strategies for the following scenarios: Releases will be made available to users who are grouped by their tolerance for software faults.

   

   ✑ Code will be deployed to enable functionality that will be available in later releases of the app. ✑ When a new release occurs, the existing deployment will remain active to minimize recovery time if a return to the previous version is required. Which strategy should you choose for each scenario? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:

   

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   Box 1: Progressive exposure - Continuous Delivery may sequence multiple deployment ג€ringsג€ for progressive exposure (also known as ג€controlling the blast radiusג€). Progressive exposure groups users who get to try new releases to monitor their experience in ג€rings.ג€ The first deployment ring is often a ג€canaryג€ used to test new versions in production before a broader rollout. CD automates deployment from one ring to the next and may optionally depend on an approval step, in which a decision maker signs off on the changes electronically. CD may create an auditable record of the approval in order to satisfy regulatory procedures or other control objectives. Box 2: Feature flags - Feature flags support a customer-first DevOps mindset, to enable (expose) and disable (hide) features in a solution, even before they are complete and ready for release. Box 3: Blue/green - Blue/green deployments which means that instead of replacing the previous version (here we refer to this version as blue), we bring up the new version (here referred to as the green version) next to the existing version, but not expose it to the actual users right away. On the condition of having successfully validated that the green version works correctly, we will promote this version to the public version by changing the routing configuration without downtime. If something is wrong with the green version we can revert back without users every noticing interruptions. Reference: https://docs.microsoft.com/en-us/azure/devops/learn/what-is-continuous-delivery https://docs.microsoft.com/en-us/azure/devops/migrate/phase-features-with-feature-flags https://medium.com/@denniszielke/continuous-kubernetes-blue-green-deployments-on-azure-using-nginx-appgateway-or-trafficmanager-4490bce29cb

   References

   • Microsoft Learn
   • Microsoft Learn

   

   Next question

3. Question 423 · 540 in bank

   DRAG DROP - You have a project in Azure DevOps. You need to associate an automated test to a test case. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Select and Place:

   

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   The process to associate an automated test with a test case is: 1. Create a test project containing your automated test. What types of tests are supported? 2. Check your test project into an Azure DevOps or Team Foundation Server (TFS) repository. 3. Create a build pipeline for your project, ensuring that it contains the automated test. What are the differences if I am still using a XAML build? 4. Use Visual Studio Enterprise or Professional 2017 or a later version to associate the automated test with a test case as shown below. The test case must have been added to a test plan that uses the build you just defined. Reference: https://docs.microsoft.com/en-us/azure/devops/test/associate-automated-test-with-test-case

   Source: Adapted from community discussion — erico

   

   Next question

4. Question 424 · 540 in bank

   DRAG DROP - You have an Azure Kubernetes Service (AKS) cluster. You need to deploy an application to the cluster by using Azure DevOps. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Select and Place:

   

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   You can set up a CI/CD pipeline to deploy your apps on a Kubernetes cluster with Azure DevOps by leveraging a Linux agent, Docker, and Helm. Step 1: Create a service principle in Azure Active Directory (Azure AD) We need to assign 3 specific service principals with specific Azure Roles that need to interact with our ACR and our AKS. Create a specific Service Principal for our Azure DevOps pipelines to be able to push and pull images and charts of our ACR. Create a specific Service Principal for our Azure DevOps pipelines to be able to deploy our application in our AKS. Step 2: Add a Helm package and deploy a task to the deployment pipeline This is the DevOps workflow with containers: Step 3: Add a Docker Compose task to the deployment pipeline. Dockerfile file is a script leveraged by Docker, composed of various commands (instructions) and arguments listed successively to automatically perform actions on a base image in order to create a new Docker image by packaging the app. Reference: https://cloudblogs.microsoft.com/opensource/2018/11/27/tutorial-azure-devops-setup-cicd-pipeline-kubernetes-docker-helm/

   Source: Adapted from community discussion — Tesshu

   

   Next question

5. Question 425 · 540 in bank

   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?

   • AYes
   • BNo

   Show answer

   Answer: B

   Explanation

   You're right, but still, webforce08 is right that this has nothing to do with "gates". The solution is to increase the timeout in Pre-deployment approvals from 2 to 8hs (as is required by policy)

   Source: Adapted from community discussion — MP270915

   References

   • Microsoft Learn

   Next question

6. Question 426 · 540 in bank

   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?

   • AYes
   • BNo

   Show answer

   Answer: B

   Explanation

   B is correct - Not such option as gates timeout in pre-deployment approvals. Pre-deployment approvals are for manual approvals and gates are for automatic approvals

   Source: Adapted from community discussion — TosO

   References

   • Microsoft Learn
   • Microsoft Learn
   • Microsoft Learn
   • Microsoft Learn

   Next question

7. Question 427 · 540 in bank

   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.

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   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. 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

   

   Next question

8. Question 428 · 540 in bank

   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 Timeout setting for pre-deployment approvals. Does this meet the goal?

   • AYes
   • BNo

   Show answer

   Answer: A

   Explanation

   correct answer is A. We need to increase the pre-deployment condition timeout from 2 to 8 hours. The solution cannot be a gate setting because we have a manual approval step here, not an automatic one.

   Source: Adapted from community discussion — rdemontis

   References

   • Microsoft Learn

   Next question

9. Question 429 · 540 in bank

   DRAG DROP - You are defining release strategies for two applications as shown in the following table.

   

   Which release strategy should you use for each application? To answer, drag the appropriate release strategies to the correct applications. Each release strategy may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Select and Place:

   

   This is an interactive task on the real exam — a drag-and-drop, hotspot or ordering question. There is nothing to select here, so the answer is shown below for reference.

   Show the answer figure

   Answer: See figure below

   Explanation

   App1: Canary deployment - With canary deployment, you deploy a new application code in a small part of the production infrastructure. Once the application is signed off for release, only a few users are routed to it. This minimizes any impact. With no errors reported, the new version can gradually roll out to the rest of the infrastructure. App2: Rolling deployment: In a rolling deployment, an application's new version gradually replaces the old one. The actual deployment happens over a period of time. During that time, new and old versions will coexist without affecting functionality or user experience. This process makes it easier to roll back any new component incompatible with the old components. Incorrect Answers: Blue/Green deployment - A blue/green deployment is a change management strategy for releasing software code. Blue/green deployments, which may also be referred to as A/B deployments require two identical hardware environments that are configured exactly the same way. While one environment is active and serving end users, the other environment remains idle. Blue/green deployments are often used for consumer-facing applications and applications with critical uptime requirements. New code is released to the inactive environment, where it is thoroughly tested. Once the code has been vetted, the team makes the idle environment active, typically by adjusting a router configuration to redirect application program traffic. The process reverses when the next software iteration is ready for release. Reference: https://dev.to/mostlyjason/intro-to-deployment-strategies-blue-green-canary-and-more-3a3

   Source: Adapted from community discussion — motu

   References

   • Microsoft Learn
   • AWS documentation

   

   Next question

10. Question 430 · 540 in bank

    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 Timeout setting for post-deployment approvals. Does this meet the goal?

    • AYes
    • BNo

    Show answer

    Answer: B

    Explanation

    And why the continuous insistence on using a gate instead of using pre-deployment approval in the proposed answer? Pre-deployment approval with a timeout of 8h should do the trick just fine!

    Source: Adapted from community discussion — ArnoudBM

    Next question

Keyboard:J Kmove between questionsA–Dselect an answerRshow or hide the answer← →change page

AZ-400 practice, question 421. 540 questions available.