You are implementing a branching strategy in Azure DevOps. Pull requests must include linked work items, pass build validation, and require at least three reviewers. What should you include in the solution?

Branch policies in Azure DevOps are the correct solution because they allow you to enforce specific requirements for pull requests before code can be merged into a target branch. You can configure policies to require linked work items, ensuring all code changes are tied to a task or bug. Build validation policies can be set up to automatically trigger a build and require it to pass, preventing broken code from being merged. Lastly, you can specify a minimum number of required reviewers, such as three, to ensure thorough code review. Pull request templates provide a standardized description for pull requests but don't enforce requirements. Branch security controls who can contribute to a branch but not the conditions for merging. Pull request permissions define who can create or approve pull requests, but not the specific checks required for approval.