For which reason would an ArcGIS Online administrator run a report instead of viewing a section of the status dashboard?

Running a report serves specific functions that may not be fully realized through the status dashboard, particularly when it comes to detailed item interactions and changes within an organization. Identifying the last member that updated a specific item showcases this need, as reports can provide comprehensive logs and histories on item activities, which often include metadata such as last updates and the creators or editors of those items.

The status dashboard provides a high-level overview of organization metrics and performance but lacks the granularity that reports offer. It is focused more on aggregated statistics such as user counts, storage usage, and overall service status rather than detailed item-specific interactions. Therefore, when detailed operational insights, like tracking updates to individual items and understanding user engagement at that level, are required, generating a report is the more suitable method. This capability allows administrators to maintain oversight on content changes and user contributions within their organization effectively.