Which of the following are advantages of using infrastructure as code (laC) instead of provisioning with a graphical user interface (GUI)? Choose two correct answers.

The correct answer is B. Lets you version, reuse, and share infrastructure configuration E. Reduces risk of operator error. B is correct: IaC configuration files can be stored in version control, reviewed, reused across environments, and shared across teams - unlike one-off GUI clicks that leave no auditable trail. E is correct: because infrastructure is defined in code and applied consistently, human

Submitted by fatema_kw· Apr 18, 2026Understand Infrastructure as Code (IaC) Concepts

Question

Which of the following are advantages of using infrastructure as code (laC) instead of provisioning with a graphical user interface (GUI)? Choose two correct answers.

Options

APrevents manual modifications to your resources
BLets you version, reuse, and share infrastructure configuration
CSecures your credentials
DProvisions the same resources at a lower cost
EReduces risk of operator error

How the community answered

(57 responses)

A
2% (1)
B
91% (52)
C
2% (1)
D
5% (3)

Explanation

B is correct: IaC configuration files can be stored in version control, reviewed, reused across environments, and shared across teams - unlike one-off GUI clicks that leave no auditable trail. E is correct: because infrastructure is defined in code and applied consistently, human error from misconfiguring a GUI is significantly reduced. A is incorrect - IaC does not technically prevent someone from making manual changes through a GUI or CLI after the fact. C is incorrect - IaC itself does not secure credentials. D is incorrect - IaC does not inherently reduce cloud resource costs.

Topics

#Infrastructure as Code#IaC benefits#Automation#Version Control

Community Discussion

No community discussion yet for this question.

Full TERRAFORM-ASSOCIATE-004 Practice