CompTIA Cloud+ Practice Test

Which symptom is NOT associated with reaching capacity boundaries?

1. Application failure

2. Latency

3. API abends

4. Request drops

The correct answer is: API abends

Reaching capacity boundaries in a cloud environment can lead to various performance issues and system malfunctions. Application failure, latency, and request drops are all typical symptoms indicative of a system being stretched beyond its limits. Application failure often occurs when resources are insufficient to handle the demands placed on them. This could refer to applications crashing or displaying errors due to a lack of processing power or memory. Latency is a significant symptom of nearing capacity, as it denotes delays in processing requests. As a system becomes overwhelmed and approaches its resource limits, the time taken to respond to requests increases, leading to a sluggish user experience. Request drops happen when a system cannot handle the volume of incoming requests. When resources are maxed out, the system may begin to reject or drop requests, causing incomplete operations and leading to disrupted service. In contrast, encountering an API abend (abnormal end) is less about reaching capacity and more about specific errors in application programming interfaces. While resource constraints can lead to general errors, an abend typically relates to programming issues or other specific faults rather than a direct symptom of capacity boundaries being hit. Thus, this is not consistently associated with reaching capacity limits like the other options are.