1. What is Gerrit?
a. A version control system
b. A code review tool
c. A bug tracking system
d. A continuous integration tool
Answer: b
2. Which version control systems are commonly integrated with Gerrit?
a. Git
b. Subversion
c. Mercurial
d. All of the above
Answer: a
3. What is the primary purpose of Gerrit?
a. Managing software development projects
b. Managing databases
c. Facilitating code review and collaboration
d. Managing documentation
Answer: c
4. In Gerrit, what is a "change"?
a. A bug report
b. A new feature request
c. A code review request
d. A software release
Answer: c
5. Which of the following is NOT a common feature of Gerrit?
a. Code review
b. Continuous integration
c. Issue tracking
d. Access control
Answer: c
6. What is a "Change-Id" in Gerrit?
a. An identifier for a change in the Git repository
b. A unique ID generated for each code review
c. A label indicating the change's priority
d. A version control system used in Gerrit
Answer: b
7. What is a "Patch Set" in Gerrit?
a. A set of changes made to the Gerrit server
b. A collection of modified files within a change
c. A list of reviewers for a change
d. A change's unique identifier
Answer: b
8. What is the purpose of the "Submit" action in Gerrit?
a. To reject a change
b. To approve and merge a change
c. To close a change without merging
d. To create a new change
Answer: b
9. How does Gerrit help maintainers and reviewers track code changes?
a. Through automated code formatting
b. Through code searching capabilities
c. By tracking and displaying code review comments
d. By rejecting all code changes
Answer: c
10. What is the purpose of the "Code-Review" label in Gerrit?
a. To automatically format code
b. To review the code's quality
c. To track the progress of code changes
d. To label code changes with version numbers
Answer: b
11. How does Gerrit handle conflicts in code changes?
a. Gerrit automatically resolves conflicts
b. Gerrit allows multiple versions of conflicting code changes
c. Gerrit rejects code changes with conflicts
d. Gerrit automatically closes conflicts
Answer: b
12. In Gerrit, what is a "Reviewer"?
a. The person who submitted the code change
b. A person responsible for fixing code issues
c. Someone assigned to review and comment on a code change
d. The person in charge of merging code changes
Answer: c
13. What is the purpose of the "Verified" label in Gerrit?
a. To indicate the code change is untested
b. To indicate the code change has been reviewed
c. To indicate the code change has passed automated tests
d. To indicate the code change has been rejected
Answer: c
14. How can you view the history of a code change in Gerrit?
a. By using the "git log" command
b. By clicking on the change's ID in the web interface
c. By creating a new branch
d. By using the "git diff" command
Answer: b
15. What is a "Topic" in Gerrit?
a. A code review comment
b. A way to categorize related code changes
c. A type of permission in Gerrit
d. A user role in Gerrit
Answer: b
16. What is a "Cherry Pick" in Gerrit?
a. A type of code review comment
b. A way to pick code changes randomly
c. The process of applying a code change from one branch to another
d. A review label in Gerrit
Answer: c
17. How does Gerrit ensure code quality and consistency?
a. Through automated code formatting
b. By rejecting all code changes
c. By limiting code reviews
d. Through automated code suggestions
Answer: a
18. What is the purpose of the "Rebase" action in Gerrit?
a. To close a change
b. To integrate the latest changes from the target branch into the change
c. To label a code change with a version number
d. To merge the change
Answer: b
19. What is a "Change Owner" in Gerrit?
a. The person responsible for managing the Gerrit server
b. The person who submitted the code change
c. The person who reviews the code change
d. The person in charge of merging code changes
Answer: b
20. In Gerrit, what is a "WIP" change?
a. A change that has been merged
b. A change that is still in progress and not ready for review
c. A change with conflicts that need resolution
d. A change that has been closed without merging
Answer: b
21. How does Gerrit handle code reviews in a distributed team?
a. By forcing all reviewers to be in the same location
b. By allowing remote code reviews through the web interface
c. By rejecting code reviews from remote locations
d. By closing code changes submitted from remote locations
Answer: b
22. What is the purpose of the "Abandon" action in Gerrit?
a. To reject a code change
b. To abandon the Gerrit server
c. To close a code change without merging
d. To integrate a code change
Answer: c
23. What is a "Reviewer Account" in Gerrit?
a. A user account for the person who submitted the code change
b. A user account for someone responsible for code quality
c. A user account for someone assigned to review code changes
d. A user account for the Gerrit administrator
Answer: c
24. What is the purpose of the "Merge" action in Gerrit?
a. To reject a code change
b. To integrate the code change into the target branch
c. To close a code change without merging
d. To create a new code change
Answer: b
25. What is a "Project" in Gerrit?
a. A code review comment
b. A container for related code changes and repositories
c. A code review label
d. A code review status
Answer: b
26. How does Gerrit help with access control to code repositories?
a. By allowing anyone to access any repository
b. By implementing fine-grained access control with permissions
c. By requiring code changes to be approved by all users
d. By rejecting code changes based on access control
Answer: b
27. What is a "Submit Strategy" in Gerrit?
a. A strategy for submitting code changes
b. A strategy for rejecting code changes
c. A strategy for testing code changes
d. A strategy for creating code changes
Answer: a
28. How does Gerrit handle conflicts between multiple code reviewers?
a. By automatically rejecting all code changes
b. By letting the reviewers resolve conflicts among themselves
c. By requiring approval from a senior developer
d. By assigning a random reviewer to resolve conflicts
Answer: b
29. What is the purpose of the "Gerrit Trigger" in continuous integration systems like Jenkins?
a. To trigger automated tests in Gerrit
b. To reject code changes in Gerrit
c. To integrate code changes in Jenkins
d. To trigger builds and tests based on code changes in Gerrit
Answer: d
30. What is the purpose of the "Submit Type" in Gerrit?
a. To specify the type of code change
b. To indicate the code change's status
c. To specify how the code change should be submitted
d. To indicate the code change's priority
Answer: c
31. In Gerrit, what is a "Reviewer Score"?
a. A score given by the Gerrit administrator
b. A score assigned to a code reviewer based on their performance
c. A score indicating the age of a code change
d. A score indicating the complexity of a code change
Answer: b
32. What is the purpose of the "Quick Approve" feature in Gerrit?
a. To quickly approve code changes without review
b. To quickly close code changes without merging
c. To quickly submit code changes without review
d. To quickly reject code changes
Answer: a
Top comments (0)