Q: What is the main purpose of configuration management in continuous deployment?
-
A
To manage user credentials
-
B
To automate source code testing
-
C
To maintain consistency in environment setup
-
D
To increase hardware performance
C
Answer:
C
Explanation:
Configuration Management (CM) is a critical component in Continuous Deployment (CD) pipelines because it ensures consistency across various deployment environments. When developers push code to production, differences in configurations between development, staging, and production environments can lead to unexpected bugs or failures. Configuration management eliminates this by automating the setup of environments using predefined configuration files or templates, so that every deployment is predictable and reliable. Moreover, it enables tracking of configuration changes over time, ensuring traceability and allowing rollback in case of failures. Tools like Ansible, Puppet, Chef, and Terraform are widely used for managing configurations, while containers like Docker make configuration portable. Thus, without configuration management, CD systems would be error-prone, difficult to scale, and inefficient to maintain.
Related Topic:
Share Above MCQ
Configuration Management