Duration – 5Days
Azure Developer Associate contains courseware that helps prepare students for Exam AZ-400. Passing this exam is required to earn the Azure Developer Associate certification.
Students in this course are interested in implementing DevOps processes or in passing the Microsoft Azure DevOps Solutions certification exam.
Fundamental knowledge about Azure, version control, Agile software development, and core software development principles. It would be helpful to have experience in an organization that delivers software.
After completing this course, students will be able to:
1. Describe the benefits of using source control
2. Migrate from TFVC to Git
3. Scale Git for Enterprise DevOps
4. Implement and manage build infrastructure Manage application config & secrets
5. Implement a mobile DevOps strategy
6. Explain why continuous integration matters
7. Implement continuous integration using Azure DevOps
8. Configure builds and the options available
9. Create an automated build workflow
10. Integrate other build tooling with Azure DevOps
11. Create hybrid build processes
12. Differentiate between a release and a deployment
13. Define the components of a release pipeline
14. Explain things to consider when designing your release strategy
15. Classify a release versus a release process, and outline how to control the quality of both
16. Describe the principle of release gates and how to deal with release notes and documentation
17. Explain deployment patterns, both in the traditional sense and in the modern sense
18. Choose a release management tool
19. Explain the terminology used in Azure DevOps and other Release Management Tooling
20. Describe what a Build and Release task is, what it can do, and some available deployment tasks
21. Classify an Agent, Agent Queue and Agent Pool
22. Explain why you sometimes need multiple release jobs in one release pipeline
23. Differentiate between multi-agent and multi-configuration release job
24. Use release variables and stage variables in your release pipeline
25. Deploy to an environment securely, using a service connection
26. Embed testing in the pipeline
27. List the different ways to inspect the health of your pipeline and release by using, alerts, service hooks and reports
28. Create a release gate
29. Describe deployment patterns
30. Implement Blue Green Deployment
31. Implement Canary Release
32. Implement Progressive Exposure Deployment
33. Recommend artifact management tools and practices
34. Abstract common packages to enable sharing and reuse
35. Inspect codebase to identify code dependencies that can be converted to packages
36. Identify and recommend standardized package types and versions across the solution
37. Refactor existing build pipelines to implement version strategy that publishes packages
38. Manage security and compliance
39. Inspect open source software packages for security and license compliance to align with corporate standards
40. Configure build pipeline to access package security and license rating ∙ Configure secure access to package feeds
41. Apply infrastructure and configuration as code principles
42. Deploy and manage infrastructure using Microsoft automation technologies such as ARM templates, PowerShell, and Azure CLI
43. Describe deployment models and services that are available with Azure
44. Deploy and configure a Managed Kubernetes cluster
45. Deploy and configure infrastructure using 3rd party tools and services with Azure, such as Chef, Puppet, Ansible, SaltStack, and Terraform
46. Define an infrastructure and configuration strategy and appropriate toolset for a release pipeline and application infrastructure
47. Implement compliance and security in your application infrastructure
48. Describe what is meant by code quality and how it is measured
49. Detect code smells
50. Integrate automated tests for code quality
51. Report on code coverage during testing
52. Add tooling to measure technical debt
53. Detect open source and other licensing issues
54. Implement a container build strategy
55. Design practices to measure end-user satisfaction
56. Design processes to capture and analyze user feedback from external sources
57. Design routing for client application crash report data
58. Recommend monitoring tools and technologies
59. Recommend system and feature usage tracking tools
60. Configure crash report integration for client applications
61. Develop monitoring and status dashboards
62. Implement routing for client application crash report data
63. Implement tools to track system usage, feature usage, and flow
64. Integrate and configure ticketing systems with development team’s work management system
65. Analyze alerts to establish a baseline
66. Analyze telemetry to establish a baseline
67. Perform live site reviews and capture feedback for system outages
68. Perform ongoing tuning to reduce meaningless or non-actionable alerts
69. Plan for the transformation with shared goals and timelines.
70. Select a project and identify project metrics and KPIs.
71. Create a team and agile organizational structure.
72. Develop a project quality strategy.
73. Plan for secure development practices and compliance rules.
74. Migrate and consolidate artifacts.
75. Migrate and integrate source control measures.