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.

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#co
Topic 3, Woodgrove bank
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the button to return to the question.
Overview
General Overview
Woodgrove Bank is a financial services company that has a main office in the United Kingdom.
Technical Requirements and Planned Changes
Planned Changes
Woodgrove Bank plans to implement the following project management changes:
* Implement Azure DevOps for project tracking.
* Centralize source code control in private GitHub repositories.
* Implement Azure Pipelines for build pipelines and release pipelines.
Woodgrove Bank plans to implement the following changes to the identity environment:
* Deploy an Azure AD tenant named woodgrovebank.com.
* Sync the Active Directory domain to Azure AD.
* Configure App1 to use a service principal.
* Integrate GitHub with Azure AD.
Woodgrove Bank plans to implement the following changes to the core apps:
* Migrate App1 to ASP.NET Core.
* Integrate Azure Pipelines and the third-party build tool used to develop App2.
Woodgrove Bank plans to implement the following changes to the DevOps environment:
* Deploy App1 to Azure App Service.
* Implement source control for the DB1 schema.
* Migrate all the source code from TFS1 to GitHub.
* Deploy App2 to an Azure virtual machine named VM1.
* Merge the POC branch into the GitHub default branch.
* Implement an Azure DevOps dashboard for stakeholders to monitor development progress.
Technical Requirements
Woodgrove Bank identifies the following technical requirements:
* The initial databases for new environments must contain both schema and reference data.
* An Azure Monitor alert for VM1 must be configured to meet the following requirements:
* Be triggered when average CPU usage exceeds 80 percent for 15 minutes.
* Calculate CPU usage averages once every minute.
* The commit history of the POC branch must replace the history of the default branch.
* The Azure DevOps dashboard must display the metrics shown in the following table.

* Access to Azure DevOps must be restricted to specific IP addresses.
* Page load times for App1 must be captured and monitored.
* Administrative effort must be minimized.

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/

Explanation

Step 1: Kubectl create
You can add a service account to Tiller using the --service-account <NAME> flag while you're configuring Helm (step 2 below). As a prerequisite, you'll have to create a role binding which specifies a role and a service account name that have been set up in advance.
Example: Service account with cluster-admin role
$ kubectl create -f rbac-config.yaml
serviceaccount "tiller" created
clusterrolebinding "tiller" created
$ helm init --service-account tiller
Step 2: helm init
To deploy a basic Tiller into an AKS cluster, use the helm init command.
Step 3: helm install
To install charts with Helm, use the helm install command and specify the name of the chart to install.
References:
https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm
https://docs.helm.sh/using_helm/#tiller-namespaces-and-rbac

Explanation:
Scenario:

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