Designing and Implementing Microsoft DevOps Solutions (AZ-400)

1. A development team using GitHub wants to adopt a branching strategy that enforces short-lived feature branches and requires all changes to go through pull requests before merging into main. Which workflow should the team implement?

2. A software development team wants to automatically notify the relevant team in Microsoft Teams whenever a pull request is opened or a build fails in Azure DevOps. What is the correct approach?

3. A startup engineering team of 8 developers is building a SaaS application with a target of deploying to production multiple times per day. The team wants to minimize merge conflicts and keep the main branch always deployable. Which branching strategy best fits this scenario?

4. A financial services company releases software on a quarterly schedule. The team needs to maintain multiple production versions simultaneously and must apply hotfixes to older releases without destabilizing active development. Which branching strategy is most appropriate?

5. A development team publishes shared NuGet libraries that are consumed by multiple internal projects across different Azure DevOps projects in the same organization. The team wants any Azure DevOps project in the organization to be able to consume these packages without requiring access to specific projects. Which Azure Artifacts feed scope should the team configure?