Define and implement a continuous delivery and release management strategy (10-15%)

[ashishrajsrivastava]

Develop deployment scripts and templates

• recommend a deployment solution (e.g. GitHub Actions, Azure Pipelines, Jenkins, CircleCI, etc.) • design and implement Infrastructure as code (ARM, Terraform, PowerShell, CLI) • develop application deployment process (container, binary, scripts) • develop database deployment process (migrations, data movement, ETL) • integrate configuration management as part of the release process • develop complex deployments (IoT, Azure IoT Edge, mobile, App Center, DR, multi- region, CDN, sovereign cloud, Azure Stack, etc.)

Implement an orchestration automation solution

• combine release targets depending on release deliverable (e.g., Infrastructure, code, assets, etc.) • design the release pipeline to ensure reliable order of dependency deployments • organize shared release configurations and process (YAML templates, variable groups) • design and implement release gates and approval processes

Plan the deployment environment strategy

• design a release strategy (blue/green, canary, ring) • implement the release strategy (using deployment slots, load balancer configurations, Azure Traffic Manager, feature toggle, etc.) • select the appropriate desired state solution for a deployment environment (PowerShell DSC, Chef, Puppet, etc.) • plan for minimizing downtime during deployments (VIP Swap, Load balancer, rolling deployments, etc.) • design a hotfix path plan for responding to high priority code fixes

[ashishrajsrivastava]

@TheAzureGuy007 Please assign a label to this issue indicating how many days it will take to cover these issues. One day session will be 3hours. So if think the content is covered in 6 hours then you will assign 2days label and so on. Feel free to create labels according to your time expectation for the module.