Question 1
During an enterprise platform consolidation at a large software services provider, the team documents this issue: Two feature teams work for months on divergent branches before integration. The affected delivery process supports customer-facing applications and shared delivery pipelines; multiple teams must coordinate changes without losing source-to-release traceability. Which change MOST DIRECTLY addresses the control failure without compromising the delivery process?
Explanation
Correct Answer
Correct. Adopt short-lived branches from main with reviewed pull requests, automated checks, and frequent integration instead of prolonged parallel development. The specific observed issue is: Two feature teams work for months on divergent branches before integration. The intervention addresses the github flow and small pull requests exposure, where large divergent branches delay integration and make the impact of changes difficult to review or isolate. After the change, acceptance should establish: A sample feature follows issue to short branch to reviewed PR to green checks to main, with an identifiable deployed commit.
Incorrect Answers
Use standardized GitHub issue templates, labels, assignments and notifications to route actionable user feedback into prioritized work and closure. The GitHub flow and small pull requests prerequisite remains unaddressed.
Link GitHub pull requests and commits to Azure Boards work items and require consistent identifiers and review evidence through delivery. It changes a different feature than GitHub flow and small pull requests.
Connect requirements, test cases, automated test runs, defects and deployment versions through Azure Test Plans or equivalent linked records. That change would not implement GitHub flow and small pull requests.