[AZ-400] Microsoft Azure DevOps Training: Step By Step Activity Guides/Hands-On Lab Exercise

This blog post gives a walkthrough of the Step-By-Step Activity Guides of [AZ-400] Microsoft Azure DevOps Engineer Expert training program that you must perform to learn this course. You can use these exact steps to bring you and your team for integration with On-Premise & Cloud application to implement, monitor, and maintain Microsoft Azure solutions.

This exam requires DevOps professionals who are capable of combining processes, people, and technologies for continuously delivering services and products that meet business objectives and user needs. The walkthrough of the Step-By-Step Activity Guides of [AZ-400] Microsoft Azure DevOps Engineer Expert training program will prepare you thoroughly for the AZ-400 certification. You could also check out my previous blog to know more about the AZ-400 certification exam. Apart from that, I have also discussed in-depth the AZ-103 certification exam here.

Activity Guides:

I. Register For Azure DevOps Free Account

The first thing you must do is to get a FREE Account for Microsoft Azure DevOps.

Microsoft Azure is one of the top choices for any organization due to its freedom to build, manage, and deploy applications. Here, we will look at how to register for the Microsoft Azure DevOps FREE Trial Account.

Note: Get this first step by step activity guide absolutely FREE from here

After you register for Microsoft Azure DevOps Account, you should get an Email Like below from Microsoft:

II. Linking Azure DevOps and GitHub/Bitbucket

III. Importing a Repo from Github/Bitbucket into Azure DevOps

In this guide, you will learn how to import an existing Git repo from GitHub, Bitbucket, GitLab, or other location into a new or empty existing repo in your project in Azure DevOps.

IV. Creating a new branch and set branch policies and branch security

Here, you’ll learn how to set up permissions to control who can read and update the code in a branch on your Git repo. You can also set permissions for individual users and groups, and inherit and override permissions as needed from your repo permissions. Branch policies help teams protect their important branches of development. Policies enforce your team’s code quality and change management standards.

V. Creating a new CI Pipeline for a sample build using YAML

This guide explains to you how to build and release pipelines using YAML (Yet Another Markup Language). YAML allows them to access the same pipeline features as those using the visual designer, but with a markup file that can be managed like any other source file. YAML build definitions can be added to a project by simply adding their source file to the root of the repository.

VI. Creating a new CI Pipeline for a sample build using GUI

This is a step-by-step guide to create a CI Pipeline from the Azure GUI. CI stands for Continuous Integration, which is a software development practice in which all developers merge code changes in a central repository multiple times a day. With the help of CI, each change in code triggers an automated build-and-test sequence for the given project, providing feedback to the developers who made the

VII. Creating a new CD Pipeline for a sample deployment to Server

So, what is a CD? CD stands for Continuous Delivery, which on top of Continuous Integration adds the practice of automating the entire software release process. Continuous Delivery includes infrastructure provisioning and deployment, which may be manual and consist of multiple stages. After following the procedural steps mentioned in this guide, you’ll learn how to create a new CD pipeline.

VIII. Installing a self-hosted agent

To build your code or deploy your software using Azure Pipelines, you need at least one agent. As you add more code and people, you’ll eventually need more. When your pipeline runs, the system begins one or more jobs. An agent is an installable software that runs one job at a time.

An agent that you set up and manage on your own to run jobs is a self-hosted agent. Self-hosted agents give you more control to install dependent software needed for your builds and deployments. The steps followed in this guide are piecemeal & gradual, and after completing it, you’ll successfully deploy a self-hosted agent.

IX. Creating Azure boards and Kanban boards

With the Azure Boards web service, teams can manage their software projects. It provides a rich set of capabilities including native support for Scrum and Kanban, customizable dashboards, and integrated reporting. These tools can scale as your business grows.

You can quickly and easily start tracking user stories, backlog items, tasks, features, and bugs associated with your project. You track work by adding work items based on the process and work item types available to your project. This guide provides apprehensive know-how on how to create Azure boards and Kanban boards.

X. Creating a Dashboard and how to customize the reports

Gain visibility into your progress by adding one or more widgets or charts to your dashboard. Customizable, highly-configurable dashboards provide you and your teams with the flexibility to share information, monitor progress and trends, and improve your workflow processes. You can tailor your dashboards to share information and monitor your progress.

XI. A key vault in Azure DevOps and how to use it in CI/CD

Azure Key Vault enables Microsoft Azure applications and users to store and use several types of secret/key data:

• Cryptographic keys: Supports multiple key types and algorithms.
• Secrets: Provides secure storage of secrets, such as passwords and database connection strings.
• Certificates: Supports certificates, which are built on top of keys and secrets and add an automated renewal feature.
• Azure Storage: Can manage keys of an Azure Storage account for you.

XII. How to run the load test and create the test case and test suites

Create test plans and test suites to track manual testing for sprints or milestones. That way, you can see when the testing for a specific sprint or milestone is complete.

• Test plans group test suites and individual test cases together. Test plans include static test suites, requirement-based suites, and query-based suites.
• Test suites group test cases into separate testing scenarios within a single test plan. Grouping test cases makes it easier to see which scenarios are complete.
• Test cases validate individual parts of your code or app deployment. You can ensure your code works correctly, has no errors, and meets business and customer requirements.

XIII. How to store the artifacts and how to use it in CI/CD

You can publish and consume many different types of packages and artifacts with Azure Pipelines. Your continuous integration/continuous deployment (CI/CD) pipeline can publish specific package types to their respective package repositories (NuGet, npm, Python, and so on).

XIV. Checking Vulnerabilities using WhiteSource Bolt and Azure DevOps

WhiteSource Bolt is a lightweight open source security and management solution, integrated within Microsoft’s Azure DevOps Services & Azure DevOps Server (formerly TFS) products. It enables you to do the following:

• Detect and remedy vulnerable open source components.
• Generate comprehensive open-source inventory reports per project or build.
• Enforce open source license compliance, including dependencies’ licenses.
• Identify outdated open-source libraries with recommendations to update.

XV. Managing Technical Debt with Azure DevOps and SonarCloud

In this guide, you will be introduced to technical debt, how to configure your Azure Build definitions to use SonarCloud, how to understand the analysis results, and finally how to configure a quality profile to control the ruleset used by SonarCloud for analyzing your project.

Technical debt is the set of problems in a development effort that makes forward progress on customer value inefficient. Technical debt saps productivity by making code hard to understand, fragile, time-consuming to change, difficult to validate, and creates unplanned work that blocks progress.

XVI. Creating a Docker image and push it to Hub

Azure Pipelines can be used to push images to container registries such as Azure Container Registry (ACR), Docker Hub, Google Container Registries, and others. In this step-by-step activity guide, you’ll learn how to create a Docker image and push it to Docker Hub.

Next Task For You

Once you have practiced all the listed hands-on for Microsoft Azure DevOps, you should appear for the Microsoft Azure AZ400 certification. Click here to know all about the Microsoft Azure AZ400 examination.

Click on the Join Waitlist now button below to join the waitlist of our much-awaited AZ-400 Certification Training which will help you clear the exam with flying colors.

The post [AZ-400] Microsoft Azure DevOps Training: Step By Step Activity Guides/Hands-On Lab Exercise appeared first on Oracle Trainings.