Continuous Integration

5 minutes 5 Questions

Continuous Integration (CI) is a development practice where developers integrate code into a shared repository frequently, ideally several times a day. The concept is meant to prevent integration hell. It implies close collaboration between developers and constant code checking, which facilitates e…

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

PMI-ACP - Continuous Integration Example Questions

Test your knowledge of Continuous Integration

Question 1

Your team's build process is slow and affects the overall efficiency of the development process. What strategy would best improve the speed of the build process?

Adding more unit tests Migrating to a different build tool Hiring more build engineers Acquiring more powerful build machines Optimizing the build process and leveraging parallelism Switching to a monorepo

Correct Answer: Optimizing the build process and leveraging parallelism

Optimizing the build process by analyzing bottlenecks and using parallelism to run independent tasks can significantly improve the build speed, allowing developers to receive faster feedback.

Question 2

Your team's Continuous Integration pipeline used to run smoothly, but recently, the test suite has been failing more frequently. Which of the following strategies will help address the issue?

Replacing the CI server Using separate test environments for each team Increasing the duration between code commits Rerunning the test suite until it passes Reducing the number of test cases Implementing a 'fix it first' policy

Correct Answer: Implementing a 'fix it first' policy

A 'fix it first' policy emphasizes the importance of fixing broken builds and test failures quickly, ensuring a high-quality and reliable test suite as well as a stable main branch.

Question 3

Your development team just completed a sprint and found out that there is a critical issue in the codebase that disrupts Continuous Integration. This issue could have been spotted earlier if a particular practice were in place. Which practice could have helped avoid this?

Initiating code reviews at the end of each sprint Performing manual testing Frequent committing of code Deploying only once per day

Correct Answer: Frequent committing of code

In the context of Continuous Integration, the most effective practice in early detection of critical issues would be 'Frequent committing of code'. This practice allows developers to integrate their code changes into the main codebase multiple times a day, enabling potential issues to be detected and resolved quickly before they become too complex. This frequent integration process also allows teams to get fast feedback on whether the changes work well with the existing codebase. On the other hand, 'Performing manual testing' is not the most efficient way to identify issues in a Continuous Integration scenario. It takes time and often lacks the speed and efficiency of automatized tests. 'Initiating code reviews at the end of each sprint' wouldn't help prevent the situation described in the question because by the time the sprint ends, the disruptive issue would already be integrated into the codebase. 'Deploying only once per day' also misses the point of Continuous Integration, which aims for several integrations per day to catch issues early.

Prove Your Agile Expertise

3,800+ questions on Scrum, Kanban, Lean & XP

7 Agile Domains: Agile principles, value-driven delivery, stakeholder engagement, team performance & more
Multi-Framework Coverage: Scrum, Kanban, Lean, XP, Crystal, and DSDM — all in one place
120-Question Mock Exams: Practice under real PMI-ACP conditions: 3 hours, 120 questions
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!