Git history: File history is replicated on the client dev machine and can be viewed even when not connected to the server. You can view history in Visual Studio and on the web portal. Note: Azure Repos supports two types of version control: Git and Team Foundation Version Control (TFVC).

Box 1: Azure Boards
Azure Boards can be used to track work with Kanban boards, backlogs, team dashboards, and custom reporting
You can create multiple Trello boards, which are spaces to store tasks (for different work contexts, or even private boards)
You can easily share Trello boards with another person.
Box 2: Azure Pipelines
You can use Bamboo to implement CI/CD (Continuous Integration and Continuous Delivery) for a simple Azure function app using Atlassian Bamboo. Bamboo does continuous delivery of the project from source code to deployment. It has stages including Build, Test and Deploy.
Software teams in every industry are upgrading their continuous delivery pipeline with Bamboo. Easy build import from popular open source tools, user and group import from JIRA, seamless integration with Bitbucket, and native support for Git, Hg, and SVN means you'll be building and deploying like a champ.
Box 3: GitHub repositories
Bitbucket can be used as the Git repository, but you can use any other Git repository (Like TFS Git) for source control of the code.

Explanation: Service hooks in Azure DevOps allow you to trigger actions in other tools based on events that occur in your Azure DevOps project. To automatically add release information to work items associated with a Get commit, you would need to configure a service hook that listens for commit events in your Get repository, and then sends the release information to the appropriate work items.
Here's the steps you can follow to set up a service hook for this purpose: In your Azure DevOps project, navigate to the project settings by clicking on the gear icon in the top right corner of the page.
Select "Service Hooks" from the left-hand menu.
Click on the "New Subscription" button to create a new service hook.
In the "Event" drop-down menu, select "Code pushed" to trigger the service hook when a new code revision is committed to the repository.
In the "Actions" section, select the action that you want to take place when the service hook is triggered. For example, you might use the "Link work items to commits" action to automatically associate work items with the relevant commits. Configure the remaining settings as needed, and then click on the "Create" button to create the service hook.

You can use the combination of Terraform and Yeoman. Terraform is a tool for creating infrastructure on Azure. Yeoman makes it easy to create Terraform modules. Terratest provides a collection of helper functions and patterns for common infrastructure testing tasks, like making HTTP requests and using SSH to access a specific virtual machine. The following list describes some of the major advantages of using Terratest:

• Convenient helpers to check infrastructure - This feature is useful when you want to verify your real infrastructure in the real environment.
• Organized folder structure - Your test cases are organized clearly and follow the standard Terraform module folder structure.
• Test cases are written in Go - Many developers who use Terraform are Go developers. If you're a Go developer, you don't have to learn another programming language to use Terratest.
• Extensible infrastructure - You can extend additional functions on top of Terratest, including Azure-specific features.

E: Exceptions in your live web app are reported by Application Insights. Note: Periodical reports help keep a team informed on how their business critical services are doing. Developers, DevOps/SRE teams, and their managers can be productive with automated reports reliably delivering insights without requiring everyone to sign in the portal. Such reports can also help identify gradual increases in latencies, load or failure rates that may not trigger any alert rules.

A: You can programmatically query Application Insights data to generate custom reports on a schedule. The following options can help you get started quickly:

• Automate reports with Microsoft Flow
• Automate reports with Logic Apps

Answer: See the solution below in explanation.

Explanation: Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps: Select Your Project: Initialize the Main Branch:

Step 2: Implement an Approval Process for the Main Branch
Navigate to Branch Policies:
Enable Required Reviewers:
Add Required Reviewers:
Enable Reset Code Reviewer Votes:
Save Changes:
Step 3: Verify the Approval Process
Create a Pull Request:
Review and Approve:
By following these steps, you will have successfully initialized the main branch and implemented an approval process that adheres to the four-eyes principle, ensuring that every iteration has at least one approval

Answer: See the solution below in explanation.

Explanation: Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps:
Select Your Project:
Initialize the Main Branch:
Step 2: Enable Squash Merge for the Main Branch
Navigate to Branch Policies: Enable Squash Merge: Save Changes:
Step 3: Verify the Squash Merge Policy
Create a Pull Request: Complete the Pull Request

Answer: See the solution below in explanation.

Explanation: Step 1: Create an Action Group
Navigate to Azure Portal:
Access Azure Monitor:
Create Action Group:
Configure Basic Settings:
Step 2: Define Actions
Add Email Notifications:
Notify Resource Owners:
Step 3: Enable Common Alert Schema
Common Alert Schema:
Step 4: Review and Create
Review:
Create:
By following these steps, you will have successfully created an action group named DevOpsAG that emails the specified users and notifies resource owners using the common alert schema

Instead, In Visual Designer you enable continuous integration (CI) by:

• Select the Triggers tab.
• Enable Continuous integration.