Designing and Implementing Microsoft DevOps solutions (AZ-400T00)

After completing this course, students will be able to:

• Plan for the transformation with shared goals and timelines
• Select a project and identify project metrics and KPIs
• Create a team and agile organization structure
• Describe the benefits of using Source Control
• Migrate from TFVC to Git
• Scale Git for Enterprise DevOps
• Recommend artifact management tools and practices
• Abstract common packages to enable sharing and reuse
• Migrate and consolidate artifacts
• Migrate and integrate source control measures
• Manage application config and secrets
• Develop a project quality strategy
• Plan for secure development practices and compliance rules
• Implement and manage build infrastructure
• Explain why continuous integration matters
• Implement continuous integration using Azure DevOps
• Manage code quality including: technical debt, SonarCloud, and other tooling solutions
• Manage security policies with open source, OWASP, and WhiteSource Bolt
• Implement a container strategy including how containers are different from virtual machines and how microservices use containers
• Implement containers using Docker
• Inspect open source software packages for security and license compliance to align with corporate standards
• Configure build pipeline to access package security and license rating
• Configure secure access to package feeds
• Inspect codebase to identify code dependencies that can be converted to packages
• Identify and recommend standardized package types and versions across the solution
• Refactor existing build pipelines to implement version strategy that publishes packages
• Manage security and compliance
• Differentiate between a release and a deployment
• Define the components of a release pipeline
• Explain things to consider when designing your release strategy
• Classify a release versus a release process and outline how to control the quality of both
• Describe the principle of release gates and how to deal with release notes and documentation
• Explain deployment patterns, both in the traditional sense and in the modern sense
•  Choose a release management tool 
• Explain the terminology used in Azure DevOps and other Release Management Tooling 
• Describe what a Build and Release task is, what it can do, and some available deployment tasks 
• Classify an Agent, Agent Queue, and Agent Pool 
• Explain why you sometimes need multiple release jobs in one release pipeline 
• Differentiate between multi-agent and multi-configuration release job 
• Use release variables and stage variables in your release pipeline 
• Deploy to an environment securely using a service connection 
• Embed testing in the pipeline 
• List the different ways to inspect the health of your pipeline and release by using alerts, service hooks, and reports 
• Create a release gate 
• Describe deployment patterns 
• Implement Blue Green Deployment 
• Implement Canary Release 
• Implement Progressive Exposure Deployment 
• Configure crash report integration for client applications 
• Develop monitoring and status dashboards 
• Implement routing for client application crash report data 
• Implement tools to track system usage, feature usage, and flow 
• Integrate and configure ticketing systems with development team's work management 
• Implement a mobile DevOps strategy
• Apply infrastructure and configuration as code principles. 
• Deploy and manage infrastructure using Microsoft automation technologies such as ARM templates, PowerShell, and Azure CLI 
• Describe deployment models and services that are available with Azure
• Deploy and configure a Managed Kubernetes cluster 
• Deploy and configure infrastructure using 3rd party tools and services with Azure, such as Chef, Puppet, Ansible, SaltStack, and Terraform 
• Define an infrastructure and configuration strategy and appropriate toolset for a release pipeline and application infrastructure 
• Implement compliance and security in your application infrastructure 
• Design practices to measure end-user satisfaction 
• Design processes to capture and analyze user feedback from external sources 
• Design routing for client application crash report data 
• Recommend monitoring tools and technologies 
• Recommend system and feature usage tracking tools 
• Analyze alerts to establish a baseline 
• Analyze telemetry to establish a baseline 
• Perform live site reviews and capture feedback for system outages 
• Perform ongoing tuning to reduce meaningless or non-actionable alerts

Audience: