What are some of the problems of how infrastructure was traditionally managed before Infrastructure as Code? (select three)

Question

Options

• ARequests for infrastructure or hardware required a ticket, increasing the time required to
• BTraditional deployment methods are not able to meet the demands of the modern
• CTraditionally managed infrastructure can't keep up with cyclic or elastic applications
• DPointing and clicking in a management console is a scalable approach and reduces

• A
  89% (32)
• D
  11% (4)

Explanation

Before IaC, infrastructure provisioning was slow and error-prone. (A) Hardware/infrastructure requests required tickets and manual approval workflows, adding significant lead time. (B) Traditional methods - manual server configuration, point-and-click consoles - cannot keep pace with the speed and scale demanded by modern cloud-native applications and CI/CD pipelines. (C) Manually managed infrastructure struggles with elastic or cyclical workloads that need to scale rapidly up or down. Choice D is the opposite of a problem - it describes pointing and clicking as 'scalable,' which is incorrect; manual console operations are inherently unscalable and are themselves one of the core problems IaC was designed to solve.

No community discussion yet for this question.