Based on the provided metrics and waterfall view, which of the following issues is occurring?

Question

Options

• AAn infinite http 302 redirect loop occurred when loading the Frultiger font object.
• BA CPU saturation issue occurred on the Sydney Cloud agent.
• CThe login.html object is not available on the HTTP server.
• DA bandwidth issue occurred between the Sydney Cloud agent and the bank website.

• A
  4% (1)
• B
  22% (5)
• C
  9% (2)
• D
  65% (15)

Explanation

Option D is correct because a bandwidth issue manifests in the waterfall view as slow, elongated bars across multiple objects - indicating that objects are downloading sequentially and slowly due to constrained throughput between the agent and the target server, which is exactly what the metrics would show for a Sydney Cloud agent with a saturated or limited network link.

Why the distractors are wrong:

• A is wrong because an HTTP 302 redirect loop would appear as a rapid series of 302 status codes in the waterfall, not a bandwidth-related slowdown pattern, and would typically trigger a browser "too many redirects" error.
• B is wrong because CPU saturation on the agent would affect the agent's ability to process data locally, but would not cause the specific network-level timing patterns (long download bars) visible in a waterfall view.
• C is wrong because an unavailable object returns an HTTP 4xx status (typically 404), which would appear as a failed/errored entry in the waterfall - not a bandwidth pattern.

Memory tip: In waterfall views, think in patterns - loops = repeated entries, missing objects = error status codes (4xx), CPU issues = processing delays before request, bandwidth issues = long, drawn-out horizontal bars on downloads. If everything loads slowly end-to-end across multiple objects, think bandwidth first.

No community discussion yet for this question.