How can a ticket-based system slow down infrastructure provisioning and limit the ability to scale? (Choose two.)
How can a ticket-based system slow down infrastructure provisioning and limit the ability to scale? (Choose two.)
A ticket-based system can slow down infrastructure provisioning and limit the ability to scale in two main ways. Firstly, a request must be submitted for infrastructure changes. This introduces delays, especially if approvals are needed or if the process is manual. Secondly, as additional resources are required, more tickets are submitted. This increases the administrative burden and creates bottlenecks, making it harder to scale rapidly or handle dynamic workloads efficiently.
Answer is BC
B. A request must be submitted for infrastructure changes C. As additional resources are required, more tickets are submitted Explanation: B. A request must be submitted for infrastructure changes: In a ticket-based system, users often need to raise a request or a ticket for any infrastructure changes. This process can introduce delays, especially when changes are needed urgently or frequently. It can slow down the provisioning process as it adds an additional layer of approval and manual intervention. C. As additional resources are required, more tickets are submitted: In a ticket-based system, when scaling is required, users may need to submit additional tickets for each resource or instance they need. This manual process can become a bottleneck as the number of tickets increases, making it less efficient for scaling rapidly or handling dynamic workloads.
B and C both ticket based
B and C
B and C are correct
B and C lets populate C
Both B & C
B and C
B and C
B and C indeed.
B and C
B and C
B and C. increase amount of C