A SaaS company sees the link that serves remote staff stay full through the workday, and someone proposes renaming the dashboard as the response. Which action belongs in the capacity report?
Select an answer to reveal the explanation.
Short Explanation
Renaming the dashboard is like relabeling a speedometer: it won’t widen a link that stays full. You should recommend the engineering change that adds capacity or shifts remote-staff traffic off the saturated link. Capacity is the constraint; another alert or more samples won’t remove it.
Full Explanation
Because the link serving remote staff stays full through the workday, the capacity report should recommend an engineering change: add capacity or shift that traffic onto a path that can carry it. This directly addresses the known constraint. Renaming the dashboard gives the saturated link a more descriptive title, but a clearer label does not change how full the link is. Adding another alert on the full link reaches a team already watching it each workday; it adds no capacity, changes no topology, and adjusts no traffic policy. Gathering more samples of that same link without changing its size, path, or traffic policy extends the evidence but supplies no engineering action. Exam caveat: a dashboard name can make a full link easier to find, but better visibility is not a capacity recommendation when the saturation is already known. Practical check: after the recommended engineering change, verify that remote-staff traffic no longer saturates the link throughout the workday, either because capacity was added or because the traffic was moved. If the link remains just as full and only its title changes, the report has not changed the network.