CAD FREE CAD Continuous Integration and Delivery Questions and Answers 2 — Questions and Answers
Question 1: In an Agile CI/CD pipeline, what is the primary purpose of a build artifact repository such as JFrog Artifactory or Nexus?
- To store and version compiled binaries and packages for consistent deployments (Correct answer)
- To replace the source code version control system
- To monitor application performance in production
- To manage user authentication tokens
Correct answer: To store and version compiled binaries and packages for consistent deployments
Artifact repositories store versioned build outputs so that the exact same binary can be promoted through environments without rebuilding.
Question 2: Which practice ensures that every code commit to the main branch automatically triggers a full build and test suite?
- Continuous Integration (Correct answer)
- Continuous Deployment
- Blue-Green Deployment
- Feature Branching
Correct answer: Continuous Integration
Continuous Integration requires that each commit is automatically built and tested to detect integration errors early.
Question 3: What is a canary release strategy in the context of Continuous Delivery?
- Deploying a new version to a small subset of users before a full rollout (Correct answer)
- Releasing all features simultaneously to every user
- Rolling back to the previous version after every deployment
- Running the test suite only on the canary branch
Correct answer: Deploying a new version to a small subset of users before a full rollout
A canary release gradually exposes a new version to a small percentage of users to detect issues before wider deployment.
Question 4: In a CI/CD workflow, what does the term 'pipeline as code' refer to?
- Defining build, test, and deploy stages in a version-controlled configuration file (Correct answer)
- Writing application code that self-deploys without any pipeline
- Using a graphical drag-and-drop tool to design the pipeline
- Storing pipeline logs inside the application database
Correct answer: Defining build, test, and deploy stages in a version-controlled configuration file
Pipeline as code means the entire CI/CD pipeline definition lives in a versioned file (e.g., Jenkinsfile, .gitlab-ci.yml) alongside the source code.
Question 5: Which metric is most useful for measuring the effectiveness of a Continuous Integration process?
- Build failure rate and mean time to fix broken builds (Correct answer)
- Number of lines of code written per sprint
- Total number of repositories in the organization
- Frequency of team standup meetings
Correct answer: Build failure rate and mean time to fix broken builds
Build failure rate and mean time to fix directly measure how well the team maintains a healthy integration process.
Question 6: What is the key difference between Continuous Delivery and Continuous Deployment?
- Continuous Delivery requires manual approval before production release; Continuous Deployment is fully automated (Correct answer)
- Continuous Deployment requires manual approval; Continuous Delivery is fully automated
- They are identical concepts with different names
- Continuous Delivery only applies to mobile applications
Correct answer: Continuous Delivery requires manual approval before production release; Continuous Deployment is fully automated
Continuous Delivery keeps code in a releasable state with a manual gate, while Continuous Deployment automatically pushes every passing change to production.
CAD FREE CAD Continuous Integration and Delivery Questions and Answers 2
In an Agile CI/CD pipeline, what is the primary purpose of a build artifact repository such as JFrog Artifactory or Nexus?