CAD CAD Continuous Integration and Delivery Questions and Answers 2

Question 1

What is the primary purpose of a build pipeline in continuous integration?

Accepted Answer

To automate the process of compiling, testing, and packaging code changes

Answer

To deploy code directly to production without testing

Answer

To replace manual code reviews entirely

Answer

To manage project documentation updates

Question 2

In a CI/CD workflow, what does 'trunk-based development' emphasize?

Accepted Answer

Developers committing to a single shared branch frequently

Answer

Maintaining long-lived feature branches for stability

Answer

Avoiding merges until the end of a sprint

Answer

Using separate repositories for each team

Question 3

Which practice helps ensure that a deployment can be safely rolled back in a continuous delivery pipeline?

Accepted Answer

Using blue-green or canary deployment strategies

Answer

Deleting previous build artifacts after each deployment

Answer

Disabling monitoring during deployments to reduce noise

Answer

Deploying only during weekends when traffic is low

Question 4

What is a 'flaky test' in the context of continuous integration?

Accepted Answer

A test that produces inconsistent pass/fail results without code changes

Answer

A test that consistently fails due to a known bug

Answer

A test that runs too slowly to include in the pipeline

Answer

A test written without assertions

Question 5

Why should database schema migrations be backward-compatible in a continuous delivery environment?

Accepted Answer

To allow the previous application version to function during a rolling deployment

Answer

Because databases cannot handle schema changes during uptime

Answer

To avoid needing automated testing for database changes

Answer

Because agile teams never modify database schemas

Question 6

What role does a container registry play in a CI/CD pipeline?

Accepted Answer

It stores and versions built container images for consistent deployment across environments

Answer

It replaces the need for version control systems

Answer

It monitors application performance in production

Answer

It manages developer access permissions to the codebase