Which of the following is the main advantage of using Infrastructure as Code (IaC) instead of manual provisioning?
Think about how IaC helps when you need to create the same setup multiple times.
IaC enables you to deploy infrastructure automatically and consistently every time, reducing human errors and saving time compared to manual steps.
Why is it important to keep your Infrastructure as Code scripts in version control systems like Git?
Think about how you can undo mistakes or see history with code.
Version control helps track changes, collaborate, and revert to previous infrastructure states if needed, improving safety and transparency.
Which option best explains how Infrastructure as Code supports faster disaster recovery?
Consider how automation helps when you need to rebuild everything quickly.
IaC scripts define infrastructure setup, so you can redeploy the entire environment quickly after a disaster without manual steps.
Which security benefit is unique to Infrastructure as Code compared to manual setup?
Think about how code can enforce rules consistently every time.
IaC can include security policies in code, ensuring they are applied automatically and consistently during every deployment.
When you manually modify cloud resources that are managed by IaC, what is the typical outcome when you next run the IaC deployment?
Consider how IaC keeps infrastructure consistent with its code definitions.
IaC tools detect configuration drift and apply the code-defined state, overwriting manual changes to maintain consistency.