Question 150
An experiment must compare an old production commit to a new branch without rewriting either. Which Git operation supports safe isolation?
Explanation
Correct Answer
Independent branches preserve the production baseline while enabling controlled experiments and traceable diffs.
Incorrect Answers
Require pull requests and code review before merging changes to the protected branch. That operation would be relevant if: A team pushes model training changes directly to the protected main branch and later cannot identify why production behavior changed. Its corresponding reason or verification is: Reviewed change history identifies the intent and author of modifications before those changes reach production automation. However the problem in this question is: An experiment must compare an old production commit to a new branch without rewriting either. The requirement instead calls for Create a separate comparison branch from the recorded production commit; the question-specific check is: Independent branches preserve the production baseline while enabling controlled experiments and traceable diffs.
Use small reviewed feature branches with merge conflict resolution against the current main branch. A separate source case supports that approach when: Several engineers independently edit one YAML deployment configuration and merge conflicts repeatedly cause incorrect production parameters. The supporting rationale or observable result is: Controlled branch integration makes conflicting edits visible before production configuration is deployed. This question describes a different issue: An experiment must compare an old production commit to a new branch without rewriting either. Address it through Create a separate comparison branch from the recorded production commit, with the required justification or evidence: Independent branches preserve the production baseline while enabling controlled experiments and traceable diffs.
Add appropriate generated-artifact patterns to the project's .gitignore. This is useful for the distinct issue: A model training script accidentally includes local experiment outputs and __pycache__ in each commit. The relevant technical rationale or evidence for that issue is: Ignoring reproducible caches and local outputs keeps source history focused on reviewed code and declarative configuration. Here the reported issue is: An experiment must compare an old production commit to a new branch without rewriting either. The relevant response is: Create a separate comparison branch from the recorded production commit. The first result cannot verify this different correction: Independent branches preserve the production baseline while enabling controlled experiments and traceable diffs.