Which DevOps practice is used when automating an operations environment to automatically adjust in scale with the demands of users?

Question

Options

• Amonitoring and logging
• Bcommunication and collaboration
• Cmicroservices
• Dinfrastructure-as-code

• C
  5% (1)
• D
  95% (19)

Explanation

Infrastructure-as-code (IaC) is correct because it treats your entire operations environment - servers, networks, load balancers - as programmable, version-controlled definitions. When user demand spikes, IaC tools (like Terraform or CloudFormation) can automatically provision or remove resources by executing those definitions, enabling true auto-scaling without manual intervention.

Why the others are wrong:

• A (monitoring and logging) - observes system behavior and records events, but does not take action to scale anything.
• B (communication and collaboration) - describes team culture and tooling (e.g., Slack, shared dashboards), not infrastructure automation.
• C (microservices) - is an architectural pattern for decomposing applications into small services; it can benefit from scaling but is not the practice that performs the scaling.

Memory tip: Think of IaC as a recipe for your infrastructure. Just as you can print more copies of a recipe to make more food on demand, IaC lets you "print" more infrastructure automatically when user load increases. If it's written down as code, it can be automated - and automation = scaling on demand.

No community discussion yet for this question.