|
| 1 | +# Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions |
| 2 | + |
| 3 | +*Skills measured as of July 26, 2024* |
| 4 | + |
| 5 | +## Skills at a Glance |
| 6 | +- Design and implement processes and communications (10–15%) |
| 7 | +- Design and implement a source control strategy (10–15%) |
| 8 | +- Design and implement build and release pipelines (50–55%) |
| 9 | +- Develop a security and compliance plan (10–15%) |
| 10 | +- Implement an instrumentation strategy (5–10%) |
| 11 | + |
| 12 | +## Table of Contents |
| 13 | +1. [Design and Implement Processes and Communications](#1-design-and-implement-processes-and-communications-1015) |
| 14 | + - [Design and Implement Traceability and Flow of Work](#design-and-implement-traceability-and-flow-of-work) |
| 15 | + - [Design and Implement Appropriate Metrics and Queries for DevOps](#design-and-implement-appropriate-metrics-and-queries-for-devops) |
| 16 | + - [Configure Collaboration and Communication](#configure-collaboration-and-communication) |
| 17 | + |
| 18 | +2. [Design and Implement a Source Control Strategy](#2-design-and-implement-a-source-control-strategy-1015) |
| 19 | + - [Design and Implement Branching Strategies](#design-and-implement-branching-strategies) |
| 20 | + - [Configure and Manage Repositories](#configure-and-manage-repositories) |
| 21 | + |
| 22 | +3. [Design and Implement Build and Release Pipelines](#3-design-and-implement-build-and-release-pipelines-5055) |
| 23 | + - [Design and Implement Package Management Strategy](#design-and-implement-package-management-strategy) |
| 24 | + - [Design and Implement Testing Strategy](#design-and-implement-testing-strategy) |
| 25 | + - [Design and Implement Pipelines](#design-and-implement-pipelines) |
| 26 | + - [Design and Implement Deployments](#design-and-implement-deployments) |
| 27 | + - [Design and Implement Infrastructure as Code](#design-and-implement-infrastructure-as-code-iac) |
| 28 | + - [Maintain Pipelines](#maintain-pipelines) |
| 29 | + |
| 30 | +4. [Develop a Security and Compliance Plan](#4-develop-a-security-and-compliance-plan-1015) |
| 31 | + - [Design and Implement Authentication and Authorization](#design-and-implement-authentication-and-authorization) |
| 32 | + - [Manage Sensitive Information](#manage-sensitive-information) |
| 33 | + - [Security and Compliance Scanning](#security-and-compliance-scanning) |
| 34 | + |
| 35 | +5. [Implement an Instrumentation Strategy](#5-implement-an-instrumentation-strategy-510) |
| 36 | + - [Configure Monitoring](#configure-monitoring) |
| 37 | + - [Analyze Metrics and Telemetry](#analyze-metrics-and-telemetry) |
| 38 | + |
| 39 | +## 1. Design and Implement Processes and Communications (10–15%) |
| 40 | + |
| 41 | +### Design and Implement Traceability and Flow of Work |
| 42 | +- Design and implement a structure for the flow of work, including GitHub Flow |
| 43 | +- Design and implement a strategy for feedback cycles, including notifications and GitHub issues |
| 44 | +- Design and implement integration for tracking work, including GitHub projects, Azure Boards, and repositories |
| 45 | +- Design and implement source, bug, and quality traceability |
| 46 | + |
| 47 | +### Design and Implement Appropriate Metrics and Queries for DevOps |
| 48 | +- Design and implement a dashboard, including flow of work metrics: |
| 49 | + - Cycle times |
| 50 | + - Time to recovery |
| 51 | + - Lead time |
| 52 | +- Design and implement appropriate metrics and queries for: |
| 53 | + - Project planning |
| 54 | + - Development |
| 55 | + - Testing |
| 56 | + - Security |
| 57 | + - Delivery |
| 58 | + - Operations |
| 59 | + |
| 60 | +### Configure Collaboration and Communication |
| 61 | +- Document a project by configuring wikis and process diagrams: |
| 62 | + - Markdown syntax |
| 63 | + - Mermaid syntax |
| 64 | +- Configure release documentation: |
| 65 | + - Release notes |
| 66 | + - API documentation |
| 67 | +- Automate creation of documentation from Git history |
| 68 | +- Configure integration: |
| 69 | + - Using webhooks |
| 70 | + - Between Azure Boards and GitHub repositories |
| 71 | + - Between GitHub/Azure DevOps and Microsoft Teams |
| 72 | + |
| 73 | +## 2. Design and Implement a Source Control Strategy (10–15%) |
| 74 | + |
| 75 | +### Design and Implement Branching Strategies |
| 76 | +- Design a branch strategy: |
| 77 | + - Trunk-based |
| 78 | + - Feature branch |
| 79 | + - Release branch |
| 80 | +- Design and implement pull request workflow using: |
| 81 | + - Branch policies |
| 82 | + - Branch protections |
| 83 | +- Implement branch merging restrictions using: |
| 84 | + - Branch policies |
| 85 | + - Branch protections |
| 86 | + |
| 87 | +### Configure and Manage Repositories |
| 88 | +- Design and implement strategy for managing large files: |
| 89 | + - Git Large File Storage (LFS) |
| 90 | + - git-fat |
| 91 | +- Design repository optimization strategy: |
| 92 | + - Scaling with Scalar |
| 93 | + - Cross-repository sharing |
| 94 | +- Configure repository management: |
| 95 | + - Permissions |
| 96 | + - Tags for organization |
| 97 | + - Data recovery using Git commands |
| 98 | + - Data removal from source control |
| 99 | + |
| 100 | +## 3. Design and Implement Build and Release Pipelines (50–55%) |
| 101 | + |
| 102 | +### Design and Implement Package Management Strategy |
| 103 | +- Recommend package management tools: |
| 104 | + - GitHub Packages registry |
| 105 | + - Azure Artifacts |
| 106 | +- Design and implement: |
| 107 | + - Package feeds and views for local/upstream packages |
| 108 | + - Dependency versioning strategy (SemVer, CalVer) |
| 109 | + - Versioning strategy for pipeline artifacts |
| 110 | + |
| 111 | +### Design and Implement Testing Strategy |
| 112 | +- Design and implement: |
| 113 | + - Quality and release gates |
| 114 | + - Security and governance |
| 115 | +- Design comprehensive testing strategy: |
| 116 | + - Local tests |
| 117 | + - Unit tests |
| 118 | + - Integration tests |
| 119 | + - Load tests |
| 120 | +- Implement pipeline testing: |
| 121 | + - Configure test tasks |
| 122 | + - Configure test agents |
| 123 | + - Test results integration |
| 124 | + - Code coverage analysis |
| 125 | + |
| 126 | +### Design and Implement Pipelines |
| 127 | +- Select deployment automation solution: |
| 128 | + - GitHub Actions |
| 129 | + - Azure Pipelines |
| 130 | +- Design and implement runner/agent infrastructure: |
| 131 | + - Cost considerations |
| 132 | + - Tool selection |
| 133 | + - Licensing |
| 134 | + - Connectivity |
| 135 | + - Maintainability |
| 136 | +- Pipeline development and integration: |
| 137 | + - GitHub repositories with Azure Pipelines |
| 138 | + - Trigger rules |
| 139 | + - YAML pipelines |
| 140 | + - Job execution order (parallelism, multi-stage) |
| 141 | +- Complex pipeline scenarios: |
| 142 | + - Hybrid pipelines |
| 143 | + - VM templates |
| 144 | + - Self-hosted runners/agents |
| 145 | +- Pipeline elements: |
| 146 | + - YAML templates |
| 147 | + - Task groups |
| 148 | + - Variables and variable groups |
| 149 | + - Checks and approvals using YAML-based environments |
| 150 | + |
| 151 | +### Design and Implement Deployments |
| 152 | +- Design deployment strategies: |
| 153 | + - Blue-green |
| 154 | + - Canary |
| 155 | + - Ring |
| 156 | + - Progressive exposure |
| 157 | + - Feature flags |
| 158 | + - A/B testing |
| 159 | +- Implementation considerations: |
| 160 | + - Dependency deployment ordering |
| 161 | + - Downtime minimization (VIP swap, load balancing) |
| 162 | + - Rolling deployments |
| 163 | + - Deployment slots |
| 164 | + - Hotfix path planning |
| 165 | + - Resiliency strategy |
| 166 | +- Feature implementation: |
| 167 | + - Feature flags with Azure App Configuration |
| 168 | + - Container/binary/script deployment |
| 169 | + - Database task deployment |
| 170 | + |
| 171 | +### Design and Implement Infrastructure as Code (IaC) |
| 172 | +- Configuration management: |
| 173 | + - Technology recommendations |
| 174 | + - Strategy implementation |
| 175 | +- IaC strategy: |
| 176 | + - Source control |
| 177 | + - Testing automation |
| 178 | + - Deployment automation |
| 179 | +- Environment configuration: |
| 180 | + - Azure Automation State Configuration |
| 181 | + - Azure Resource Manager |
| 182 | + - Bicep |
| 183 | + - Azure Automanage Machine Configuration |
| 184 | + - Azure Deployment Environments |
| 185 | + |
| 186 | +### Maintain Pipelines |
| 187 | +- Monitoring and optimization: |
| 188 | + - Pipeline health (failure rate, duration, flaky tests) |
| 189 | + - Cost optimization |
| 190 | + - Time optimization |
| 191 | + - Performance optimization |
| 192 | + - Reliability optimization |
| 193 | + - Concurrency optimization |
| 194 | +- Management: |
| 195 | + - Retention strategy for artifacts/dependencies |
| 196 | + - Migration from classic to YAML in Azure Pipelines |
| 197 | + |
| 198 | +## 4. Develop a Security and Compliance Plan (10–15%) |
| 199 | + |
| 200 | +### Design and Implement Authentication and Authorization |
| 201 | +- Identity management: |
| 202 | + - Service Principals vs Managed Identity |
| 203 | + - GitHub authentication (Apps, GITHUB_TOKEN, PATs) |
| 204 | + - Azure DevOps connections and tokens |
| 205 | +- Permission management: |
| 206 | + - GitHub roles and permissions |
| 207 | + - Azure DevOps security groups |
| 208 | + - Access levels (stakeholder, collaborator) |
| 209 | + - Project/team configuration |
| 210 | + |
| 211 | +### Manage Sensitive Information |
| 212 | +- Secrets management: |
| 213 | + - Azure Key Vault integration |
| 214 | + - GitHub Actions secrets |
| 215 | + - Azure Pipelines secrets |
| 216 | + - Sensitive file deployment |
| 217 | + - Pipeline security for sensitive data |
| 218 | + |
| 219 | +### Security and Compliance Scanning |
| 220 | +- Scanning strategy: |
| 221 | + - Dependency scanning |
| 222 | + - Code scanning |
| 223 | + - Secret scanning |
| 224 | + - License scanning |
| 225 | +- Security tooling: |
| 226 | + - Microsoft Defender for Cloud DevOps |
| 227 | + - GitHub Advanced Security |
| 228 | + - Container scanning |
| 229 | + - CodeQL analysis |
| 230 | + - Dependabot alerts |
| 231 | + |
| 232 | +## 5. Implement an Instrumentation Strategy (5–10%) |
| 233 | + |
| 234 | +### Configure Monitoring |
| 235 | +- DevOps monitoring: |
| 236 | + - Azure Monitor |
| 237 | + - Log Analytics integration |
| 238 | +- Telemetry collection: |
| 239 | + - Application Insights |
| 240 | + - VM Insights |
| 241 | + - Container Insights |
| 242 | + - Storage Insights |
| 243 | + - Network Insights |
| 244 | +- GitHub monitoring: |
| 245 | + - Insights configuration |
| 246 | + - Chart creation |
| 247 | + - Alerts for Actions and Pipelines |
| 248 | + |
| 249 | +### Analyze Metrics and Telemetry |
| 250 | +- Performance monitoring: |
| 251 | + - CPU, memory, disk, network indicators |
| 252 | + - Usage metrics |
| 253 | + - Application performance |
| 254 | + - Distributed tracing with Application Insights |
| 255 | +- Log analysis: |
| 256 | + - Basic KQL queries |
0 commit comments