CI/CD — Learn free · DataAI Nexus

Self-check

Questions 1–10 of 10

1. What does CI stand for in CI/CD?
Question 1A. Continuous ImprovementB. Continuous IntegrationC. Code InspectionD. Configuration IntegrationE. Controlled Implementation
2. What does CD stand for in CI/CD?
Question 2A. Code DevelopmentB. Continuous DesignC. Change DocumentationD. Continuous Delivery or DeploymentE. Configuration Database
3. What was the challenge with the traditional development and implementation life cycle once coding was complete?
Question 3A. The remaining steps were time-consuming, with many manual processes and dependencies on departments for review, approval and deploymentB. Developers had no access to version controlC. Code could not be packaged for productionD. Testing was not permitted before deploymentE. Deployments could only happen once a year
4. In the example where five deployments are carried out at the same time, four go smoothly and the fifth breaks the other four. What does this illustrate?
Question 4A. That deployments should always be done in batches of fiveB. That testing is unnecessary for small changesC. That automated pipelines cause more failures than manual onesD. That version control cannot handle parallel workE. That with manual processes one deployment can affect other people's code as well
5. Once development is done and code is pushed into the CI process, what does CI do?
Question 5A. Deploys the code straight to productionB. Archives the code for auditC. Builds and tests the code before passing it to the CD processD. Provisions new serversE. Requests manual approval from each department
6. What does the CD process do after receiving code from CI?
Question 6A. Builds, configures, packages and deploys it so that it meets all production-ready standardsB. Runs unit tests onlyC. Writes the release notesD. Rolls the code back to the previous versionE. Sends the code to business users for sign-off
7. With the help of CI/CD, how much has the release cycle for small deployments been reduced?
Question 7A. From years to monthsB. From weeks to a few daysC. From hours to secondsD. From days or sometimes weeks to minutesE. From months to weeks
8. Which development approach does CI/CD directly support, enabling mini code deployments?
Question 8A. Waterfall developmentB. Big-bang releasesC. Agile developmentD. Mainframe batch developmentE. Prototype-only development
9. What is identified as the fundamental reason errors were inevitable in the traditional release process?
Question 9A. Insufficient hardwareB. Poorly written codeC. Lack of a data warehouseD. Slow network connectionsE. Human involvement in the manual steps
10. What is said about the future of release management?
Question 10A. Manual review boards will return for safetyB. The future is CI/CD for any and every kind of release managementC. Release management will be replaced by data governanceD. Only large enterprises will need release managementE. Releases will be limited to once per quarter