Which of the following statements about Azure DevOps branch policies are true? (Select all that apply.)

Azure DevOps branch policies are designed to protect important branches in your repository by enforcing specific requirements for pull requests. They enforce your team's change management standards by requiring code reviews, linking work items, and checking for successful build completions before merging code. This ensures that all changes follow established procedures. They also enforce your team's code quality by integrating with build pipelines and code analysis tools to ensure that only code meeting defined quality gates can be merged. While branch policies can restrict direct pushes to a branch, they do not control who can read or update code in a general sense (that's handled by repository permissions) nor do they place a branch into a read-only state, as changes are still allowed via pull requests.