Question 1
At the Alderbridge payments platform, a product team retains long-lived development branches that routinely conflict during release week. Which approach most directly resolves the reported issue?
Explanation
Correct Answer
The relevant weakness is that long-lived branches defer integration and allow incompatible changes to accumulate. The best correction is to adopt short-lived feature branches and reviewed pull requests into a protected main branch. Evidence of success would be that two successive releases integrate smaller changes through reviewed pull requests without a last-minute conflict backlog. This directly addresses the reported issue at the Alderbridge payments platform.
Incorrect Answers
The proposed action would be to create actionable issues automatically from failed pipeline or monitoring events with deduplication, which is relevant to automated issue creation from failures. It would leave the main reported problem unresolved. For the Alderbridge payments platform, the priority is to adopt short-lived feature branches and reviewed pull requests into a protected main branch.
The scenario states: At the Alderbridge payments platform, a product team retains long-lived development branches that routinely conflict during release week. “Integrate meaningful pipeline failure events with a supported Microsoft Teams notification channel and owner” does not correct this failure. Long-lived branches defer integration and allow incompatible changes to accumulate. The more directly supported option is “Adopt short-lived feature branches and reviewed pull requests into a protected main branch”.
This is appropriate in cases involving release throughput metrics, but the facts here call for the team to adopt short-lived feature branches and reviewed pull requests into a protected main branch. For the Alderbridge payments platform, the priority is to adopt short-lived feature branches and reviewed pull requests into a protected main branch.