Which statement best describes Infrastructure as Code (IAC) in cloud-native automation?

Which statement best describes Infrastructure as Code (IAC) in cloud-native automation?

• A. It standardizes manual server configuration.
• B. It encrypts all data at rest.
• C. It enables infrastructure to be described in code and version-controlled.
• D. It eliminates the need for monitoring.

Answer: (C)

In cloud-native automation, Infrastructure as Code means you describe all your infrastructure—servers, networks, policies, and services—in code and store that code in version control. This makes infrastructure a reproducible artifact just like application code. Tooling can read these declarations and automatically provision, configure, and update resources to match the desired state, enabling consistent environments across environments and easy rollbacks by reverting changes in version control. It also provides an audit trail of who changed what and when, which is crucial for compliance and collaboration. This approach is not about encrypting data or removing monitoring. Encryption concerns data security, not how infrastructure is defined. Monitoring remains essential to observe health and performance. And Infrastructure as Code emphasizes replacing manual configuration with codified, repeatable processes rather than standardizing manual steps.

In cloud-native automation, Infrastructure as Code means you describe all your infrastructure—servers, networks, policies, and services—in code and store that code in version control. This makes infrastructure a reproducible artifact just like application code. Tooling can read these declarations and automatically provision, configure, and update resources to match the desired state, enabling consistent environments across environments and easy rollbacks by reverting changes in version control. It also provides an audit trail of who changed what and when, which is crucial for compliance and collaboration.

This approach is not about encrypting data or removing monitoring. Encryption concerns data security, not how infrastructure is defined. Monitoring remains essential to observe health and performance. And Infrastructure as Code emphasizes replacing manual configuration with codified, repeatable processes rather than standardizing manual steps.