AZ-400T05: Implementing Application Infrastructure

This camp is offered as part of the MCE Microsoft Azure DevOps boot camp.

Please note - the course titles and outlines are based on preliminary information from Microsoft - Titles, content, requirements are subject to change.  Additionally - Microsoft requires students to have achieved an MCA Azure certification to earn the MCE.  We have combo boot camps which include both the MCA and this MCE. 

The NEW Microsoft Certified Expert - Azure DevOps Training & Certification 6 Day Boot Camp focuses on actual job task for designing and building cloud solutions for applications and services.

The Microsoft Certified Azure DevOps boot camp is taught using Microsoft Official Courseware -

AZ-400T01: Implementing DevOps Development Processes
AZ-400T02: Implementing Continuous Integration
AZ-400T03: Implementing Continuous Delivery
AZ-400T04: Implementing Dependency Management

AZ-400T05: Implementing Application Infrastructure
AZ-400T06: Implementing Continuous Feedback
AZ-400T07: Developing a DevOps Strategy

While attending this 6 day camp - students will take one exam (AZ-400) to achieve the Microsoft Certified Expert Azure DevOps Engineer certification.  This hands on, instructor led live camp teaches the knowledge to develop / deploy applications in an Azure environment along with the knowledge needed for the certification exams (administered while attending camp).

Topics covered in this official boot camp:

Describe the benefits of using source control
Migrate from TFVC to Git
Scale Git for Enterprise DevOps
Implement and manage build infrastructure
Manage application config & secrets
Implement a mobile DevOps strategy

Explain why continuous integration matters
Implement continuous integration using Azure DevOps
Configure builds and the options available
Create an automated build workflow
Integrate other build tooling with Azure DevOps
Create hybrid build processes
Describe what is meant by code quality and how it is measured
Detect code smells
Integrate automated tests for code quality
Report on code coverage during testing
Add tooling to measure technical debt
Detect open source and other licensing issues
Implement a container build strategy

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
Design a release strategy
Set up a release management workflow
Implement an appropriate deployment pattern

Recommend artifact management tools and practices
Abstract common packages to enable sharing and reuse
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
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
Design an infrastructure and configuration management strategy
Implement Infrastructure as Code
Manage Azure Kubernetes Service infrastructure
Implement infrastructure compliance and security

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
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 system
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

Plan for the transformation with shared goals and timelines.
Select a project and identify project metrics and KPIs.
Create a team and agile organizational structure.
Develop a project quality strategy.
Plan for secure development practices and compliance rules.
Migrate and consolidate artifacts.
Migrate and integrate source control measures.