Which of the following is not an advantage of using infrastructure as code operations?

• A. Self-service infrastructure deployment
• B. Troubleshoot via a Linux diff command
• C. Public cloud console configuration workflows
• D. API driven workflows

Answer: (C)

Infrastructure as code focuses on automating, standardizing, and versioning how infrastructure is described and applied, so deployments are repeatable, auditable, and easily integrated into pipelines. Using public cloud console workflows relies on manual GUI steps, which are slower, harder to version, and prone to human error. That manual, ad-hoc approach clashes with the reliability and speed that IaC aims to provide, making it not an advantage of IaC.

On the other hand, self-service infrastructure deployment fits perfectly with IaC: teams can provisioning resources through code and automated processes without waiting on a human to click through a console. The ability to preview changes through a diff or plan output aligns with IaC as well, because you can see exactly what will change before applying it, ensuring safer updates. API-driven workflows are central to IaC, enabling automation, integration with CI/CD, and scalable management across environments.