Explanation
The first thing to do is to declare your Sonar Qube 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
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 Next 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 Question 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.

Explanation
Use Publish Code Coverage Results task in a build pipeline to publish code coverage results to Azure Pipelines or TFS, which were produced by a build in Cobertura or JaCoCo format.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results

See solution below.
Explanation
* Sign in to the Azure portal.
* Navigate to the container registry az40010480345acr1.
* Under Services, select Webhooks.
* Select the existing webhook https://contoso.com/statushook, and double-click on it to get its properties.
* For Trigger actions select image push
Example web hook:

Reference:
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-webhook

Explanation
Scenarios and use cases for gates include:
* Quality validation. Query metrics from tests on the build artifacts such as pass rate or code coverage and deploy only if they are within required thresholds.
Use Quality Gates to integrate monitoring into your pre-deployment or post-deployment. This ensures that you are meeting the key health/performance metrics (KPIs) as your applications move from dev to production and any differences in the infrastructure environment or scale is not negatively impacting your KPIs.
Note: 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.
References:
https://docs.microsoft.com/en-us/azure/azure-monitor/continuous-monitoring
https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops

Explanation

Step 1 : az acr create
An Azure Container Registry (ACR) can also be created using the new Azure CLI.
az acr create
--name <REGISTRY_NAME>
--resource-group <RESOURCE_GROUP_NAME>
--sku Basic
Step 2: az ad sp create-for-rbac
Once the ACR has been provisioned, you can either enable administrative access (which is okay for testing) or you create a Service Principal (sp) which will provide a client_id and a client_secret.
az ad sp create-for-rbac
--scopes
/subscriptions/<SUBSCRIPTION_ID>/resourcegroups/<RG_NAME>/providers/Microsoft.ContainerRegistry/re
--role Contributor
--name <SERVICE_PRINCIPAL_NAME>
Step 3: kubectl create
Create a new Kubernetes Secret.
kubectl create secret docker-registry <SECRET_NAME>
--docker-server <REGISTRY_NAME>.azurecr.io
--docker-email <YOUR_MAIL>
--docker-username=<SERVICE_PRINCIPAL_ID>
--docker-password <YOUR_PASSWORD>
References:
https://thorsten-hans.com/how-to-use-private-azure-container-registry-with-kubernetes