A development team is defining resources in JSON, storing them in a version-control system, and applying the same definitions across multiple environments. They want to roll back unwanted changes and replicate consistent setups. Which strategy best meets these goals?
Depend on a manual process for each environment in which changes are approved individually
Record changes in a spreadsheet and copy environment information from one setup to another
Maintain a single definitions file on a separate server that reacts whenever it detects altered resources
Use a code repository containing resource definitions along with checks for differences before deployment
Storing resource definitions in a code repository with checks for differences provides a repeatable and trackable process. Rollbacks are simpler when every change is version-controlled. Manual updates, spreadsheets, or a single template on an isolated server create risks by lacking robust change tracking or streamlined replication. In contrast, consistent definitions in a repository allow improvements, team collaboration, and rollback capability, aligning with repeatable deployments and drift detection.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a version-control system?
Open an interactive chat with Bash
What are checks for differences in deployments?
Open an interactive chat with Bash
Why is it risky to rely on spreadsheets or manual processes for deployments?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Deployment
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access