Question 140
At the Whitford logistics company, teams hold completed features on private branches until a large product launch. How should the team reduce the chance of the issue recurring?
Explanation
Correct Answer
The continuing risk is that long waits for a launch create avoidable branch drift and late integration risk. To sustain the correction, review feature flag ownership and remove obsolete flags after release. This directly addresses the reported issue at the Whitford logistics company.
Incorrect Answers
That practice helps control a different risk: direct pushes bypass independent checks and may introduce untested production changes. The recurring control here should be to review feature flag ownership and remove obsolete flags after release. For the Whitford logistics company, the priority is to integrate reviewed changes behind controlled flags while keeping user exposure disabled until approved.
The alternative suggests that the team review dependency update proposals with traceable version changes; it would not directly prevent the observed issue from returning. For the Whitford logistics company, the priority is to integrate reviewed changes behind controlled flags while keeping user exposure disabled until approved.
This maintenance work is reasonable for repository secret push protection. The continuing exposure described here is that long waits for a launch create avoidable branch drift and late integration risk. For the Whitford logistics company, the priority is to integrate reviewed changes behind controlled flags while keeping user exposure disabled until approved.