An organization that uses an open-source method for building and adjusting resources in a cloud environment wants to maintain stability in production while changes are tested. Which technique best ensures the environment remains consistent?
Import the latest revision from the main branch whenever code is built.
Clone the repository locally and allow merges on a rolling basis for all updates.
Keep a single locked file for modules across each environment to ensure uniformity.
Reference stable releases so that tested versions are used until new ones are validated.
Infrastructure as code (IaC) promotes consistent and repeatable deployments. Referencing stable releases prevents unintended updates from passing into production. Pulling from the main branch introduces changes prematurely, relying on a single locked file for shared modules can cause unexpected behavior across different stages, and merging locally on a rolling basis might allow unreviewed code to be included. Organized release management through stable references helps avoid disruptions.
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 Infrastructure as Code (IaC)?
Open an interactive chat with Bash
Why are stable releases important in cloud environments?
Open an interactive chat with Bash
What are the risks of pulling code from the main branch for production?