フリー問題

問題文

A developer rewrote the shared branch and everyone else lost commits. Which server side setting prevents that, and what does the tool itself guarantee?

選択肢

1. The tool itself only refuses a push that is not a fast forward by default, and that refusal can be overridden with a flag, so the protection has to come from a server side rule that forbids the override on the named branch and can also demand a passing ticket and an approving note before any merge in the configuration.
2. The tool itself only refuses a push that is not a signed commit by default, and that refusal can be overridden with a token, so the protection has to come from a server side rule that forbids the override on the named branch and can also demand a passing ticket and an approving note before any merge in the configuration.
3. The tool itself only refuses a push that is not a signed commit by default, and that refusal can be overridden with a token, so the protection has to come from a server side rule that forbids the override on the named branch and can also demand a passing check and an approving review before any merge in the configuration.
4. The tool itself only refuses a push that is not a fast forward by default, and that refusal can be overridden with a flag, so the protection has to come from a server side rule that forbids the override on the named branch and can also demand a passing check and an approving review before any merge in the configuration.