701.4 Continuous Integration and Continuous Delivery (weight: 3) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   What is the main benefit of using infrastructure as code to provision environments?

   • AIt makes environments identical and reproducible
   • BIt requires manual steps to set up each environment
   • CIt eliminates the need for any configuration management
   • DIt only works for cloud environments
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   What is the main advantage of triggering a CI/CD pipeline automatically on every push to a version control repository?

   • AIt guarantees that production deployments happen without any human intervention
   • BIt eliminates the need for version control branching
   • CIt reduces the need for developers to write unit tests
   • DIt ensures that integration issues are detected early and consistently
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A team is designing a CI/CD pipeline for a mobile application. They want to ensure that the app is automatically built and tested on every commit, but the release to the app store should be a manual step performed by the release manager. How should the pipeline be structured?

   • AA pipeline with automated build and test stages, followed by a manual approval gate before the release stage
   • BA pipeline that requires manual approval before the build and test stages
   • CA pipeline that only runs the build and test stages manually when the release manager requests it
   • DA pipeline that automatically builds, tests, and releases the app to the store on every commit
   Reveal Solution Discussion Select an answer first
5. 4foundation · medium

   A DevOps team wants to improve the reliability and maintainability of their CI/CD pipelines. Which practice is widely recognized as a core CI/CD best practice for reducing integration risk and enabling faster feedback?

   • ACommitting code changes directly to the main branch and running the full test suite only at the end of the sprint
   • BRunning automated tests on every commit to the shared repository to detect integration issues early
   • CKeeping the pipeline configuration in a separate repository from the application code to avoid mixing concerns
   • DDeploying to production only after a manual approval from the release manager for every change
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A DevOps team is designing a CI/CD pipeline for a microservices application. The pipeline needs to deploy to a cloud environment and requires access to database credentials and API keys. The team wants to avoid storing secrets in the pipeline configuration files. Which approach is the most secure and recommended?

   • AStore the secrets as environment variables in the pipeline configuration file
   • BShare the secrets with the team via a messaging application and have them enter them manually during deployment
   • CUse a dedicated secrets management service and reference the secrets by name in the pipeline configuration
   • DEmbed the secrets directly in the application's source code
   Reveal Solution Discussion Select an answer first