CAD CAD Continuous Integration and Testing 2

Question 1

What is the primary purpose of a CI build pipeline in an Agile development environment?

Accepted Answer

To automatically compile, test, and validate every code change merged into the shared repository

Answer

To replace manual code reviews entirely

Answer

To deploy code directly to production without any checks

Answer

To generate documentation for each sprint

Question 2

Which testing strategy is most aligned with the Agile testing pyramid?

Accepted Answer

A large number of unit tests, fewer integration tests, and minimal end-to-end tests

Answer

Equal numbers of unit, integration, and end-to-end tests

Answer

Mostly end-to-end tests with very few unit tests

Answer

Only manual exploratory testing after each sprint

Question 3

In a CI workflow, what does 'breaking the build' typically indicate?

Accepted Answer

A committed change caused compilation errors or test failures in the shared branch

Answer

The CI server hardware has malfunctioned

Answer

A developer deleted the repository by accident

Answer

The project manager rejected a user story

Question 4

What is the recommended response time for fixing a broken CI build in Agile practice?

Accepted Answer

It should be the team's top priority and fixed immediately

Answer

It can wait until the next sprint planning session

Answer

It should be assigned to the QA team only

Answer

It should be deferred until a hardening sprint

Question 5

Which practice helps ensure that automated tests in a CI pipeline remain trustworthy?

Accepted Answer

Eliminating flaky tests and ensuring each test produces deterministic results

Answer

Running tests only on weekends to reduce server load

Answer

Allowing tests to pass intermittently without investigation

Answer

Writing tests only for new features, not bug fixes

Question 6

What is the main benefit of running static code analysis as part of a CI pipeline?

Accepted Answer

It detects code quality issues, security vulnerabilities, and style violations automatically before code review

Answer

It replaces the need for any form of testing

Answer

It speeds up the application at runtime

Answer

It eliminates the need for version control