CAD CAD Continuous Integration and Delivery Questions and Answers 3

Question 1

What is the key difference between continuous delivery and continuous deployment?

Accepted Answer

Continuous delivery requires manual approval before production release while continuous deployment is fully automated

Answer

Continuous deployment includes testing but continuous delivery does not

Answer

Continuous delivery only applies to web applications

Answer

There is no difference between the two practices

Question 2

Which metric best indicates the health of a team's continuous integration practice?

Accepted Answer

The lead time from commit to successful build and test completion

Answer

Number of lines of code committed per day

Answer

Total number of branches in the repository

Answer

Frequency of production incident reports

Question 3

What is the purpose of running integration tests in a staging environment before production deployment?

Accepted Answer

To verify that components work together in an environment that closely mirrors production

Answer

To eliminate the need for unit tests in the pipeline

Answer

To test the application with real customer data

Answer

To reduce the total number of tests that need to be maintained

Question 4

How does feature flagging support continuous delivery practices?

Accepted Answer

By allowing incomplete features to be merged and deployed without being visible to users

Answer

By preventing developers from committing code until a feature is complete

Answer

By automatically generating release notes for each deployment

Answer

By replacing the need for a staging environment

Question 5

What is the main risk of having a slow CI pipeline?

Accepted Answer

Developers batch larger changes and integrate less frequently, increasing merge conflicts

Answer

The application will run slower in production

Answer

Automated tests become less accurate over time

Answer

Code quality tools stop functioning correctly

Question 6

In an agile CI/CD context, what is an 'artifact' produced by the build process?

Accepted Answer

A deployable package such as a JAR, Docker image, or compiled binary

Answer

A document describing the sprint retrospective outcomes

Answer

A record of all code review comments

Answer

A list of user stories completed in the sprint