1. Which tool is commonly used for continuous integration in software development?
A. Docker
B. Jenkins
C. Sublime Text
D. GitHub
Answer: B) Jenkins
Rationale: Jenkins is a popular tool for continuous integration that automates the
process of integrating code changes and running tests.
2. Which of the following is NOT an example of an Agile practice?
A. Daily standups
B. Sprint planning
C. Waterfall milestones
D. Retrospectives
Answer: C) Waterfall milestones
Rationale: Waterfall is a traditional model, while daily standups, sprint planning, and
retrospectives are all Agile practices used to facilitate iterative development.
,3. Which of the following is a method of software development where requirements
and solutions evolve through collaboration between self-organizing cross-functional
teams?
A. Waterfall
B. Agile
C. Spiral
D. V-Model
Answer: B) Agile
Rationale: The Agile methodology focuses on iterative development and collaboration
among cross-functional teams.
4. What is the purpose of "code review" in software development?
A. To test the software for bugs
B. To identify potential errors and improve code quality
C. To design the architecture of the system
D. To finalize the project documentation
Answer: B) To identify potential errors and improve code quality
, Rationale: Code reviews are performed to ensure that the code is of high quality,
follows best practices, and is free from bugs or vulnerabilities.
5. What is the main difference between "black-box testing" and "white-box testing"?
A. Black-box testing is performed by the user, and white-box testing is done by the
developer.
B. Black-box testing focuses on functionality, and white-box testing focuses on
internal code.
C. Black-box testing is for software that uses graphics, and white-box is for console-
based software.
D. Black-box testing involves testing hardware, and white-box testing involves testing
software.
Answer: B) Black-box testing focuses on functionality, and white-box testing focuses
on internal code.
Rationale: Black-box testing looks at the software’s functionality without knowing the
internal workings, while white-box testing involves understanding and testing the
internal structure or code.
6. What does the term "technical debt" refer to?
A. Docker
B. Jenkins
C. Sublime Text
D. GitHub
Answer: B) Jenkins
Rationale: Jenkins is a popular tool for continuous integration that automates the
process of integrating code changes and running tests.
2. Which of the following is NOT an example of an Agile practice?
A. Daily standups
B. Sprint planning
C. Waterfall milestones
D. Retrospectives
Answer: C) Waterfall milestones
Rationale: Waterfall is a traditional model, while daily standups, sprint planning, and
retrospectives are all Agile practices used to facilitate iterative development.
,3. Which of the following is a method of software development where requirements
and solutions evolve through collaboration between self-organizing cross-functional
teams?
A. Waterfall
B. Agile
C. Spiral
D. V-Model
Answer: B) Agile
Rationale: The Agile methodology focuses on iterative development and collaboration
among cross-functional teams.
4. What is the purpose of "code review" in software development?
A. To test the software for bugs
B. To identify potential errors and improve code quality
C. To design the architecture of the system
D. To finalize the project documentation
Answer: B) To identify potential errors and improve code quality
, Rationale: Code reviews are performed to ensure that the code is of high quality,
follows best practices, and is free from bugs or vulnerabilities.
5. What is the main difference between "black-box testing" and "white-box testing"?
A. Black-box testing is performed by the user, and white-box testing is done by the
developer.
B. Black-box testing focuses on functionality, and white-box testing focuses on
internal code.
C. Black-box testing is for software that uses graphics, and white-box is for console-
based software.
D. Black-box testing involves testing hardware, and white-box testing involves testing
software.
Answer: B) Black-box testing focuses on functionality, and white-box testing focuses
on internal code.
Rationale: Black-box testing looks at the software’s functionality without knowing the
internal workings, while white-box testing involves understanding and testing the
internal structure or code.
6. What does the term "technical debt" refer to?