Scenario: Access to Azure DevOps must be restricted to specific IP addresses.
Azure DevOps is authenticated through Azure Active Directory. You can use Azure AD's conditional access to prevent logins from certain geographies and address ranges.
Reference:
https://www.rebeladmin.com/2018/08/step-step-guide-configure-location-based-conditional-access-policies/

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
PMD is a source code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, and so forth.
There is an Apache Maven PMD Plugin which allows you to automatically run the PMD code analysis tool on your project's source code and generate a site report with its results.
References: https://pmd.github.io/
Topic 1, Case Study: 2Overview
Existing Environment
This is a case study Case studies are not limed separately. You can use as much exam time at 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 m 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 the case study, a review screen will appear. This screen allows you to review your answers and to mate 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 on 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.
Requirements
Contoso plans to improve its IT development and operations processes implementing Azue DevOps principles.
Contoso has an Azure subscription and creates an Azure DevOPs organization.
The Azure DevOps organization includes:
* The Docker extension
* A deployment pool named Pool7 that contains 10 Azure virtual machines that run Windows Server
2016.
The Azure subscription contains an Azure Automation account.
Planned Changes
Contoso plans to create projects in Azure DevOps as shown in the following table.

Technical Requirements
Contoso identities the following technical requirements:
* Implement build agents rot Project 1.
* Whenever possible, use Azure resources
*Avoid using deprecated technologies
* Implement a code flow strategy for Project2 that will:
*Enable Team 2 to submit pull requests for Project2.
* Enable Team 2 to work independently on changes to a copy of Project?
* Ensure that any intermediary changes performed by Tram2 on a copy of Project2 will be subject to the same restrictions as the ones defied in the build policy of Project2.
* Whenever possible. Implement automation and minimize administrative effort.
* Implement Protect3, Project5, Project6, and Project7 based on the planned changes.
* Implement Project4 and configure the project to push Docker images to Azure Container Reentry.

Explanation/Reference:
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
A feature typically represents a shippable component of software.
Features, examples:
* Add view options to the new work hub
* Add mobile shopping cart
* Support text alerts
* Refresh the web portal with new look and feel
User Stories and Tasks are used to track work. Teams can choose how they track bugs, either as requirements or as tasks Reference:
https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/define-features-epics
https://docs.microsoft.com/en-us/azure/devops/boards/work-items/about-work-items