Explanation
Service hooks let you run tasks on other services when events happen in your Azure DevOps projects. For example, create a card in Trello when a work item is created or send a push notification to your team's mobile devices when a build fails. You can also use service hooks in custom apps and services as a more efficient way to drive activities when events happen in your projects.
Note: Service hook publishers define a set of events. Subscriptions listen for the events and define actions to take based on the event. Subscriptions also target consumers, which are external services that can run their own actions, when an event occurs.
Reference:
https://docs.microsoft.com/en-us/azure/devops/service-hooks/overview

Explanation
In Visual Designer you enable continuous integration (CI) by:
* Select the Triggers tab.
* Enable Continuous integration.
References:
https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designer

Explanation
You can create a service hook for Azure DevOps Services and TFS with Jenkins.
References:
https://docs.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins

Explanation

Box 1: Secret
Store credential in Azure Key Vault by reference secret stored in key vault.
To reference a credential stored in Azure Key Vault, you need to:
Retrieve data factory managed identity
Grant the managed identity access to your Azure Key Vault. In your key vault -> Access policies -> Add Access Policy, search this managed identity to grant Get permission in Secret permissions dropdown. It allows this designated factory to access secret in key vault.
Create a linked service pointing to your Azure Key Vault.
Create data store linked service, inside which reference the corresponding secret stored in key vault.
Box 2: Access policy
Reference:
https://docs.microsoft.com/en-us/azure/data-factory/store-credentials-in-key-vault

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